Star Trek The Next Generation
S6E25
· Timescape

Picard gambles runabout to sever beam

With the Enterprise trapped in temporal stasis and a Romulan warbird frozen alongside it, Picard realizes the alien power beam cannot be evaded—moving the ship would trigger its destruction. In a high-stakes maneuver, he remotely pilots a Runabout into the beam’s path, severing its connection and saving the Enterprise at the cost of exposing the crew to escalating temporal instability. The act underscores Picard’s willingness to gamble the ship’s safety for a calculated solution, deepening the stakes of the time-skipping crisis. The bridge crew’s tension mounts as Picard executes the risky plan, with Riker confirming the ship’s vulnerability to feedback from the beam. The scene hinges on Picard’s decisive leadership under pressure, where his strategic improvisation becomes the only viable path forward despite the potential loss of the Runabout—and himself—if the maneuver fails. The moment also foreshadows the broader consequences of temporal disruption, as the crew’s survival now depends on the success of this desperate gamble.

Plot Beats

The narrative micro-steps within this event

3

Picard, under pressure, inquires about moving the Enterprise, but Riker reports that the feedback from the transfer beam would destroy the ship.

urgency to hopelessness

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.

hopelessness to determination

Picard brings the Runabout in, presumably to carry out his plan to sever to power transfer beam and save the Enterprise.

tension to action

Who Was There

Characters present in this moment

1
William Riker
Bridge Communications Relay
 primary

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.

Goals in this moment
  • • Sever the beam’s connection to the *Enterprise* at all costs
  • • Protect the crew from temporal destabilization
Active beliefs
  • • The Runabout is the only viable tool to disrupt the beam
  • • Leadership requires personal sacrifice when necessary
Character traits
Calculating and bold Willing to take personal risk for the crew Authoritative yet collaborative Adaptable under extreme pressure
Follow William Riker's journey

Objects Involved

Significant items in this scene

3
Enterprise Main Bridge Tactical Consoles

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.

Before: Functional but under strain, displaying red alerts and …
After: Still operational but potentially damaged from the temporal …
Before: Functional but under strain, displaying red alerts and scorch marks from the temporal anomaly. The Conn panel is active, awaiting Riker’s input to establish the patch.
After: Still operational but potentially damaged from the temporal stress. The consoles remain active, though their readouts may reflect the aftermath of the Runabout’s collision with the beam.
Destructive Transfer Beam (Enterprise-Romulan Warbird)

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.

Before: Active and fully engaged, locking the Enterprise and …
After: Severed and deactivated, no longer connected to the …
Before: Active and fully engaged, locking the Enterprise and warbird in stasis. Its energy signature is visible on the bridge viewscreen, pulsing ominously.
After: Severed and deactivated, no longer connected to the Enterprise or warbird. The temporal stasis is broken, but the broader spacetime anomaly persists.
Picard’s Runabout (USS *Enterprise*-E, *Timescape* Mission)

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

Before: Docked and operational, ready for deployment. Its navigational …
After: Destroyed upon impact with the transfer beam, its …
Before: Docked and operational, ready for deployment. Its navigational controls are patched into the Enterprise’s Tactical console, awaiting Picard’s remote command.
After: Destroyed upon impact with the transfer beam, its wreckage likely scattered in the temporal anomaly. The Runabout is no longer functional or recoverable.

Organizations Involved

Institutional presence and influence

1
Starfleet

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.

Representation Via institutional protocol (e.g., chain of command, emergency procedures) and collective action (e.g., crew coordination, …
Power Dynamics Exercising authority over the situation through Picard’s command decisions, but operating under the constraint of …
Impact The event reinforces Starfleet’s ethos of adaptability and sacrifice, showing how its principles are applied …
Internal Dynamics None explicitly shown, but the scene implies a hierarchy where Picard’s authority is unquestioned, and …
Preserve the Enterprise and its crew from the temporal threat Disrupt the Romulan transfer beam using available resources (e.g., the Runabout) Through Picard’s leadership and decision-making authority Via the crew’s technical expertise and adherence to emergency protocols By leveraging Starfleet-trained improvisation under extreme conditions

Narrative Connections

How this event relates to others in the story

What this causes 1
Causal

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

Picard sacrifices runabout to sever time lock
S6E25 · Timescape

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