S7E6
· Phantasms

Warp core collapses mid-engage

The Enterprise prepares to enter warp under Picard’s command, with Geordi confirming the warp core is stable. As Ensign Russell executes the order, the engines flare violently but fail to propel the ship—then shut down entirely. The warp field collapses, stranding the vessel in uncharted space. In Engineering, Geordi diagnoses a blown power converter and impulse engine failure, while Data reports the warp field collapse to Picard. The warp core emits an ominous rattling noise, signaling deeper system instability. This mechanical failure escalates the interphasic crisis, as the ship’s malfunction aligns with Data’s nightmares, hinting at a hidden, systemic threat. The crew’s immediate focus shifts from warp readiness to emergency repairs, but the underlying cause—Data’s interphasic visions—remains unaddressed, foreshadowing a broader, unseen sabotage.

Plot Beats

The narrative micro-steps within this event

2

Geordi reports the warp core is active and all systems are holding steady, indicating the Enterprise is ready for its warp test.

optimism to anticipation ['Engineering']

Picard orders Ensign Russell to engage, initiating the warp test; however, the Enterprise fails to go to warp, and the engines completely shut down.

anticipation to failure ['Bridge']

Who Was There

Characters present in this moment

5

Confident assurance → alarmed urgency → determined resolve (masking underlying frustration at the core’s betrayal).

Geordi La Forge, initially confident in the warp core’s stability, rushes to a console as the engines flare and die, his fingers darting across panels to diagnose the failure. He confirms the blown power converter and impulse engine shutdown to Picard via com, his voice shifting from professional assurance to alarmed urgency as the core emits a rattling noise. His physical presence—hunched over consoles, reacting with appalled disbelief—underscores the crisis, while his technical expertise becomes the crew’s lifeline.

Goals in this moment
  • Diagnose and repair the warp core and power converter to restore warp capability.
  • Reassure Picard and the crew that the situation is under control, despite the severity.
Active beliefs
  • The warp core’s failure is a mechanical anomaly, not a supernatural threat (yet).
  • His expertise and the ship’s redundancy systems will overcome the crisis within hours.
Character traits
Quick-thinking under pressure Technically precise Adaptive problem-solver Emotionally reactive to system failures
Follow Geordi La …'s journey

Calm authority → measured concern (the failure disrupts his plans but does not shake his resolve).

Picard, standing on the bridge, issues the order to engage warp speed with calm authority, only for the engines to flare and die. His voice cuts through the sudden silence via com as Data reports the warp field collapse, his tone shifting from composed command to measured concern. Though physically absent from Engineering, his presence looms over the scene—his orders set the crisis in motion, and his expectation of solutions (Geordi’s ‘two, three hours’) frames the crew’s response. The failure is a direct challenge to his leadership, yet his demeanor remains controlled, a bulwark against panic.

Goals in this moment
  • Restore warp capability as swiftly as possible to resume the mission.
  • Maintain crew morale and confidence in his leadership despite the setback.
Active beliefs
  • The warp core failure is a solvable technical problem, not a supernatural threat (yet).
  • Geordi’s expertise will resolve the issue within the promised timeframe.
Character traits
Composed under pressure Authoritative yet adaptable Trusts his crew’s expertise Strategic thinker (already considering next steps)
Follow Jean-Luc Picard's journey

Neutral surface masking subconscious unease (the core’s rattling echoes his interphasic visions).

Data stands near the consoles in Engineering, his expression neutral as he relays the warp field collapse to Picard via com. His lack of visible emotion contrasts with Geordi’s alarm, but his precise, detached reporting—‘The warp field has collapsed, sir’—serves as a counterpoint to the chaos. He does not physically interact with the failing systems, instead acting as a conduit for critical information, his presence a reminder of the ship’s reliance on both human and android precision.

Goals in this moment
  • Ensure Picard receives accurate, real-time updates on the warp core’s status.
  • Avoid drawing attention to his own connection to the failure (his nightmares).
Active beliefs
  • The warp core’s failure is an isolated technical issue, unrelated to his subconscious (for now).
  • His duty is to support the crew, even if he suspects a deeper link to his dreams.
Character traits
Logically detached in crises Reliable information relay Emotionally inscrutable (even as the core’s failure mirrors his nightmares) Dutifully subordinate to Picard’s chain of command
Follow Data's journey
Supporting 2

Unseen but implied frustration (watching the engines fail after his execution of the order).

Ensign Russell, though not physically present in Engineering during this event, is the bridge officer who executes Picard’s order to engage warp speed—only for the engines to fail spectacularly. His role is implied through the scene’s action: the flare of the engines, their sudden death, and the warp field’s collapse are direct consequences of his compliance with Picard’s command. His absence from the Engineering scene underscores the ship-wide impact of the failure, as his actions (or lack thereof) are felt across departments.

Goals in this moment
  • Execute Picard’s orders precisely, even if the outcome is catastrophic.
  • Avoid blame for the failure (it was a direct command).
Active beliefs
  • The warp core was stable when the order was given (he had no reason to doubt it).
  • His role is to obey, not question, the captain’s commands.
Character traits
Dutifully follows orders Indirectly triggers the crisis through compliance Represents the chain of command in action
Follow Russell's journey
Tyler
Ensign
secondary

Silent alarm (watching the crisis unfold with growing unease).

Ensign Tyler stands in Engineering during the warp core failure but does not speak or act, her presence a silent witness to the crisis. Positioned near the consoles, she observes Geordi’s frantic diagnostics and the core’s ominous rattling, her lack of participation highlighting the urgency of the moment—only senior officers (Geordi, Data) are equipped to respond. Her role here is symbolic: the ‘everyman’ crewmember whose safety depends on the officers’ success, her quiet alarm a reminder of the stakes for the entire ship.

Goals in this moment
  • Stay out of the way of senior officers to avoid hindering repairs.
  • Mentally prepare for potential emergency protocols if the situation worsens.
Active beliefs
  • The officers will handle the crisis, but the core’s rattling is deeply unsettling.
  • Her role is to support, not lead, in this moment.
Character traits
Observant but deferential Alarmed but non-interfering Represents the broader crew’s vulnerability
Follow Tyler's journey

Objects Involved

Significant items in this scene

5
Data's Communicator

Data’s communicator serves as the bridge between Engineering’s chaos and Picard’s command, relaying the warp field collapse with clinical precision. His voice, devoid of emotion, cuts through the rattling core and Geordi’s alarmed reactions, delivering the bad news in a way that underscores the disconnect between the android’s detachment and the human crew’s urgency. The device itself is unremarkable, but its role in this moment is pivotal: it ensures Picard’s awareness of the crisis, even as it highlights the growing gulf between perceived stability and reality.

Before: Active and synced to the ship’s com network, …
After: Still functional but now carrying urgent, crisis-related transmissions.
Before: Active and synced to the ship’s com network, ready for standard operational updates.
After: Still functional but now carrying urgent, crisis-related transmissions.
USS Enterprise-D Warp Core (Main Engineering) (Primary System)

The Enterprise’s warp core, freshly activated under Geordi’s confirmation, roars to life with a blinding flare—only to sputter violently and die mid-engagement, its plasma shaft darkening as it emits a catastrophic rattle. This rattle is not a mere mechanical noise but a harbinger: it foreshadows the interphasic threat lurking in Data’s nightmares, now manifesting in the ship’s physical systems. The core’s failure strands the Enterprise, its ominous vibrations a soundtrack to the crew’s sudden crisis, symbolizing the unseen forces at work.

Before: Active and stable, glowing with plasma energy, humming …
After: Darkened and inert, emitting a persistent, eerie rattling …
Before: Active and stable, glowing with plasma energy, humming steadily under Geordi’s confirmation.
After: Darkened and inert, emitting a persistent, eerie rattling noise, its plasma field collapsed.
USS Enterprise-D Impulse Engines

The impulse engines, designed as a backup propulsion system, flare brightly under Ensign Russell’s execution of Picard’s order—only to cut out entirely as the power converter fails. Their sudden death is a secondary but critical failure, compounding the warp core’s collapse and leaving the Enterprise completely adrift. Geordi’s offhand mention of their shutdown (‘Impulse engines are down, too’) underscores the ship’s paralysis, the engines’ failure a reminder that no system is immune to the crisis.

Before: Standby mode, ready to engage if warp speed …
After: Inert and non-functional, requiring diagnostics and repairs alongside …
Before: Standby mode, ready to engage if warp speed fails.
After: Inert and non-functional, requiring diagnostics and repairs alongside the warp core.
Engineering Warp Core Primary Control Consoles

The Engineering consoles, usually a hub of controlled activity, become a battleground as Geordi’s fingers dart across their panels, pulling up diagnostics on the failing warp core and power converter. Their screens flicker with red alerts, the data confirming the worst: the ship is stranded. The consoles’ role here is twofold—first, as a tool for Geordi’s frantic troubleshooting, and second, as a visual representation of the crisis, their glowing panels casting an urgent light on the scene. They are the interface between human expertise and the ship’s dying systems.

Before: Displaying green ‘all systems nominal’ readouts, humming with …
After: Flooded with red alert indicators, scrolling with failure …
Before: Displaying green ‘all systems nominal’ readouts, humming with standard operational activity.
After: Flooded with red alert indicators, scrolling with failure codes, and demanding immediate attention.
USS Enterprise Engineering Power Converter

The power converter, a critical component in the warp core’s energy distribution, blows out violently as the engines flare and die. Its failure is the first domino in a cascade of system collapses, directly causing the impulse engines to shut down and stranding the ship. Geordi identifies it as the immediate cause of the crisis, his diagnosis framing it as a repairable (but urgent) issue—though the rattling core suggests deeper corruption. The converter’s destruction is a tangible manifestation of the ship’s vulnerability, its smoke and sparks a visual cue of the mechanical betrayal.

Before: Functional and integrated into the warp core’s energy …
After: Blown out, inert, and requiring replacement or repair …
Before: Functional and integrated into the warp core’s energy grid, supplying power to the impulse engines.
After: Blown out, inert, and requiring replacement or repair (Geordi estimates 2–3 hours).

Location Details

Places and their significance in this event

2
Main Bridge of the USS Enterprise-D

Though the bridge is not the primary setting for this event, its presence looms over the scene as the command center where Picard’s order to engage warp speed originates—and where the failure’s consequences are first felt. The viewscreen’s flare and sudden darkness, the red alerts on the consoles, and the stunned silence of the crew all reflect the bridge’s role as the nerve center of the crisis. Picard’s voice, relayed via com, ties the two locations together, his authority stretching from the bridge to Engineering as he demands solutions. The bridge’s usual air of control is momentarily disrupted, a reminder that no part of the ship is untouched by the failure.

Atmosphere Stunned silence giving way to urgent, hushed activity—officers tense at their stations, the weight of …
Function Command hub where the crisis is first recognized and coordinated; the source of the order …
Symbolism Embodies the chain of command and the crew’s reliance on Picard’s leadership in a moment …
Access Restricted to senior officers and essential crew during operational crises.
The viewscreen’s flare and sudden darkness as the engines fail. Red alert indicators pulsing on LCARS displays. The stunned silence of the bridge crew, broken only by Picard’s voice via com.
Main Engineering (Deck 42, USS Enterprise-D, Present Timeline)

Main Engineering’s warp core chamber, usually a place of ordered activity and humming efficiency, becomes a pressure cooker of alarm as the warp core dies with a violent rattle. The plasma shaft darkens, the consoles flare red, and Geordi rushes between stations, his movements sharp with urgency. The location’s usual atmosphere of controlled precision is shattered, replaced by a tense, chaotic energy where every sound—the rattling core, the beeping consoles—feels like a countdown. The chamber’s catwalks and machinery, once symbols of Starfleet ingenuity, now frame a scene of vulnerability, the ship’s ‘heart’ stuttering under unseen strain.

Atmosphere Tension-filled with urgent activity, the air thick with the scent of ozone and the sound …
Function Primary site of the warp core failure and emergency diagnostics; the crew’s last line of …
Symbolism Represents the Enterprise’s exposed vulnerability, its ‘heart’ (the warp core) now a source of terror …
Access Restricted to senior engineering staff and officers during crises (Ensign Tyler’s passive presence underscores this).
The warp core’s plasma shaft darkening from a brilliant glow to eerie blackness. Consoles flashing red alert indicators, casting an urgent glow on Geordi’s face. The persistent, ominous rattle of the core, like a dying breath. Smoke or sparks from the blown power converter, adding to the visual chaos.

Organizations Involved

Institutional presence and influence

1
Starfleet

Starfleet’s presence in this event is embodied in the Enterprise’s systems, protocols, and the crew’s training—all of which are tested by the warp core failure. The ship’s redundancy systems, designed to prevent such crises, prove insufficient, exposing a gap between Starfleet’s theoretical preparedness and the reality of an interphasic threat. Picard’s leadership, Geordi’s technical expertise, and Data’s reporting all reflect Starfleet’s values: duty, adaptability, and problem-solving under pressure. Yet the failure itself is a silent critique of institutional assumptions, hinting that even Starfleet’s best may not be enough against the unseen.

Representation Through the crew’s adherence to protocol (Picard’s orders, Geordi’s diagnostics, Data’s reporting) and the ship’s …
Power Dynamics Exercising authority over the crew (Picard’s commands) but being challenged by the warp core’s failure …
Impact The failure forces Starfleet’s ideals into conflict with reality, revealing the limits of even its …
Internal Dynamics Tension between protocol (follow orders) and pragmatism (adapt to the crisis), with Geordi’s technical leadership …
Restore the Enterprise’s warp capability to resume the mission and avoid further systemic failure. Maintain crew morale and confidence in Starfleet’s protocols, despite the unprecedented crisis. Chain of command (Picard’s orders → Geordi’s execution → Data’s reporting). Technical expertise (Geordi’s diagnostics and repair plan). Institutional trust (the crew’s faith in Starfleet’s systems and training).

Narrative Connections

How this event relates to others in the story

What led here 1
Escalation medium

"The warp core emitting a rattling noise further escalates the situation and alarms Geordi."

Warp core collapses under unseen threat
S7E6 · Phantasms
What this causes 1
Escalation medium

"The warp core emitting a rattling noise further escalates the situation and alarms Geordi."

Warp core collapses under unseen threat
S7E6 · Phantasms

Key Dialogue

"GEORDI: "We've just started her up, sir. All systems are holding steady... Ready when you are, Captain.""
"PICARD: "Ensign Russell -- set course and engage.""
"DATA: "The warp field has collapsed, sir.""
"GEORDI: "It looks like we've blown out the entire power converter, Captain. Impulse engines are down, too - we're not going anywhere... But I know exactly how to fix it. Give me two, three hours, tops.""