Fabula
S5E10 · New Ground
S5E10
· New Ground

Worf races to save Alexander amid failing systems

On the Enterprise bridge, the crew scrambles to rescue Alexander Rozhenko, trapped in a burning biolab, while the ship’s failing warp core threatens their ability to intercept the Soliton wave. Picard attempts to contact Alexander via comms, but the boy doesn’t respond—heightening Worf’s fear that he’s injured or worse. Worf’s frustration boils over as he confirms the transporters remain offline, leaving no immediate way to extract Alexander. Felton’s urgent report of a catastrophic warp power failure forces Picard and Riker to confront a brutal choice: divert resources to stabilize the warp core or maintain their desperate pursuit of the Soliton wave. The scene escalates the dual crisis—Alexander’s physical peril and the ship’s existential threat—while exposing Worf’s helplessness to protect his son, both emotionally and physically. The tension underscores the collision of personal and professional stakes, with every second counting as the fire spreads and the Soliton wave looms closer.

Plot Beats

The narrative micro-steps within this event

2

Picard attempts to contact Alexander in the biolab, but receives no response. Worf confirms Alexander is alive via sensors but possibly injured, setting a tone of urgency.

urgency to worry

Riker inquires about transporting Alexander, but Worf reports transporters are offline, increasing the stress and posing an obstacle for the rescue.

worry to frustration

Who Was There

Characters present in this moment

4

Terror and disorientation—Alexander is likely overwhelmed by the fire, the smoke, and the realization that he is trapped with no immediate way out. His silence suggests shock, pain, or a desperate attempt to stay calm.

Alexander is trapped in Biolab Four, unresponsive to Picard’s comms hail. Sensor readings (monitored by Worf) suggest he is alive but possibly injured, though his exact condition remains unclear. The fire raging around him is implied by the urgency of the crew’s reactions, and his silence speaks volumes—whether from injury, fear, or the chaos of the moment. His physical absence looms large over the bridge, a ticking clock whose fate hinges on the crew’s ability to act.

Goals in this moment
  • Survive the fire and await rescue (implicit, unspoken).
  • Reconnect with Worf, even if only through comms, to feel less alone (unconscious desire).
Active beliefs
  • His father will find a way to save him, despite their strained relationship.
  • He is responsible for his own mistakes (e.g., stealing the lizard model earlier), but this crisis is beyond his control.
Character traits
Vulnerability in crisis Unspoken fear (inferred from silence) Dependence on others for survival
Follow Alexander Rozhenko's journey

Controlled urgency masking deep concern—Picard’s calm exterior belies the internal conflict between paternalistic instinct (for Worf’s son) and his duty to the ship and crew.

Picard initiates direct contact with Alexander via comms, his voice steady but laced with urgency as he calls into the burning Biolab Four. Upon receiving no response, he exchanges a tense, wordless look with Riker, acknowledging the escalating crisis. His leadership is tested as Felton’s report of warp power failure forces him to weigh the ship’s survival against the immediate need to rescue Alexander. Picard’s posture remains composed, but his grip on the console tightens subtly, betraying the weight of the decision ahead.

Goals in this moment
  • Establish communication with Alexander to assess his condition and provide reassurance.
  • Coordinate a response to the warp core failure while maintaining pursuit of the Soliton wave.
Active beliefs
  • Every life on the *Enterprise* is his responsibility, including Alexander as an extension of Worf’s family.
  • Technological failure is surmountable with quick thinking, but human lives cannot be gambled lightly.
Character traits
Command presence under pressure Empathetic but decisive Strategic multitasking Emotional restraint in crisis
Follow Jean-Luc Picard's journey

A maelstrom of guilt, fear, and fury—Worf blames himself for not being there for Alexander sooner, and his inability to act physically manifests as a physical tension that radiates from him.

(Note: This entry is a secondary participation for Worf, focusing on his emotional subtext not fully captured in the primary entry.) Worf’s internal conflict is visible in the way he avoids looking at Picard or Riker after confirming the transporters are offline. His hands hover over his console, fingers twitching as if itching to take action—any action—that might save Alexander. The Klingon in him wants to roar in frustration, but the Starfleet officer clamps down, channeling his energy into scanning for alternative solutions. His silence speaks volumes: a father’s fear, a warrior’s helplessness.

Goals in this moment
  • Find a loophole in Starfleet protocol or technology that could extract Alexander, no matter how risky.
  • Protect his son’s legacy and honor, even if it means defying orders.
Active beliefs
  • A true Klingon father would never abandon his son, even in the face of impossible odds.
  • Starfleet’s rules are meant to be bent when lives are at stake, especially family.
Character traits
Internalized rage at his powerlessness Discipline as a coping mechanism Paternal instinct clashing with duty
Follow Worf's journey
Supporting 1
Felton
Ensign
secondary

High-alert urgency with underlying tension—Felton is fully invested in the mission but acutely aware of the human cost, particularly Worf’s distress. His focus is razor-sharp, but there’s a flicker of frustration at the ship’s limitations.

Felton’s urgency is palpable as he interrupts the tense silence with his report of warp power failure, his voice cutting through the bridge like a alarm. His fingers move swiftly over his console, confirming the drop in speed and the ship’s vulnerability. He directs his report to Picard but glances briefly at Worf, acknowledging the personal stakes of the crisis. Felton’s role as the messenger of bad news is unwelcome but necessary, and he carries it with professionalism, though his posture betrays the weight of the moment.

Goals in this moment
  • Provide Captain Picard with accurate, real-time data on the warp core failure to inform his decisions.
  • Support the crew’s efforts to stabilize the ship while indirectly aiding Worf’s need to rescue Alexander.
Active beliefs
  • The *Enterprise*’s systems are reliable, but even the best technology can fail when pushed to its limits.
  • Every crew member’s well-being is interconnected, and personal crises can’t be separated from the mission.
Character traits
Unwavering professionalism under pressure Clear, concise communication in crises Empathy for crewmates’ personal struggles (e.g., Worf’s plight) Adaptability to shifting priorities
Follow Felton's journey

Objects Involved

Significant items in this scene

4
USS Enterprise Main Bridge Control Consoles and Displays

The bridge consoles become the nerve center of the dual crisis, relaying critical data that forces impossible choices. Worf’s console confirms Alexander’s status (alive but injured) and the transporters’ offline status, while Felton’s console reveals the warp power failure and the ship’s deceleration. These stations are not just tools but active participants in the tension, their screens flashing warnings and their alerts (e.g., Felton’s urgent report) dictating the crew’s next moves. The consoles’ limitations—unable to transport Alexander, unable to sustain warp speed—mirror the crew’s frustration and the ship’s vulnerability.

Before: Operational but under duress—sensors and comms are functional, …
After: Critical systems (warp power) are failing, and the …
Before: Operational but under duress—sensors and comms are functional, though the transporters remain offline.
After: Critical systems (warp power) are failing, and the consoles now display dire warnings, forcing the crew to prioritize between Alexander’s rescue and the Soliton wave pursuit.
USS Enterprise Transporter System

The Enterprise transporters, though not physically present on the bridge, cast a long shadow over the event. Worf’s frustrated confirmation that they remain 'off-line' is the moment the crew realizes Alexander is truly trapped, with no immediate technological solution. The transporters’ failure symbolizes the crew’s powerlessness and the fragility of their advanced systems. Their offline status forces the crew to consider desperate alternatives, such as risking the warp core or attempting a manual rescue—options that carry their own dangers.

Before: Offline due to the warp core instability, rendering …
After: Still offline, with no indication of when they …
Before: Offline due to the warp core instability, rendering them unusable for extraction.
After: Still offline, with no indication of when they might be restored, leaving Alexander’s rescue dependent on other, riskier methods.
Enterprise-D Antimatter Core

The warp core’s failure is the ticking time bomb of this event, its instability forcing Felton to deliver the devastating report that 'warp power is dropping.' This failure is not just a technical issue but a narrative pivot, as it collides with the personal crisis of Alexander’s rescue. The warp core’s decline mirrors the crew’s unraveling composure, and its potential collapse threatens to strand them between the Soliton wave and their trapped crewmate. The object’s failure is both literal (power loss) and symbolic (the ship’s—and crew’s—limits).

Before: Stable but pushed to its limits by the …
After: Catastrophically failing, with warp power dropping and the …
Before: Stable but pushed to its limits by the Soliton wave pursuit, showing early signs of strain.
After: Catastrophically failing, with warp power dropping and the ship losing speed, forcing Picard and Riker to confront an impossible choice.
USS Enterprise-D Bridge Communications Console

The Enterprise bridge comms console serves as the lifeline to Alexander in Biolab Four, but it fails to establish contact, leaving Picard’s hail unanswered. This silence amplifies the crew’s dread, as the console’s inability to connect underscores Alexander’s isolation and the crew’s helplessness. Later, Felton uses the console to report the catastrophic warp power failure, transforming it from a tool of communication to a harbinger of the ship’s impending crisis. Its beeping alerts and static-filled channels mirror the urgency and frustration of the moment.

Before: Functional but strained—comms are operational, though Alexander does …
After: Still functional for internal ship communications (e.g., Felton’s …
Before: Functional but strained—comms are operational, though Alexander does not respond to hails.
After: Still functional for internal ship communications (e.g., Felton’s report to Picard), but the failure to reach Alexander leaves it symbolically 'broken' in the crew’s eyes.

Location Details

Places and their significance in this event

1
Main Bridge of the USS Enterprise-D

The Enterprise bridge is the epicenter of the dual crisis, its usually orderly space now charged with urgency and tension. The forward viewscreen looms as a silent witness to the Soliton wave’s approach, while the crew’s consoles bathe them in emergency lighting. The air hums with the low thrum of alarms and the sharp exchanges of the crew, each word and gesture amplified by the confined space. The bridge’s design—open, circular, with no physical barriers—forces the crew to confront their shared predicament: Alexander’s life hangs in the balance, and the ship’s survival is at risk. The location’s symbolism is potent: a place of command now reduced to helplessness.

Atmosphere A pressure cooker of controlled panic—alarms pulse like a heartbeat, dialogue is clipped and urgent, …
Function Command hub for crisis management, where personal and professional stakes collide, and where every decision …
Symbolism Represents the intersection of duty and humanity—the bridge is where Starfleet’s ideals (exploration, protection) are …
Access Restricted to senior officers and essential crew during Red Alert; no unnecessary personnel or distractions …
Pulsing red alert lights casting long shadows across the consoles. The low, insistent hum of alarms blending with the crew’s tense voices. The forward viewscreen displaying the ominous Soliton wave, a visual reminder of the looming threat. Consoles flickering with warnings, their screens reflecting the crew’s strained expressions.

Organizations Involved

Institutional presence and influence

1

Narrative Connections

How this event relates to others in the story

What led here 2
Escalation

"The threat to the colony on Lemma Two escalates when the fire in Biolab Four traps Alexander, raising the personal stakes and forcing the crew to balance saving the colony with rescuing Worf's son."

Soliton wave accelerates beyond all projections
S5E10 · New Ground
Escalation

"The threat to the colony on Lemma Two escalates when the fire in Biolab Four traps Alexander, raising the personal stakes and forcing the crew to balance saving the colony with rescuing Worf's son."

Soliton wave escalates to planetary threat
S5E10 · New Ground

Key Dialogue

"PICARD: Bridge to biolab four. Alexander, can you hear us?"
"WORF: ((tight)) Sensors show he is alive... he may be injured."
"RIKER: Can we transport him out of there?"
"WORF: ((getting frustrated)) Transporters are still off-line."
"FELTON: ((urgent)) Captain, warp power is dropping. We're losing speed."