Pressman forces Enterprise into asteroid chasm
Plot Beats
The narrative micro-steps within this event
Picard inquires about the Romulan's location as Data reveals the Pegasus's warp core signature deep within the asteroid, prompting Riker to question how to reach it. Picard suggests using a shuttle, but Data cautions against it due to potential gravimetric or magnetic fluctuations.
Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers. He identifies a chasm on the asteroid's surface large enough for the ship to maneuver, arguing it's the only way to salvage the Pegasus, while Data cautiously acknowledges the theoretical possibility but warns of unforeseen difficulties.
Who Was There
Characters present in this moment
Resolute and slightly impatient, with a hint of paternalistic frustration toward Picard’s hesitation. He views the Pegasus’s retrieval as a necessity that justifies overriding protocol, and his emotional investment in the mission’s success overshadows concerns about risk or morality.
Pressman dominates the scene with calm authority, dismissing Picard’s objections and Riker’s shuttle suggestion with a single, firm directive: ‘Prepare to take the Enterprise in, Captain. That’s an order.’ He points to the Okudagram, demanding Data display the chasm on the viewer, and justifies the maneuver as the only viable solution. His body language—leaning slightly forward, voice smooth but unyielding—signals absolute confidence in his decision, leaving no room for debate.
- • To retrieve the *Pegasus* at all costs, even if it means violating Starfleet protocols or treating risks.
- • To assert his authority over Picard and the *Enterprise* crew, reinforcing his role as the mission’s ultimate decision-maker.
- • The ends justify the means when national security (or in this case, Federation security) is at stake.
- • Picard’s objections are well-intentioned but naive, failing to grasp the broader strategic imperative.
Controlled frustration with a simmering sense of betrayal by Starfleet’s hierarchy, tempered by professional duty.
Picard enters the bridge and immediately challenges Pressman’s authority by proposing a shuttle mission and questioning the risks of taking the Enterprise into the asteroid chasm. When Pressman overrides him, Picard logs his dissent in the ship’s log—a quiet but defiant act of record—before reluctantly executing the order. His posture and measured tone mask his tension, but his insistence on protocol and safety underscores his role as the crew’s ethical anchor.
- • To prevent unnecessary risk to the *Enterprise* and crew by advocating for safer alternatives (e.g., shuttle mission).
- • To formally document his objections to Pressman’s order, preserving a record of ethical dissent for potential future accountability.
- • Starfleet’s principles—including the Prime Directive and treaty obligations—must be upheld, even when challenged by superior officers.
- • Pressman’s authority, while legally valid, is morally questionable and could lead to catastrophic consequences for the crew and Federation.
Neutral, with a subtle undercurrent of curiosity about the crew’s emotional responses to the situation. Data does not experience conflict but is acutely aware of the tension between Picard and Pressman.
Data provides precise, risk-assessed analysis of the asteroid’s chasm, warning of theoretical gravimetric and magnetic fluctuations. When Picard logs his dissent, Data notes it in the ship’s log without judgment. He then plots the course into the chasm under Picard’s orders, executing the maneuver with mechanical efficiency. His neutral tone and lack of emotional reaction underscore the crew’s internal conflict, serving as a foil to the human drama unfolding around him.
- • To provide accurate, data-driven assessments of the risks involved in the maneuver.
- • To comply with Picard’s orders without question, ensuring the *Enterprise*’s systems are optimized for the high-risk descent.
- • The crew’s emotional reactions, while interesting, do not alter the objective facts of the situation.
- • Pressman’s authority, as a superior officer, must be respected, even if his methods are ethically ambiguous.
Paralyzed by conflicted loyalty, oscillating between nostalgia for his time under Pressman and allegiance to Picard’s leadership. His silence speaks volumes—he is neither fully supportive nor openly rebellious.
Riker stands beside Pressman at Data’s station, initially questioning the feasibility of a shuttle mission but falling silent as Pressman asserts his authority. He complies with Picard’s Yellow Alert orders—raising shields and adjusting inertial dampers—without vocalizing his reservations. His physical presence near Pressman suggests lingering loyalty, but his lack of intervention or support for Picard reveals his internal struggle between past mentorship and present duty.
- • To avoid escalating the tension between Picard and Pressman, potentially preserving crew unity.
- • To ensure the *Enterprise*’s safety by complying with Yellow Alert protocols, even if the mission itself is ethically dubious.
- • Pressman’s experience and past mentorship grant him a degree of trust, but his methods are increasingly questionable.
- • Picard’s leadership is the moral compass of the *Enterprise*, and blindly following Pressman could undermine that.
Detached but alert, focusing on his duties rather than the moral dilemma. His Klingon honor code is satisfied by following orders, but his Starfleet training ensures he remains vigilant for threats.
Worf remains at Tactical, monitoring Romulan sensor range and alert status. He does not directly participate in the chasm decision but ensures the bridge is operationally ready for Yellow Alert. His presence is a silent but steadying force, reinforcing the chain of command and providing tactical oversight without emotional investment in the conflict.
- • To maintain the *Enterprise*’s defensive readiness during the high-risk maneuver.
- • To ensure all tactical systems (shields, sensors, weapons) are operational in case of Romulan interference or unforeseen hazards.
- • The chain of command must be respected, even when orders are ethically ambiguous.
- • Pressman’s authority as a superior officer outweighs personal or moral reservations in this context.
Objects Involved
Significant items in this scene
The Enterprise’s maneuvering thrusters are the physical means by which Pressman’s order is executed, transforming abstract authority into concrete action. Data engages the thrusters from the bridge helm console, using controlled bursts to guide the ship into the narrow chasm. The thrusters’ hum under Yellow Alert conditions creates an auditory backdrop to the tension, while their precise adjustments—countering gravimetric fluctuations and magnetic hazards—highlight the high-stakes nature of the maneuver. The thrusters’ role is both functional (enabling the descent) and symbolic (embodying the crew’s compliance with Pressman’s directive despite their reservations).
The Okudagram schematic of the asteroid’s interior serves as a visual and tactical focal point for the conflict between Pressman and Picard. Pressman uses it to justify his order, pointing directly at the chasm to emphasize its feasibility. Data manipulates the schematic to project it onto the main viewer, transforming it from a passive data display into an active tool for the Enterprise’s descent. The schematic’s bright resonance signature—indicating the Pegasus’s location—symbolizes the mission’s core objective and the ethical dilemma it presents: the crew’s loyalty to Starfleet’s principles versus the imperative to retrieve the lost ship.
Picard’s entry into the ship’s log—‘this action is being taken over my explicit objections’—is a quiet but defiant act of institutional pushback. The log serves as both a record of dissent and a potential future accountability tool, preserving Picard’s moral stance for posterity. Data’s neutral confirmation (‘It is so noted.’) underscores the formality of the process, while the log’s digital timestamp captures the moment’s tension: Yellow Alert conditions, crew compliance under protest, and the unspoken question of who will be held responsible if the maneuver fails. The log’s role here is symbolic, representing the tension between individual conscience and institutional authority.
Location Details
Places and their significance in this event
The asteroid’s deep chasms serve as both a physical obstacle and a narrative crucible for the crew’s moral dilemma. The jagged fissures, wide enough to accommodate the Enterprise, symbolize the fractures in the crew’s unity and the perilous path Pressman is forcing them to take. The chasm’s resonance signature—echoing the Pegasus’s warp core—acts as a siren call, drawing the crew into ethical ambiguity. As the Enterprise descends, the chasm’s looming presence on the viewscreen amplifies the tension, transforming the location from a passive backdrop into an active antagonist in the story. The crew’s compliance with the maneuver is a metaphorical descent into moral compromise, mirroring the ship’s physical descent into the asteroid.
Organizations Involved
Institutional presence and influence
Starfleet’s institutional presence is palpable in this event, manifesting through the chain of command, the ship’s log, and the crew’s adherence to protocol—even under protest. Pressman’s authority as an admiral represents Starfleet’s hierarchical structure, while Picard’s logged dissent highlights the organization’s formal channels for ethical accountability. The Enterprise’s compliance with Yellow Alert protocols, despite the crew’s reservations, underscores Starfleet’s emphasis on operational discipline. However, the event also exposes the organization’s moral ambiguities, as Pressman’s orders prioritize mission success over treaty obligations and crew safety, revealing a tension between Starfleet’s ideals and its pragmatic realities.
The Romulans’ presence looms as an external threat, shaping the crew’s urgency and Pressman’s justification for the high-risk maneuver. While not physically present on the bridge, their existence as a monitoring force—positioned off the Enterprise’s bow and scanning the asteroid—creates a sense of imminent danger. Pressman cites the Romulans’ exclusive cloaking technology as a 60-year tactical edge, framing the Pegasus’s retrieval as a necessity to maintain Federation security. The Romulans’ role in this event is indirect but critical, serving as the catalyst for Pressman’s uncompromising stance and the crew’s moral dilemma.
Narrative Connections
How this event relates to others in the story
"Picard proposes options for approaching and retrieving the ship, but Pressman overrides him at every turn."
"Worf alerts of the approach, and Picard and the crew discuss ingress approach options, deciding upon shuttle or direct flight."
"Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers, and defying Picard."
"Picard proposes options for approaching and retrieving the ship, but Pressman overrides him at every turn."
"Picard's decision to enter the asteroid causes the Enterprise crew to navigate the asteroid's winding tunnels, encountering magnetic field shifts during their journey."
"Picard's decision to enter the asteroid causes the Enterprise crew to navigate the asteroid's winding tunnels, encountering magnetic field shifts during their journey."
"Following Picard's orders, the Enterprise navigates the asteroid's winding tunnels, encountering magnetic field shifts."
"Following Picard's orders, the Enterprise navigates the asteroid's winding tunnels, encountering magnetic field shifts."
"Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers, and defying Picard."
Key Dialogue
"PRESSMAN: Sounds like the best solution is to take the *Enterprise* in."
"PICARD: Mister Data, please note in the ship's log that this action is being taken over my explicit objections."
"PRESSMAN: (smooth) I've made my decision. Prepare to take the *Enterprise* in, Captain. That's an order."