Picard gambles runabout to sever beam
Plot Beats
The narrative micro-steps within this event
Picard, under pressure, inquires about moving the Enterprise, but Riker reports that the feedback from the transfer beam would destroy the ship.
Picard gets an idea to use the Runabout and orders Riker to patch him into its navigational control, which Riker does amidst the ship shaking.
Picard brings the Runabout in, presumably to carry out his plan to sever to power transfer beam and save the Enterprise.
Who Was There
Characters present in this moment
Steely resolve masking deep concern. His exterior is composed, but the stakes are palpable—every movement is deliberate, every word measured. There’s a quiet intensity, as if he’s already accepted the potential cost of failure.
Picard assesses the situation with rapid strategic calculation, realizing the Enterprise cannot evade the beam without self-destruction. He rushes to Tactical, barking orders to Riker to patch him into the Runabout’s controls. His voice is low but commanding as he remotely pilots the vessel into the beam, his posture rigid with concentration. The bridge crew’s tension mirrors his own—this is a gamble with no room for error.
- • Sever the beam’s connection to the *Enterprise* at all costs
- • Protect the crew from temporal destabilization
- • The Runabout is the only viable tool to disrupt the beam
- • Leadership requires personal sacrifice when necessary
Objects Involved
Significant items in this scene
The Tactical consoles on the Enterprise bridge are the nerve center of Picard’s maneuver. Riker uses them to patch Picard into the Runabout’s controls, while Picard himself inputs the commands to remotely pilot the vessel. The consoles flash with alerts, their readouts critical for assessing the beam’s feedback risks. Their functionality is essential—without them, the Runabout could not be controlled, and the Enterprise would remain trapped.
The Destructive Transfer Beam is the antagonistic force locking the Enterprise and Romulan warbird in temporal stasis. It pulses with destructive energy, threatening to tear the Enterprise apart if the ship moves. Picard’s gambit—ramming the Runabout into the beam—severs its connection, freeing both vessels. The beam’s presence looms over the scene, a tangible threat that forces the crew into desperate measures. Its disruption is the turning point, but the temporal instability it caused lingers as a broader consequence.
The Runabout serves as the critical tool in Picard’s high-risk maneuver. Remotely piloted from the Enterprise’s Tactical console, it is deliberately crashed into the Romulan transfer beam. The collision severs the beam’s connection, freeing the Enterprise from temporal stasis but at the cost of the Runabout’s destruction. Its role is both functional (disrupting the beam) and symbolic (representing Picard’s willingness to sacrifice resources for the greater good).
Organizations Involved
Institutional presence and influence
Starfleet is represented through the Enterprise crew’s adherence to protocol, improvisational problem-solving, and collective action under crisis. Picard and Riker’s rapid coordination reflects Starfleet’s training and values—prioritizing the ship’s survival while accepting calculated risks. The organization’s influence is seen in the crew’s trust in Picard’s leadership and their willingness to follow his unconventional orders, even when they involve sacrificing a Runabout.
Narrative Connections
How this event relates to others in the story
"The realization that the Enterprise will be destroyed if Picard does nothing is countered by the realization the runabout can save the Enterprise. Picard then flies the Runabout between the Enterprise and the Romulan ship, severing the transfer beam and saving the ship at the cost of the Runabout and the Romulan Warbird."
Key Dialogue
"PICARD: Can we move the ship?"
"RIKER: The feedback from the transfer beam would tear us apart."
"PICARD: I'm bringing the Runabout in..."