S6E4
· Relics

Scott Proposes a High-Risk Rescue Plan

After analyzing the Dyson Sphere’s portal and deducing the Enterprise’s likely fate, Montgomery Scott proposes a daring plan to remotely trigger the Jenolan’s hatch—using the ship as a wedge to jam the portal open. Geordi initially resists, citing the catastrophic risks, but Scott’s engineer-to-engineer urgency and confidence in the Jenolan’s shields ultimately sway him. The moment hinges on trust in Scott’s expertise and a shared understanding of the stakes: if the plan fails, the Jenolan will be crushed, and the Enterprise will remain trapped. The exchange reveals Scott’s ingenuity and Geordi’s growing respect for his predecessor’s instincts, while underscoring the desperation of their situation. The decision to proceed marks a turning point, shifting from analysis to action and committing the crew to a high-stakes gambit with irreversible consequences.

Plot Beats

The narrative micro-steps within this event

3

Scott and Geordi, studying the portal and Enterprise's ion trail, deduce that the Enterprise was pulled into the Dyson Sphere through the hatch, triggered by a subspace signal when they attempted a standard hail.

curiosity to realization

Faced with the danger of repeating the Enterprise's fate, Scott proposes a risky plan: trigger the hatch from a distance and then use the Jenolan to jam it open, allowing the Enterprise to escape.

problem to determination

Geordi initially objects to Scott's suicidal plan, but Scott's passionate plea, engineer to engineer, convinces him of its necessity and his confidence in making it work.

disagreement to reluctant agreement

Who Was There

Characters present in this moment

3

Conflicted—caught between the urge to follow protocol and the pull of Scott’s infectious confidence. His emotional state is a mix of skepticism, loyalty, and the quiet thrill of defying caution for a greater cause.

Geordi La Forge is the voice of reason and modern engineering caution in this scene. He stands firm, arms crossed, as Scott pitches his plan, his skepticism etched into his furrowed brow and the firm set of his jaw. His resistance is rooted in data: the hatch’s size, the shields’ limits, the sheer madness of the idea. Yet when Scott appeals to him ‘one engineer to another,’ Geordi’s hesitation wavers. His internal struggle is palpable—logic vs. instinct, protocol vs. desperation—as he searches his own heart before finally conceding. His agreement is reluctant but resolute, marking the moment he chooses to trust Scott’s legacy over his own caution.

Goals in this moment
  • To ensure the Jenolan’s survival and avoid repeating the fate of its lost crew.
  • To balance modern engineering rigor with the boldness of the past.
Active beliefs
  • That Scott’s plan is recklessly dangerous but potentially the only way to save the *Enterprise*.
  • That trusting a 23rd-century engineer’s instincts is a gamble worth taking in this desperate situation.
Character traits
Analytical Cautious Loyal Conflict-Averse Adaptive
Follow Montgomery Scott's journey
Supporting 1

Absent yet palpable; their memory is a silent, driving force behind Scott’s urgency and Geordi’s hesitation.

The USS Jenolan Crew are invoked indirectly as a poignant reminder of Scott’s lost comrades and the passage of time. Their absence looms over the scene, symbolizing the stakes of the rescue mission—failure would mean repeating their fate. Scott’s determination to honor their legacy fuels his risky plan, while Geordi’s caution reflects the crew’s unspoken fear of becoming another casualty of the Dyson Sphere’s mysteries.

Goals in this moment
  • To serve as a cautionary reminder of the dangers of the Dyson Sphere.
  • To symbolize the weight of legacy and the cost of failure.
Active beliefs
  • That the Jenolan’s crew would have taken the same risks to save others.
  • That their sacrifice must not be in vain.
Character traits
Sacrificial Symbolic Haunting
Follow USS Jenolan …'s journey
James T. Kirk

Ensign Franklin is mentioned indirectly as a reminder of the Jenolan’s lost crew and the 75 years Scott has missed. …

Objects Involved

Significant items in this scene

8
Dyson Sphere Portal Communications Array

The Dyson Sphere Portal Communications Array is the indirect catalyst for this event. Though not physically present in the Jenolan’s ops center, its existence is the linchpin of Scott’s plan. The array’s subspace-triggered hatch mechanism is deduced by Geordi and Scott as the likely cause of the Enterprise’s disappearance, and thus the key to its rescue. The array’s role is purely functional here—its design and activation frequencies are the puzzle pieces that Scott and Geordi must solve to execute their gambit. The object’s absence in the scene underscores its power: an ancient, alien technology that holds the Enterprise hostage and forces these engineers into a high-stakes game of deduction and risk.

Before: Dormant but active; the array’s subspace frequencies are …
After: Activated; the hatch begins to open in response …
Before: Dormant but active; the array’s subspace frequencies are still operational, waiting to be triggered by the Jenolan’s transmission.
After: Activated; the hatch begins to open in response to the subspace signal, setting the stage for the Jenolan’s wedge maneuver.
Dyson Sphere Portal Schematic (Communications Arrays Diagram)

The Diagram of Dyson Sphere Portal and Communications Arrays is the intellectual scaffolding of Scott and Geordi’s plan. Displayed on the Jenolan’s console, the schematic reveals the portal’s structure and the subspace frequencies that trigger its hatch. Geordi studies it intently, his finger tracing the lines that connect the communications arrays to the portal’s mechanism. The diagram is the key to unlocking the puzzle: it confirms Geordi’s theory that the arrays are access terminals, not just passive receivers. Scott’s quick grasp of the diagram’s implications—‘A nice bit of reasoning, Lad’—shows how the object bridges the gap between deduction and action. Its role is purely functional, but its presence in the scene underscores the power of knowledge: in the right hands, even an ancient alien schematic can be weaponized for rescue.

Before: Static but informative; the diagram is a pre-existing …
After: Activated; the diagram’s subspace frequencies are input into …
Before: Static but informative; the diagram is a pre-existing file pulled from the Jenolan’s archives, its data untouched since the ship’s crash.
After: Activated; the diagram’s subspace frequencies are input into the Jenolan’s systems, becoming the blueprint for the rescue plan.
Scott’s Dyson Sphere Hatch-Trigger Subspace Transmission

Scott’s Subspace Hatch-Trigger Transmission is the linchpin of the entire plan, a precisely calibrated signal designed to remotely activate the Dyson Sphere’s portal hatch. The transmission is both a technical marvel and a gamble: if it works, it will pull the Enterprise within reach; if it fails, the Jenolan will be crushed. Scott pitches the idea with engineer-to-engineer conviction, appealing to Geordi’s trust in his expertise. The transmission’s success hinges on two factors: the correct subspace frequency (deduced from the diagram) and the Jenolan’s shields (which must hold long enough to jam the hatch). The object’s role is purely functional, but its narrative weight is immense—it is the moment where theory becomes action, and where Scott’s legacy is put to the test.

Before: Hypothetical but designed; the transmission parameters are calculated …
After: Executed; the subspace signal is transmitted, triggering the …
Before: Hypothetical but designed; the transmission parameters are calculated based on the diagram and the ion trail data, but it has not yet been sent.
After: Executed; the subspace signal is transmitted, triggering the hatch and setting the Jenolan on its collision course with the portal.
USS Enterprise-D's Residual Impulse Ion Trail (Jenolan Departure)

The Enterprise’s Impulse Ion Trail is the critical clue that sets this event in motion. Its faint signature, detected by Scott on the Jenolan’s damaged consoles, is the breadcrumb that leads to the deduction of the Enterprise’s fate. The ion trail is more than data—it’s a lifeline, a whisper of hope in the void. Scott’s observation that the trail suggests the Enterprise was pulled in against its will (‘an impulse engine at full reverse’) is the spark that ignites his plan. The trail’s presence on the monitor looms over the engineers like a ghost, a silent plea for rescue. Its role in the event is purely informational, but its narrative weight is immense: it is the proof that the Enterprise is still reachable, and that Scott and Geordi’s gamble is justified.

Before: Faint but detectable; the ion trail lingers in …
After: Confirmed as a critical lead; the trail’s data …
Before: Faint but detectable; the ion trail lingers in space, a residual signature of the Enterprise’s struggle against the Dyson Sphere’s tractor beam.
After: Confirmed as a critical lead; the trail’s data is used to calculate the Jenolan’s approach vector, ensuring the subspace transmission is aimed at the correct terminal.
USS Jenolan Deflector Shield

The Jenolan’s Shields are the unsung heroes of this event, the thin line between success and annihilation. Scott’s confidence in their durability is the cornerstone of his plan: without the shields, the Jenolan would be crushed like an egg the moment it makes contact with the hatch. Geordi’s resistance is rooted in his skepticism of the shields’ capacity, but Scott’s reassurance—‘I know how to get a few extra gigawatts out of these babies’—wins him over. The shields’ role is to absorb the crushing force of the hatch long enough for the Enterprise to escape, a task that pushes them to their absolute limit. Their success or failure will determine whether the Jenolan becomes a coffin or a lifeline.

Before: Operational but strained; the shields are at 60% …
After: Overloaded and glowing; the shields flare blue as …
Before: Operational but strained; the shields are at 60% capacity, their generators damaged in the Jenolan’s crash, but Scott believes he can eke out enough power for the maneuver.
After: Overloaded and glowing; the shields flare blue as they absorb the hatch’s impact, their energy reserves drained but holding just long enough for the plan to work.
USS Jenolan Engineering/Ops Consoles

The USS Jenolan Ops Center Consoles are the nerve center of this event, where Scott and Geordi’s intellectual and emotional battle plays out. These consoles, though damaged and flickering, become extensions of the engineers’ wills—Scott’s hands fly over the controls with the urgency of a man racing against time, while Geordi leans in, his fingers tracing schematics as he weighs the risks. The consoles display critical data: the ion trail of the Enterprise, the diagram of the portal, and the Jenolan’s shield readings. Their glowing screens cast a tense, blue-tinged light on the engineers’ faces, symbolizing the fragile line between success and disaster. The consoles are both tools and witnesses, recording the moment two engineers from different eras bridge the gap between past and future with a single, desperate plan.

Before: Damaged but functional; the consoles are operational, though …
After: Overloaded but victorious; the consoles hum with increased …
Before: Damaged but functional; the consoles are operational, though their displays flicker and their systems are strained by the Jenolan’s failing power core.
After: Overloaded but victorious; the consoles hum with increased power as Scott pushes the shields to their limits, their screens flashing with confirmation of the subspace transmission’s success.
USS Jenolan Hatch

The USS Jenolan Hatch is the physical embodiment of the plan’s stakes. It is both the obstacle and the tool: an ancient, massive door that must be forced open to save the Enterprise, but one that could just as easily crush the Jenolan in the attempt. Scott’s idea to use the Jenolan as a wedge is a brilliant but brutal solution—turning the ship itself into a lever against the hatch’s mechanism. The hatch’s role is to serve as the ultimate test of Scott’s engineering prowess and the Jenolan’s resilience. Its presence looms over the scene, a silent, looming threat that forces Scott and Geordi to confront the consequences of their gamble: if the hatch closes too quickly, the Jenolan will be pulverized, and the Enterprise will remain trapped forever.

Before: Closed but activated; the hatch is dormant until …
After: Jammed open; the Jenolan’s hull presses against the …
Before: Closed but activated; the hatch is dormant until the subspace transmission triggers it, at which point it begins to open, revealing the Dyson Sphere’s interior.
After: Jammed open; the Jenolan’s hull presses against the hatch, holding it ajar long enough for the Enterprise to escape, though the strain threatens to tear the ship apart.
USS Jenolan Ops Monitor (Real-Time Portal and Ion Trail Display)

The USS Jenolan Ops Monitor (Portal and Ion Trail Display) is the visual anchor of this event, its screen a dynamic canvas where the fate of the Enterprise is debated and decided. The monitor cycles between two critical views: the ominous, circular hatch of the Dyson Sphere portal and the fading ion trail of the Enterprise. Scott and Geordi huddle around it, their faces illuminated by its eerie glow as they trace the trail with their fingers and point to the portal’s schematics. The monitor’s display is a battleground of logic and instinct—Scott sees opportunity in the portal’s mechanics, while Geordi sees only danger. Its role is to distill complex data into a visual narrative, making the abstract tangible: the Enterprise’s plight is no longer a theory, but a glowing, undeniable reality on the screen.

Before: Functional but strained; the monitor’s display flickers intermittently, …
After: Critical to execution; the monitor confirms the success …
Before: Functional but strained; the monitor’s display flickers intermittently, reflecting the Jenolan’s failing systems, but it remains the primary tool for analysis.
After: Critical to execution; the monitor confirms the success of the subspace transmission and the hatch’s activation, its screen flashing with alerts as the Jenolan prepares for the wedge maneuver.

Location Details

Places and their significance in this event

3
Dyson Sphere (Northern Hemisphere Surface)

The Dyson Sphere (Northern Hemisphere Surface) is the silent, looming antagonist of this event, its vast metallic expanse a reminder of the ancient, incomprehensible forces at play. Though the sphere itself is not physically present in the Jenolan’s ops center, its presence is felt in every line of dialogue and every glance at the monitor. The sphere’s portal hatch, displayed on the screen, is the focal point of the engineers’ tension—a circular maw that could either swallow the Enterprise forever or become the key to its salvation. The sphere’s role in this event is to serve as the ultimate test of human ingenuity against alien technology, a gauntlet that Scott and Geordi must navigate with nothing but their wits and the Jenolan’s failing systems. Its atmosphere is one of awe and dread, a mix of scientific curiosity and primal fear of the unknown.

Atmosphere Tense and awe-inspiring; the sphere’s sheer scale and alien design create a sense of insignificance, …
Function Antagonistic environment; the sphere’s portal is both the obstacle to be overcome and the mechanism …
Symbolism Represents the unknown and the limits of human understanding—an ancient, indifferent force that tests the …
Access Restricted by the sphere’s alien technology; the portal’s hatch can only be opened with the …
The eerie glow of the portal on the monitor, casting blue light on Scott and Geordi’s faces. The faint hum of the Jenolan’s failing systems, a counterpoint to the sphere’s silent, vast presence. The schematic of the portal’s arrays, a tiny human-made diagram superimposed on the incomprehensible scale of the sphere.
Dyson Sphere Portal Hatch

The Dyson Sphere Portal Hatch is the critical threshold of this event, a massive circular doorway that separates the Enterprise from freedom and the Jenolan from destruction. Though not physically present in the Jenolan’s ops center, the hatch is the focal point of the engineers’ tension, its image displayed on the monitor like a silent challenge. The hatch’s role is to serve as the ultimate test of Scott’s plan: if the Jenolan can jam it open, the Enterprise stands a chance; if not, both ships will be lost. The hatch’s presence looms over the scene, a reminder of the delicate balance between success and disaster. Its atmosphere is one of ominous anticipation, a mix of scientific curiosity and primal fear of the unknown forces that built it. The hatch is both the key and the lock, the solution and the obstacle.

Atmosphere Ominous and anticipatory; the hatch’s sheer size and alien design create a sense of dread, …
Function Critical threshold; the hatch must be jammed open to rescue the Enterprise, but doing so …
Symbolism Represents the boundary between the known and the unknown, a gateway that could either save …
Access Restricted by the sphere’s alien technology; the hatch can only be opened with the correct …
The circular shape of the hatch, displayed on the monitor like an unblinking eye. The faint glow of the portal’s arrays, a reminder of the ancient technology at play. The schematic overlay on the monitor, showing the hatch’s mechanism and the subspace frequencies required to trigger it.
USS Jenolen

The USS Jenolan is the stage for this high-stakes drama, its cramped, flickering ops center a microcosm of the tension between past and future. The ship’s decaying state—sparking consoles, damaged panels, and the ever-present hum of failing systems—mirrors the fragility of Scott’s position in the 24th century. The Jenolan is both a relic and a weapon: a 23rd-century vessel repurposed for a desperate 24th-century rescue. Its role in this event is to serve as the engineers’ last hope, a ship that must endure one final, brutal test to honor its lost crew and save the Enterprise. The Jenolan’s atmosphere is one of urgency and nostalgia, a place where the weight of history presses down on the present. The ship’s shuddering and groaning as Scott pushes its systems to the limit add a layer of physical tension, reinforcing the stakes of their gamble.

Atmosphere Urgently nostalgic; the Jenolan’s decaying systems create a sense of impending doom, while the engineers’ …
Function Command center and sacrificial vessel; the Jenolan is where the plan is hatched and executed, …
Symbolism Represents the bridge between past and future, a ship that must prove its worth one …
Access Limited by the ship’s failing systems; the Jenolan’s power core is unstable, and its shields …
The flickering blue glow of the consoles, casting long shadows on Scott and Geordi’s faces. The sporadic sparks from damaged panels, a reminder of the ship’s precarious state. The low hum of the Jenolan’s engines, a counterpoint to the engineers’ raised voices as they debate the plan.

Organizations Involved

Institutional presence and influence

1
Starfleet

Starfleet is the institutional backbone of this event, its protocols, values, and legacy shaping every decision made by Scott and Geordi. Though not physically present, Starfleet’s influence is felt in the engineers’ dialogue, their body language, and the weight of their choices. Scott’s appeal to Geordi—‘one engineer to another’—is a nod to Starfleet’s engineering culture, a tradition that binds them despite the 75-year gap. The organization’s role in this event is to serve as the moral and technical framework within which the rescue plan is hatched. Starfleet’s emphasis on exploration, ingenuity, and crew solidarity is what drives Scott to take the risk, while its modern protocols (embodied by Geordi’s caution) add a layer of tension to the decision. The organization’s presence is felt in the Jenolan’s systems, the Enterprise’s distress signal, and the very idea of a rescue mission—all of which are rooted in Starfleet’s mission to ‘boldly go.’

Representation Through institutional protocol (engineering standards, rescue procedures) and shared legacy (Scott and Geordi’s bond as …
Power Dynamics Exercising authority through tradition and protocol, but also being challenged by the need for bold, …
Impact The event reinforces Starfleet’s dual identity as both a rigid institution (embodied by Geordi’s caution) …
Internal Dynamics A tension between modern engineering caution (Geordi) and 23rd-century boldness (Scott), reflecting broader debates within …
To uphold Starfleet’s mission of exploration and rescue, even in the face of overwhelming odds. To honor the legacy of its engineers, past and present, by trusting in their ingenuity and adaptability. Through the shared values of exploration and crew solidarity, which motivate Scott and Geordi to take the risk. Through engineering protocols and standards, which Geordi initially uses to resist the plan but ultimately bends to the urgency of the situation. Through the Enterprise’s distress signal, which serves as a call to action rooted in Starfleet’s duty to assist stranded crews.

Narrative Connections

How this event relates to others in the story

What this causes 1
Causal

"Following the plan, Scott reports the Jenolan's damage, advising Captain Picard to destroy it, so the Enterprise could escape."

Jenolan's fatal engine meltdown
S6E4 · Relics

Key Dialogue

"SCOTT: Maybe all we need to do is get our foot in the door. If we trigger the hatch with a subspace transmission, we might not be pulled inside if we keep our distance from the sphere—say a half million kilometers. Then, when the hatch starts to close again, we move in, and use the Jenolen to jam the hatch open and hope the Enterprise can escape."
"GEORDI: You can't be serious. That hatch is huge. It could crush this ship like an egg."
"SCOTT: The shields will hold, Lad, don't you worry about that. I know how to get a few extra gigawatts out of these babies. Geordi. I've spent my whole life figuring out how to make crazy things work. I'm telling you... one engineer to another... I can do this."