Fabula
S5E18 · Cause and Effect

Collision Course and Catastrophic Impact

The Enterprise crew, already grappling with unexplained auditory anomalies and temporal distortions, faces an immediate existential threat when an unidentified starship materializes on a direct collision course. The bridge erupts into controlled chaos as Picard and his senior staff scramble for solutions, with Riker proposing a desperate decompress maneuver and Data advocating for a tractor beam attempt. Despite Worf’s precise execution, the ship’s systems fail catastrophically—shields, helm, and inertial dampers all offline—leaving the crew powerless to alter their fate. The collision is inevitable, and the subsequent impact breaches the starboard nacelle, triggering a cascading failure of critical systems. As the ship spirals toward destruction, Picard orders an emergency core shutdown and ultimately abandons ship, marking the crew’s repeated failure to break the temporal loop. The scene underscores the futility of their efforts, the inescapable nature of the causality trap, and the high stakes of their predicament, where even their most calculated actions lead to the same devastating outcome.

Plot Beats

The narrative micro-steps within this event

2

Riker suggests decompressing the shuttlebay as a desperate measure, but Data recommends using the tractor beam to alter the other ship's trajectory, and Picard orders Worf to engage the tractor beam.

panic to desperate hope ['Bridge']

The Enterprise collides with the other ship despite Worf's attempt to use the tractor beam.

hope to catastrophe ['Bridge']

Who Was There

Characters present in this moment

10

Tense, efficient, and alarmed—her Bajoran independence clashes with the loop's inescapable nature, leaving her frustrated but undeterred.

Ro is at the helm, her hands flying over the controls as she confirms the thrusters and helm are unresponsive. Her voice is tense but efficient—'The helm's not responding!'—as she assists with damage control. She grips the console, her Bajoran resilience evident as the ship spirals toward destruction. Her actions are precise, but the loop's repetition leaves her with a sense of helplessness, a reminder that even her skills cannot alter the outcome.

Goals in this moment
  • Report system failures accurately to guide the crew's response
  • Assist with damage control and evacuation efforts
Active beliefs
  • Her technical skills can help mitigate the damage, even if they cannot prevent the collision
  • The crew's survival depends on clear communication and quick action
Character traits
Efficient under pressure Tense but focused Quick to report failures and assist with damage control Resilient in the face of repeated failure
Follow Alyssa Ogawa's journey

Worried, tense, and professional—her medical instincts kick in, but she is acutely aware of the futility of her role in this moment.

Beverly works a nearby console, her fingers flying as she pulls up casualty reports. Her medical perspective is secondary to the immediate crisis, but her presence grounds the chaos with professional urgency. She reacts with worry to Worf's sensor readings, her voice steady as she relays the damage—'Casualty reports coming in from all over the ship...'—but her eyes betray her fear. She is a healer in a situation where healing is impossible, a reminder of the crew's vulnerability.

Goals in this moment
  • Assess and communicate the extent of the damage and casualties
  • Support the crew with medical expertise, even in the face of inevitable destruction
Active beliefs
  • Her medical knowledge can mitigate suffering, even if it cannot prevent the loop
  • The crew's well-being is her priority, no matter the circumstances
Character traits
Professionally urgent in crises Empathetic to the crew's suffering Quick to assess and communicate damage Grounded by medical training amid chaos
Follow Ro Laren's journey

Antagonistic, indifferent—its actions (or lack thereof) are the direct cause of the collision, leaving the Enterprise crew powerless.

The unidentified starship emerges from the distortion on a direct collision course, its silence and lack of response adding to the tension. It is an antagonist force, a catalyst for the Enterprise's destruction, and its presence underscores the futility of the crew's efforts. The ship's failure to hail or evade it seals the crew's fate, making it a silent, inexorable harbinger of doom in the temporal loop.

Goals in this moment
  • None (it is an inanimate force of the loop, not an agent with intent)
  • Its emergence and collision are the inevitable result of the temporal distortion
Active beliefs
  • Its presence is a manifestation of the loop's causality
  • It represents the crew's inability to alter their fate
Character traits
Silent and unresponsive Inexorable in its trajectory A catalyst for destruction Symbolic of the loop's inescapable nature
Follow Unnamed Captain's journey

Tense, resolute, and increasingly desperate—his surface calm masks a growing sense of helplessness as the loop's futility becomes undeniable.

Picard stands at the center of the bridge, his posture rigid with command authority as the temporal distortion unfolds. He issues precise orders—'Back us off,' 'Hail them,' 'Mister Worf, make it so'—while absorbing the crew's frantic reports. His voice remains steady, but his eyes betray mounting tension as the collision becomes inevitable. When the ship is struck, he grips the console edge, his knuckles whitening, before delivering the grim order to abandon ship. His leadership is resolute yet increasingly desperate, a man trapped in a loop of failure.

Goals in this moment
  • Prevent the collision through any available means (evasive maneuvers, hailing, tractor beam)
  • Maintain crew morale and order amid cascading failures
Active beliefs
  • Starfleet protocol and quick thinking can overcome even temporal anomalies
  • His crew's survival depends on his ability to adapt to the unknown
Character traits
Decisive under pressure Emotionally contained but internally conflicted Trusts his crew's expertise Accepts the inevitability of failure with grim resolve
Follow Jean-Luc Picard's journey

Calm, analytical, and urgent—his positronic mind processes the data, but the repetition of the loop introduces a subtle tension, a recognition of futility.

Data stands at ops, his fingers flying across the console as he analyzes the distortion and recommends the tractor beam. His voice is calm but urgent—'The vessel is on a collision course. Impact in thirty-six seconds...'—as he processes the ship's failing systems in real-time. When the collision occurs, he delivers the grim assessments: 'The starboard nacelle has sustained a direct impact. We are venting drive plasma.' His analytical precision contrasts with the chaos, but his urgency betrays the stakes. He attempts to eject the core, only to confirm the ejection systems are offline, sealing the ship's fate.

Goals in this moment
  • Use the tractor beam to alter the other ship's trajectory and avoid collision
  • Provide real-time updates on system failures to guide the crew's response
Active beliefs
  • Technical solutions can overcome temporal anomalies if executed perfectly
  • The crew's survival depends on his ability to process and communicate data accurately
Character traits
Analytically precise under pressure Urgency masked by calm delivery Relies on logic even in existential crises Quick to identify and communicate critical failures
Follow Data's journey

Focused, stressed, and determined—his usual optimism is replaced by a grim resolve as the ship's systems collapse around him.

Geordi works frantically at the engineering console, his VISOR flickering as he initiates the emergency core shutdown. His voice is strained—'Inertial dampers failing. We're losing attitude control...'—as he struggles to eject the engine core after the collision. His hands move with desperate precision, but the systems fail one by one, leaving him powerless. His focus is unwavering, a man fighting to save his ship with every tool at his disposal, even as the loop proves unstoppable.

Goals in this moment
  • Initiate emergency core shutdown to prevent a breach
  • Eject the engine core as a last-resort measure to save the ship
Active beliefs
  • Engineering solutions can mitigate even catastrophic failures if acted upon quickly
  • The *Enterprise* is his responsibility, and he will fight for her until the end
Character traits
Highly focused under pressure Determined to the last moment Technically precise but emotionally invested in the ship Quick to adapt to failing systems
Follow Worf's journey

Urgent, focused, and increasingly frustrated—his usual confidence is undermined by the ship's repeated failures, but he channels that energy into action.

Riker stands near Data at ops, his body coiled with urgency as the crisis escalates. He barks orders—'Shields up! Evasive maneuvers!'—and proposes the shuttlebay decompress maneuver, a last-ditch effort to alter the ship's trajectory. His frustration is palpable as the helm and shields fail, and he coordinates damage control post-collision, his voice straining over the alarms. When the core breach is imminent, he issues the evacuation order, his competitive edge sharpened by the stakes. His actions reflect a man who refuses to accept defeat, even as the loop proves inescapable.

Goals in this moment
  • Find a technical or tactical solution to avoid the collision
  • Ensure the crew follows evacuation protocols when all else fails
Active beliefs
  • Innovative thinking can break the loop, even if it defies standard procedure
  • The crew's survival is his responsibility, and he will exhaust every option
Character traits
Quick-thinking and proactive Frustrated by systemic failures Loyal to Picard but willing to challenge protocols Competitive even in life-or-death scenarios
Follow William Riker's journey

Alarmed, urgent, and helpless—her empathic senses amplify the crew's desperation, and she is powerless to alter the outcome.

Troi stands near Picard, her body tensing as the distortion emerges. She senses the impending danger before it's visually confirmed, her empathic warning—'Captain, we have to get out of here now'—cutting through the chaos. Her face pales as the collision occurs, and she grips a console for support, her empathic senses overwhelmed by the crew's fear and the ship's doom. She is a silent witness to the futility, her usual insight rendered useless by the loop's inescapable nature.

Goals in this moment
  • Warn Picard of the immediate danger through her empathic senses
  • Support the crew emotionally during the crisis
Active beliefs
  • Her empathic warnings can sometimes avert disaster, but not this time
  • The loop's repetition is a psychological torment as much as a physical one
Character traits
Empathically attuned to the crew's fear Quick to recognize existential threats Helpless in the face of the loop's repetition Uses her abilities to urge immediate action
Follow Beverly Crusher's journey

Focused, disciplined, and frustrated—his Klingon warrior's pride is wounded by the repeated failure, but he channels it into action.

Worf stands at tactical, his Klingon discipline evident as he reports the distortion and confirms the shields and helm are inoperative. He attempts to engage the tractor beam on Picard's orders, his voice a growl of frustration as the systems fail. His body tenses with each report of failure—'Shields inoperative! The helm's not responding!'—and he watches the collision unfold with disciplined fury. His actions are precise, but the loop's repetition tests his honor and his patience, leaving him powerless to alter the outcome.

Goals in this moment
  • Execute Picard's orders with precision, even as the systems fail
  • Protect the crew and the ship to the best of his ability
Active beliefs
  • Honor demands he fight to the end, even against impossible odds
  • The loop is a test of his discipline and loyalty
Character traits
Disciplined under pressure Frustrated by systemic failures Loyal to Picard and the crew Quick to execute orders, even in futility
Follow Deanna Troi's journey
Supporting 1

Unseen but implied to be stressed and focused—their absence from the bridge suggests they are either trapped in engineering or among the casualties.

Fletcher is not physically present on the bridge during this event, but their role in engineering—monitoring the warp core and ensuring crew safety—is implied by the cascading failures. Their absence highlights the broader impact of the collision: systems they would normally oversee (e.g., plasma venting, core containment) are failing catastrophically, and their potential casualties are part of Beverly's reports. Their unseen presence underscores the ship-wide scale of the disaster.

Goals in this moment
  • Ensure the warp core remains stable (a goal ultimately failed)
  • Protect lower-deck crew during emergencies
Active beliefs
  • Their vigilance can prevent catastrophic failures
  • The crew's safety is their top priority, even in the face of the unknown
Character traits
Dependable in high-stakes engineering roles Vigilant in hazardous zones Unseen but critical to ship operations
Follow Fletcher's journey

Objects Involved

Significant items in this scene

10
Enterprise Main Bridge Lighting System

The Enterprise's main bridge lights flicker erratically and shut off under the temporal distortion's energy surge, activating dim red emergency lighting. This shift casts stark shadows across the consoles, heightening the tension as the crew scrambles to respond. The emergency lights provide just enough illumination for the crew to see the ship's failing systems, but they also symbolize the crew's descent into chaos and the inevitability of the loop's repetition. The lights' failure is a physical manifestation of the ship's collapse, a reminder that even basic functions are not spared in the distortion's wake.

Before: Functional, though flickering as the distortion emerges.
After: Shut off, replaced by dim red emergency lighting …
Before: Functional, though flickering as the distortion emerges.
After: Shut off, replaced by dim red emergency lighting as the ship explodes.
USS Enterprise Main Bridge Control Consoles and Displays

The bridge consoles are the crew's primary tools for navigating the crisis, but they fail one by one as the distortion takes hold. Picard grips one station's edge while issuing commands; Riker punches override sequences; Data scans diagnostics; Worf activates tactical overrides. Fingers hammer keys and palms slap interfaces, but the systems lock out every input as antimatter containment fails. The consoles become useless, a physical manifestation of the crew's powerlessness in the face of the loop's repetition.

Before: Functional, though sensors detect unusual readings from the …
After: Locked out or non-responsive, their screens flickering with …
Before: Functional, though sensors detect unusual readings from the distortion.
After: Locked out or non-responsive, their screens flickering with red error readouts as the ship explodes.
Enterprise Tractor Beam System

Worf engages the Enterprise tractor beam from the bridge tactical station as Picard authorizes Data's proposed maneuver, but the beam fails to lock onto the emerging starship. The controls activate, but the distortion's interference renders them ineffective. The tractor beam's failure is a direct result of the ship's systems being overwhelmed by the temporal anomaly, leaving the crew with no way to alter the collision course. Its inefficacy underscores the futility of their efforts in the loop.

Before: Functional and ready for use, though sensors detect …
After: Inoperative, unable to engage the tractor beam as …
Before: Functional and ready for use, though sensors detect interference from the distortion.
After: Inoperative, unable to engage the tractor beam as the ship collides and explodes.
Enterprise Starboard Nacelle

The starboard nacelle is the critical structural failure point in the collision. When the unidentified starship strikes, the nacelle shatters, unleashing uncontrolled plasma that casts flickering glows across the bridge. Data delivers the grim assessment: 'The starboard nacelle has sustained a direct impact. We are venting drive plasma.' This breach triggers the cascading failure of the ship's systems, including the inertial dampers and antimatter containment. The nacelle's destruction is the direct cause of the Enterprise's doom, a physical manifestation of the loop's inescapable repetition.

Before: Intact and functional, though sensors detect unusual readings …
After: Shattered, venting plasma, and triggering a chain reaction …
Before: Intact and functional, though sensors detect unusual readings from the distortion.
After: Shattered, venting plasma, and triggering a chain reaction of system failures leading to the ship's explosion.
Enterprise System-Wide Emergency Alerts

The Enterprise system-wide alerts blare across the bridge as the temporal distortion emerges, their harsh klaxons and red warning lights piercing the eerie glow of the distortion. These alerts signal the ship's immediate peril, jolting the crew into action as the starboard nacelle begins to fail. The alarms are a constant reminder of the impending doom, their urgency mirroring the crew's desperation as they scramble to avoid the collision. The alerts fail to prevent the disaster, however, underscoring the futility of their efforts in the loop.

Before: Active but stable—standard operational alerts are present, but …
After: Blaring continuously as the ship spirals toward destruction, …
Before: Active but stable—standard operational alerts are present, but no red alerts or warnings.
After: Blaring continuously as the ship spirals toward destruction, red lights flashing erratically before the explosion silences them.
Enterprise's Emergency Escape Pods

The Enterprise's emergency escape pods are the crew's last-resort evacuation method, but they are never reached in time. Riker orders all hands to abandon ship, but the explosion occurs before anyone can board. The pods remain unused, a symbol of the crew's repeated failure to escape the loop. Their presence highlights the desperation of the moment, a reminder that even the most basic survival protocols cannot alter the outcome.

Before: Functional and ready for use, though the crew …
After: Unused, as the ship explodes before evacuation can …
Before: Functional and ready for use, though the crew has not yet attempted to reach them.
After: Unused, as the ship explodes before evacuation can be completed.
Enterprise's Main Shuttlebay

The incoming starship is the direct cause of the collision, emerging from the distortion on a direct course for the Enterprise. Its silence and lack of response add to the tension, making it an antagonistic force that the crew cannot evade. The ship's collision with the starboard nacelle triggers the cascading failures that doom the Enterprise, and its presence underscores the futility of the crew's efforts to break the loop. It is an inescapable harbinger of destruction, a manifestation of the temporal distortion's power.

Before: Emerging from the distortion, on a direct collision …
After: Collides with the Enterprise, causing catastrophic damage and …
Before: Emerging from the distortion, on a direct collision course.
After: Collides with the Enterprise, causing catastrophic damage and the ship's explosion.
Enterprise's Matter-Antimatter Propulsion System

The antimatter containment field collapses as the starboard nacelle is breached, a critical failure that Data reports alongside the core shutdown's failure. Geordi attempts emergency measures, but the containment's loss is inevitable, sealing the ship's fate. The field's collapse is the final nail in the coffin, ensuring the Enterprise's destruction in the loop. Its failure is a direct result of the collision and the nacelle's breach, a cascading effect that the crew cannot stop.

Before: Stable, though sensors detect fluctuations as the distortion …
After: Collapsed, leading to an imminent core breach and …
Before: Stable, though sensors detect fluctuations as the distortion emerges.
After: Collapsed, leading to an imminent core breach and the ship's explosion.
Enterprise-D Antimatter Core

The Enterprise's engine core is the heart of the ship's propulsion, but it becomes the source of its destruction in the loop. Geordi urges its ejection as containment fails, but the systems are offline, leaving the core to breach catastrophically. Data confirms the shutdown failure amid the ship's violent spins, forcing Picard to order abandonment. The core's breach is the final, irreversible step in the ship's destruction, a direct result of the collision and the nacelle's failure. Its destruction is the culmination of the loop's repetition, a physical manifestation of the crew's inability to escape their fate.

Before: Functional, though sensors detect fluctuations as the distortion …
After: Breached, triggering the ship's explosion.
Before: Functional, though sensors detect fluctuations as the distortion emerges.
After: Breached, triggering the ship's explosion.
Temporal Distortion Field

The temporal distortion is the catalyst for the collision, a highly localized anomaly in the space-time continuum that scrambles sensors and disables the Enterprise's systems. It spawns the unidentified starship on a direct course for the Enterprise, rendering evasive maneuvers impossible. The distortion's emergence is the first sign of the loop's repetition, a force that the crew cannot overcome. Its presence underscores the inescapable nature of the causality trap, a reminder that the crew is trapped in a cycle of destruction from which they cannot break free.

Before: Detected 20,000 kilometers off the port bow, murky …
After: Causes the collision, the ship's destruction, and the …
Before: Detected 20,000 kilometers off the port bow, murky and distorted.
After: Causes the collision, the ship's destruction, and the reset of the temporal loop.

Location Details

Places and their significance in this event

1
Main Bridge of the USS Enterprise-D

The bridge is the command center of the Enterprise and the epicenter of the crisis. Picard and his senior staff rush to their stations as the temporal distortion emerges, their voices overlapping in urgent exchanges. The viewscreen shows the murky distortion and the emerging starship, while consoles flicker with red alerts. The bridge's atmosphere is one of controlled chaos, with the crew scrambling to avoid the collision. As the ship is struck, the bridge becomes a battleground of failing systems and desperate orders, a microcosm of the crew's struggle against the loop's inescapable repetition.

Atmosphere Tension-filled with shouted orders, blaring alarms, and flickering emergency lights—chaotic yet disciplined, a microcosm of …
Function Command center and epicenter of the crisis, where the crew's efforts to avoid the collision …
Symbolism Represents the crew's struggle against the inescapable forces of the temporal loop, a battleground where …
Access Restricted to senior staff and essential personnel during red alert.
Red alert klaxons blaring Flickering emergency lights casting stark shadows Consoles displaying cascading error readouts Viewscreen showing the emerging starship and the distortion

Organizations Involved

Institutional presence and influence

1
Starfleet

Starfleet is represented through the Enterprise crew's adherence to protocols, their training, and the ship's systems. The crew follows Starfleet's emergency procedures—red alerts, damage control, evacuation orders—but the temporal distortion renders these protocols ineffective. The organization's influence is evident in the crew's disciplined response, even as the loop proves inescapable. Starfleet's technology and protocols are tested to their limits, exposing their vulnerabilities in the face of the unknown.

Representation Via institutional protocol being followed (red alerts, damage control, evacuation orders) and the crew's training.
Power Dynamics Exercising authority over individuals (Picard's commands, Riker's coordination) but being challenged by external forces (the …
Impact The crew's disciplined response highlights Starfleet's emphasis on training and protocol, but the loop's repetition …
Internal Dynamics Chain of command is tested as the crew scrambles to respond, with Picard and Riker …
Prevent the collision through adherence to Starfleet emergency protocols Ensure the crew's survival through evacuation procedures Institutional protocols (red alerts, damage control, evacuation orders) Technological systems (shields, helm, tractor beam, escape pods) Chain of command (Picard's leadership, Riker's coordination)

Narrative Connections

How this event relates to others in the story

What led here 7
Causal

"Picard directs Geordi and Data to investigate the anomalies Beverly reports; this directly leads back to the Observation Lounge and the inability to verify anything out of the ordinary."

Picard and Beverly share temporal déjà vu
S5E18 · Cause and Effect
Causal

"Picard directs Geordi and Data to investigate the anomalies Beverly reports; this directly leads back to the Observation Lounge and the inability to verify anything out of the ordinary."

Picard orders temporal anomaly investigation
S5E18 · Cause and Effect
Causal

"Picard directs Geordi and Data to investigate the anomalies Beverly reports; this directly leads back to the Observation Lounge and the inability to verify anything out of the ordinary."

Picard deflects gratitude with Adele’s legacy
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Voices and Distortion Collide
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Enterprise trapped in temporal distortion
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Catastrophic collision and ship destruction
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Enterprise Collision and Catastrophic Abandonment
S5E18 · Cause and Effect
What this causes 4
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Voices and Distortion Collide
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Enterprise trapped in temporal distortion
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Catastrophic collision and ship destruction
S5E18 · Cause and Effect
Causal

"Riker and Data propose different solutions which leads to Data predicting the impact of the ship, emphasizing the urgency and the dire consequences of failure."

Enterprise Collision and Catastrophic Abandonment
S5E18 · Cause and Effect

Key Dialogue

"RIKER: Decompress the main shuttlebay -- the explosive reaction might kick us out of the way."
"DATA: Captain -- I recommend we use the tractor beam to alter the other ship's trajectory."
"PICARD: Mister Worf -- make it so."
"DATA: The starboard nacelle has sustained a direct impact. We are venting drive plasma."
"PICARD: ((to comm)) All hands abandon ship. Repeat, all hands abandon -"