Pressman forces Enterprise into asteroid
Plot Beats
The narrative micro-steps within this event
Picard hesitates to risk the ship, but Pressman overrides his objections and orders the Enterprise to enter the chasm, asserting his authority. Defiantly, Picard instructs Data to log his explicit disagreement with the order.
Picard, proceeding with caution, orders the ship to Yellow Alert and directs Data to plot a course into the chasm using only maneuvering thrusters. The Enterprise begins its dangerous journey into the asteroid.
Who Was There
Characters present in this moment
Determined and self-assured, with a subtle undercurrent of urgency—he knows the stakes and is unwilling to entertain delays or dissent.
Pressman dominates the scene with smooth, commanding authority, cutting off Picard’s objections with a calm but firm ‘That’s an order.’ He directs Data to display the asteroid chasm on the main viewer, dismissing warnings about gravimetric hazards with the confidence of a man who has already made up his mind. His physical presence—leaning over Data’s station, pointing to the schematic, then standing tall as he issues the order—projects unshakable resolve. Pressman’s tone is paternalistic toward Riker, his former first officer, but his demeanor toward Picard is that of a superior asserting control. This is a man who believes the ends justify the means, and his willingness to risk the Enterprise reflects his prioritization of Federation security over individual lives or ethical niceties.
- • To secure the *Pegasus* and its cloaking technology at all costs, even if it means overriding Starfleet protocol and risking the *Enterprise*.
- • To reassert his authority over Picard and the crew, leveraging his rank and past relationship with Riker to ensure compliance.
- • The *Pegasus*’s cloaking technology is too valuable to leave behind, and the Romulan threat justifies extraordinary measures.
- • Picard’s objections, while understandable, are an obstacle to a mission-critical objective and must be overridden for the greater good.
Resigned but tense, with a simmering undercurrent of frustration at Pressman’s overreach, masked by professional composure.
Picard enters the bridge from the Ready Room, immediately assessing the Romulan threat before shifting focus to the Pegasus’s location. He proposes a shuttlecraft as a safer alternative to Pressman’s risky plan, but when Pressman overrides him with a direct order, Picard logs his dissent in the ship’s log—a quiet but defiant act of record. His compliance is disciplined but tense, as he sets Yellow Alert and orders a cautious approach using maneuvering thrusters, his posture and measured tone betraying his reluctance. Picard’s leadership is tested: he must balance Starfleet protocol with the operational urgency Pressman imposes, all while the crew watches his response as a barometer of their own moral compass.
- • To protect the *Enterprise* and crew from unnecessary risk by advocating for safer alternatives (e.g., shuttlecraft).
- • To formally document his objections in the ship’s log, ensuring a record of dissent for potential future accountability or ethical review.
- • Starfleet protocol and crew safety must take precedence over operational urgency, especially when the risks are uncharted.
- • Admiral Pressman’s authority, while legally valid, is ethically questionable in this context, and his methods may compromise the Federation’s principles.
Neutral, with no visible emotional response—his function is to provide data and execute orders, regardless of their ethical implications.
Data provides the technical and logistical backbone of the event, analyzing the Pegasus’s resonance signature, warning of potential hazards, and plotting the course into the asteroid. His delivery is precise and unemotional, but his warnings carry weight due to his reputation for accuracy. When Picard asks him to log the dissent, Data complies without comment, his actions serving as a neutral record of the crew’s divided loyalties. He then executes the maneuver using maneuvering thrusters, his focus entirely on the technical execution of the order. Data’s role here is that of the impartial machine, but his presence underscores the human stakes of the decision—his warnings go unheeded, yet he facilitates the action nonetheless.
- • To ensure the *Enterprise*’s safe navigation into the asteroid chasm by accounting for all known hazards and plotting the most stable course.
- • To accurately document Picard’s objections in the ship’s log, fulfilling his role as a neutral recorder of events.
- • The mission parameters, as defined by Pressman, must be followed, even if they conflict with Picard’s preferences.
- • His role is to provide information and execute commands, not to judge their moral validity.
Conflicted and internally fractured, oscillating between loyalty to Pressman and guilt over his silence in the face of Picard’s dissent.
Riker stands near Pressman and Data at an aft station, initially questioning the feasibility of transporting through the asteroid and expressing surprise at Pressman’s suggestion to take the Enterprise into the chasm. His silence during Picard’s protest and subsequent compliance with the Yellow Alert orders is deafening, signaling his internal conflict. Physically, he moves to the command area with Picard, executing tactical protocols (shields up, inertial dampers to maximum) with mechanical precision, but his body language—rigid, avoiding eye contact—reveals his turmoil. Riker is caught between his loyalty to Pressman (his former captain) and his duty to Picard and Starfleet, a conflict that renders him momentarily paralyzed by indecision.
- • To navigate the operational demands of the mission without openly challenging Pressman, preserving his professional relationship.
- • To subtly align with Picard’s cautious approach by enforcing Yellow Alert protocols, mitigating some of the risk Pressman is imposing.
- • Pressman’s plan is reckless but may be necessary to recover the *Pegasus* and its secrets, justifying his compliance.
- • Picard’s objections are valid, and his dissent should be respected, but Riker lacks the moral clarity to voice his own opposition.
Neutral and focused, with no visible internal conflict—his role is operational, not ethical.
Worf remains at Tactical, monitoring the Romulan sensor range and providing updates, but his role in this event is limited to tactical support. He does not engage in the debate over entering the asteroid, instead focusing on his duties with Klingon-like discipline. His presence on the bridge serves as a silent counterpoint to the human moral dilemmas unfolding—his loyalty to Picard is unwavering, but his Klingon honor code does not require him to challenge Pressman’s authority directly. Worf’s neutrality here underscores the personal nature of the conflict between Picard, Riker, and Pressman, as he operates within the chain of command without emotional investment in the ethical debate.
- • To ensure the *Enterprise*’s tactical systems are optimized for the maneuver into the asteroid, prioritizing structural integrity and sensor coverage.
- • To maintain situational awareness of the Romulan threat, even as the crew’s attention shifts to the *Pegasus*.
- • Pressman’s order, while risky, is a command decision that does not require Worf’s personal judgment to execute.
- • Picard’s leadership is the ultimate authority on the *Enterprise*, but Worf’s role is to support, not question, unless directly ordered to do so.
Objects Involved
Significant items in this scene
The Enterprise’s maneuvering thrusters are the physical means by which Pressman’s risky order is executed, transforming abstract authority into concrete action. Data engages them from the bridge helm console, firing controlled bursts to guide the ship into the narrow asteroid chasm. The thrusters operate as a counterbalance to the gravitational and magnetic hazards Data has warned about, their precise adjustments enabling a cautious descent despite the crew’s reservations. Their activation marks the point of no return—the moment when the Enterprise commits to the perilous path, and the crew’s compliance under protest becomes irreversible. The thrusters symbolize the tension between human agency and mechanical necessity: they are the tools that make Pressman’s will manifest, but they also bear the weight of the crew’s ethical dilemmas, as their use could mean the difference between success and catastrophe.
The Okudagram schematic of the asteroid’s interior serves as the visual catalyst for Pressman’s gambit, its bright point tracing the Pegasus’s resonance signature deep within the chasm. Pressman uses it as a tactical tool, pointing directly to the graphic to demand entry into the asteroid, effectively weaponizing data to justify his order. The schematic shifts from a passive display to an active agent in the conflict, as Data projects it onto the main viewer at Pressman’s command. Its role is twofold: it provides the Enterprise crew with a clear visual of the perilous path ahead, while also symbolizing the irresistible pull of the Pegasus’s secrets—a siren call that overrides caution and protocol. The schematic’s presence underscores the tension between discovery and destruction, as the crew is forced to confront the physical and ethical risks of the maneuver.
Picard’s entry into the ship’s log of his explicit objections to Pressman’s order is a quiet but powerful act of defiance, serving as both a legal and ethical record of the crew’s divided loyalties. The log functions as a moral anchor in a moment of operational chaos, ensuring that Picard’s dissent is preserved for future review or accountability. Its activation is a deliberate choice—Picard does not raise his voice or challenge Pressman directly, but he ensures that his opposition is documented, creating a paper trail that could later be used to justify his actions or critique Pressman’s. The log’s digital nature makes it immutable and official, reinforcing Picard’s role as the moral compass of the Enterprise even in the face of overwhelming authority. Its inclusion in this event highlights the tension between institutional protocol and individual conscience.
Location Details
Places and their significance in this event
The Enterprise’s main bridge functions as the command hub where the moral and operational conflict unfolds, its familiar layout serving as a stage for the clashing wills of Picard, Pressman, and Riker. The bridge’s design—with its aft stations, tactical consoles, and main viewer—facilitates both the technical execution of the maneuver and the interpersonal dynamics that drive the event. It is a space of authority, where rank and protocol dictate actions, but also a space of tension, as the crew grapples with the ethical implications of Pressman’s order. The bridge’s role is to amplify the stakes: every order given, every objection raised, and every silent compliance is amplified by the weight of the ship’s history and the crew’s shared purpose. As the Enterprise prepares to enter the chasm, the bridge becomes a microcosm of the larger conflict between duty and conscience.
Organizations Involved
Institutional presence and influence
Starfleet’s influence is palpable in this event, manifesting through the chain of command, institutional protocols, and the ethical dilemmas that arise from Pressman’s order. The organization’s presence is felt in Picard’s adherence to protocol (logging his dissent, setting Yellow Alert), Riker’s conflicted loyalty to both Pressman and Starfleet’s principles, and Data’s neutral execution of commands. Starfleet’s rules and values are the unseen third party in the room, shaping the crew’s actions and reactions. Pressman’s authority, while legally valid, is ethically questionable from a Starfleet perspective, creating a tension between individual ambition and institutional integrity. The event highlights Starfleet’s struggle to balance security imperatives (the Pegasus’s cloaking technology) with ethical constraints (the Treaty of Algeron and crew safety).
The Romulans’ presence looms as an external threat that justifies Pressman’s urgency but also underscores the ethical risks of his plan. Their discovery of the Pegasus wreckage and their warbird’s position in the Devolin system create a sense of imminent danger, pressuring the crew to act quickly. However, the Romulans also serve as a symbolic counterpoint to Pressman’s methods—their exclusive cloaking technology, enabled by the Federation’s Treaty of Algeron compliance, is the very reason the Pegasus’s secrets are so valuable. The Romulans’ threat is both a catalyst (driving the mission) and a cautionary tale (warning of the consequences of unchecked ambition). Their influence in this event is indirect but critical: they are the reason Pressman is willing to take such risks, and their existence highlights the moral ambiguity of the Federation’s own technological pursuits.
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'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."
"Picard proposes options for approaching and retrieving the ship, but Pressman overrides him at every turn."
"Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers, and defying Picard."
"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."
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."