Fabula
S7E12 · The Pegasus
S7E12
· The Pegasus

Pressman forces Enterprise into asteroid chasm

Admiral Pressman overrides Captain Picard’s objections and orders the Enterprise into a perilous asteroid chasm to retrieve the Pegasus. After Data warns of the maneuver’s untested risks—including potential gravimetric fluctuations and structural instability—Picard attempts to propose alternatives, including a shuttle mission. Pressman dismisses these options, asserting his authority with a calm but firm directive: 'Prepare to take the Enterprise in, Captain. That’s an order.' Picard logs his dissent in the ship’s log, then reluctantly executes the maneuver under Yellow Alert, with Riker and Data complying despite their reservations. The scene escalates tension between Pressman’s unyielding command and the crew’s growing unease, foreshadowing the moral and operational stakes of the Pegasus mission. Riker’s silence during the exchange underscores his internal conflict, as he grapples with loyalty to Pressman and the Federation’s ethical boundaries. The Enterprise’s descent into the chasm marks a turning point, where institutional authority clashes with personal judgment, setting the stage for the revelation of the Pegasus’s illegal cloaking device.

Plot Beats

The narrative micro-steps within this event

2

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.

curiosity to concern

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.

hesitation to determination

Who Was There

Characters present in this moment

5

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.

Goals in this moment
  • 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.
Active beliefs
  • 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.
Character traits
Authoritative and decisive Unapologetic in bending rules for perceived greater good Charismatic but manipulative, leveraging past relationships (e.g., with Riker) Strategic, prioritizing mission success over ethical niceties
Follow Erik Pressman's journey

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.

Goals in this moment
  • 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.
Active beliefs
  • 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.
Character traits
Defiant yet disciplined Protective of crew and ship Diplomatic under pressure Unwavering in moral principles
Follow Jean-Luc Picard's journey

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.

Goals in this moment
  • 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.
Active beliefs
  • 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.
Character traits
Logically impartial, providing facts without bias Efficient in executing orders, regardless of personal or ethical implications Observant of crew dynamics, though unable to fully grasp their emotional undercurrents Reliable in high-pressure situations, offering technical solutions to moral dilemmas
Follow Data's journey

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.

Goals in this moment
  • 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.
Active beliefs
  • 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.
Character traits
Conflict-avoidant in high-stakes moments Loyal to both Picard and Pressman, creating internal division Pragmatic in crisis, prioritizing immediate action over debate Emotionally restrained, masking turmoil behind professionalism
Follow William Riker's journey
Supporting 1

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.

Goals in this moment
  • 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.
Active beliefs
  • 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.
Character traits
Unwaveringly professional Tactically focused, prioritizing ship safety Neutral in command disputes unless directly ordered to intervene Disciplined under pressure, embodying Klingon-Starfleet duality
Follow Worf's journey

Objects Involved

Significant items in this scene

3
USS Enterprise-D Maneuvering Thrusters

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).

Before: Idle, with minimal power output. The thrusters are …
After: Actively engaged, firing controlled bursts to navigate the …
Before: Idle, with minimal power output. The thrusters are in standby mode, ready for standard maneuvers but not yet engaged for the high-risk chasm descent.
After: Actively engaged, firing controlled bursts to navigate the asteroid’s chasm. The thrusters are operating at elevated power levels, countering gravitational and magnetic anomalies as the Enterprise descends. Their status is now tied to the ship’s structural integrity and the success of the mission.
Enterprise-D Bridge Okudagram: Asteroid Chasm Schematic (Pegasus Resonance Trace)

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.

Before: Displayed on Data’s station, showing the asteroid’s internal …
After: Projected onto the main viewer, now an active …
Before: Displayed on Data’s station, showing the asteroid’s internal structure with a bright point marking the Pegasus’s resonance signature. Passive but critical for the crew’s understanding of the terrain.
After: Projected onto the main viewer, now an active navigational aid guiding the Enterprise into the chasm. The schematic’s data is integrated into the ship’s course-plotting systems, and its visual prominence reinforces the urgency of the maneuver.
USS Enterprise Ship's Log: Picard's Dissent to Asteroid Chasm Maneuver

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.

Before: Inactive, awaiting new entries. The ship’s computer core …
After: Updated with Picard’s formal objection, now a permanent …
Before: Inactive, awaiting new entries. The ship’s computer core is ready to record Picard’s dissent, but the log itself is a blank slate until this moment.
After: Updated with Picard’s formal objection, now a permanent part of the Enterprise’s official record. The entry is time-stamped and stored in the ship’s computer core, where it could later be retrieved as evidence of ethical dissent or used in a court-martial proceeding.

Location Details

Places and their significance in this event

1
Romulan Trap Asteroid (Cavern Chamber)

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.

Atmosphere Oppressive and foreboding, with a sense of irreversible commitment. The chasm’s darkness on the viewscreen …
Function A high-stakes obstacle course and symbolic threshold, marking the crew’s crossing from ethical certainty into …
Symbolism Represents the crew’s descent into moral compromise, where institutional loyalty clashes with personal ethics. The …
Access Restricted to the Enterprise and its crew, with Romulan warbirds monitoring the asteroid’s exterior. The …
The viewscreen’s image of the chasm looming larger as the Enterprise approaches, casting a shadow over the bridge. The hum of maneuvering thrusters and the occasional beep of alert systems, creating a soundscape of controlled tension. The Okudagram schematic’s bright resonance signature, a visual anchor for the crew’s focus and a reminder of their objective. The dimmed bridge lighting, emphasizing the gravity of the moment and the crew’s collective unease.

Organizations Involved

Institutional presence and influence

2
Starfleet

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.

Representation Through institutional protocol (e.g., chain of command, ship’s log), collective action of members (crew compliance), …
Power Dynamics Starfleet’s authority is exercised through Pressman’s unyielding orders, which override Picard’s objections and the crew’s …
Impact The event highlights the tension between Starfleet’s ethical principles and its pragmatic needs, foreshadowing the …
Internal Dynamics The scene reveals a fracture within Starfleet’s ranks, where Pressman’s unyielding command style clashes with …
To retrieve the Pegasus and its cloaking technology, justifying the bending of Starfleet protocols in the name of Federation security. To maintain the chain of command and operational discipline, even when orders are ethically questionable, ensuring the crew’s compliance with superior officers. Hierarchical authority (Pressman’s rank as admiral), Institutional protocol (ship’s log, Yellow Alert procedures), Collective compliance (crew adherence to orders despite reservations), Symbolic power (Starfleet’s reputation and the weight of its history).
Romulan Star Empire Forces

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.

Representation Via the threat they pose (monitoring the asteroid, scanning for the Pegasus) and the strategic …
Power Dynamics The Romulans exert indirect power over the Enterprise crew by forcing them into a high-stakes …
Impact The Romulans’ presence amplifies the stakes of the Pegasus mission, turning it into a race …
To maintain their technological superiority by preventing the Federation from accessing the Pegasus’s cloaking device. To monitor Starfleet’s movements and exploit any perceived weakness or ethical lapse (e.g., the Enterprise’s descent into the chasm). Tactical pressure (positioning a warbird to monitor the asteroid), Technological leverage (exclusive cloaking technology as a strategic advantage), Perceived threat (creating urgency and justifying Pressman’s actions).

Narrative Connections

How this event relates to others in the story

What led here 3
Causal

"Picard proposes options for approaching and retrieving the ship, but Pressman overrides him at every turn."

Pressman forces Enterprise into asteroid
S7E12 · The Pegasus
NARRATIVELY_FOLLOWS

"Worf alerts of the approach, and Picard and the crew discuss ingress approach options, deciding upon shuttle or direct flight."

Picard’s Authority Overruled by Blackwell
S7E12 · The Pegasus
NARRATIVELY_FOLLOWS

"Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers, and defying Picard."

Pressman forces Enterprise into asteroid
S7E12 · The Pegasus
What this causes 6
Causal

"Picard proposes options for approaching and retrieving the ship, but Pressman overrides him at every turn."

Pressman forces Enterprise into asteroid
S7E12 · The Pegasus
Causal

"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."

Pressman enforces restricted salvage operation
S7E12 · The Pegasus
Causal

"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."

Pegasus discovered fused in asteroid
S7E12 · The Pegasus
NARRATIVELY_FOLLOWS

"Following Picard's orders, the Enterprise navigates the asteroid's winding tunnels, encountering magnetic field shifts."

Pegasus discovered fused in asteroid
S7E12 · The Pegasus
NARRATIVELY_FOLLOWS

"Following Picard's orders, the Enterprise navigates the asteroid's winding tunnels, encountering magnetic field shifts."

Pressman enforces restricted salvage operation
S7E12 · The Pegasus
NARRATIVELY_FOLLOWS

"Pressman proposes taking the Enterprise into the asteroid itself, despite the potential dangers, and defying Picard."

Pressman forces Enterprise into asteroid
S7E12 · The Pegasus

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."