Fabula
S2E17 · Samaritan Snare

Bluff Set in Motion — Picard's Emergency Call

In Engineering Riker pushes forward with a risky, nonlethal ruse: Sonya will simulate overwhelming firepower while Geordi improvises under duress aboard the Mondor. Data frames the plan clinically — timing and intent must be perfect — and Sonya, skeptical at first, accepts the task. The moment turns sharp when Worf interrupts with an emergency summons: Picard is close to death. The announcement raises the stakes, forcing Riker to accelerate the rescue and balance two simultaneous lives at risk. This is an escalation and set-up: the bluff is activated just as the moral pressure to prioritize Picard threatens to derail the extraction of Geordi.

Plot Beats

The narrative micro-steps within this event

2

Worf’s urgent hail detonates the stakes: Starbase 515 reports Picard is close to death, stunning Riker and spiking pressure on the rescue.

operational focus to dread ['Bridge (V.O.)', 'Starbase five one five']

Riker snaps to command—“Be ready!”—and moves out with Data while Sonya attacks the controls, priming the anti-matter blender for the bluff.

shock to decisive action

Who Was There

Characters present in this moment

5

Incredulous at first, then determined and focused as she transitions into action to implement the bluff despite the sudden escalation.

Begins skeptical and questioning about the plan's feasibility, then accepts responsibility, immediately moving to operate engineering systems (anti‑matter blender) to simulate weapons effects and prepare the staged display.

Goals in this moment
  • Produce a convincing nonlethal simulation of weapons fire to intimidate the Pakleds.
  • Execute engineering procedures quickly and accurately to support the away team's safety.
  • Maintain engineering control even as command is forced to depart for a medical emergency.
Active beliefs
  • A well‑timed engineering display can alter enemy perception and behavior.
  • Riker and Geordi are competent and worth supporting with technical risk.
  • Practical technical implementation is the linchpin separating theory from success.
Character traits
skeptical technically competent practical resolute under pressure
Follow Sonya's journey

Clinical and detached in presentation, but methodical concern is implied by the urgency of his technical caveats.

Provides sensor analysis and tactical framing: confirms progressive weapons potential, emphasizes timing and intent, reports the Pakleds heard the fabricated story about Geordi; remains clinical and precise before departing with Riker.

Goals in this moment
  • Supply accurate sensor and timing data to ensure the bluff's success.
  • Clarify technical constraints so the operation minimizes risk.
  • Support Riker's decision-making with precise information.
Active beliefs
  • Precise timing and clear intent are critical for deception to work operationally.
  • Sensor data can meaningfully predict enemy capability and reaction.
  • Logical assessment should guide risky tactical improvisations.
Character traits
analytical calm procedural supportive of command
Follow Data's journey

Alert and grave; his transmission carries the weight of an urgent duty call rather than personal panic.

Interrupts remotely (V.O.) from the bridge to deliver an emergency summons: informs Riker that Starbase Five One Five reports Captain Picard is close to death, conveying urgent, protocol‑critical information.

Goals in this moment
  • Ensure command is immediately informed of a high‑priority medical emergency.
  • Prompt appropriate chain‑of‑command reaction in accordance with Starfleet protocol.
Active beliefs
  • Starfleet emergency summonses require immediate attention and action.
  • Chain of command and timely notification save lives.
Character traits
duty‑bound direct urgent formal
Follow Worf's journey

Focused and tactically confident while planning, then abruptly stunned and concerned when told of Picard's condition; urgency quickly overlays deliberate planning.

Leads the rescue planning in Engineering: reassures Sonya about Geordi's improvisational capacity, confirms the bluff strategy, instructs Sonya to prepare, and reacts stunned to Worf's medical summons before exiting immediately with Data.

Goals in this moment
  • Execute a convincing nonlethal bluff to enable Geordi's extraction from the Mondor.
  • Protect Enterprise crew while minimizing escalation and casualties.
  • Respond immediately to the medical emergency without abandoning the rescue.
Active beliefs
  • Geordi's engineering skill and adaptability will allow him to improvise under pressure.
  • The Pakleds can be manipulated by perceived intelligence/strength signals.
  • Command must balance multiple lives and prioritize according to immediacy and protocol.
Character traits
decisive pragmatic trusting of subordinates command‑minded under pressure
Follow William Riker's journey

Implicitly pressured and endangered; determined to survive and assist the rescue through improvisation.

Referenced as the stranded chief engineer on the Mondor: the entire bluff and timing hinge on his ability to improvise under duress and interpret the staged signals from the Enterprise to neutralize or distract the Pakleds.

Goals in this moment
  • Use engineering skill to disrupt or disable Pakled systems as opportunity allows.
  • Interpret Enterprise's signals and time his actions to maximize the bluff's credibility.
Active beliefs
  • His technical ability gives him a fighting chance despite being outnumbered or outgunned.
  • The Enterprise will act to recover him and will coordinate with his improvised efforts.
Character traits
resourceful (implied) steadfast (implied) technically inventive (implied)
Follow Geordi La …'s journey

Objects Involved

Significant items in this scene

1
Main Engineering Pool Table

The Main Engineering pool table functions as immediate visual set dressing and a pragmatic work surface: Sonya looks up from it at the opening of the exchange, using its presence to ground the scene's casual‑to‑urgent shift. It marks Industrial Engineering's informal work rhythm before she moves to the core apparatus.

Before: Located in Main Engineering, scuffed and used as …
After: Remains in Main Engineering unchanged physically, continuing to …
Before: Located in Main Engineering, scuffed and used as a leaning rail and informal workbench; crew clustered around it.
After: Remains in Main Engineering unchanged physically, continuing to serve as nearby set dressing while attention shifts to active engineering systems.

Location Details

Places and their significance in this event

3
Main Bridge

The Bridge functions offstage as the communications node: Worf transmits an emergency message to Engineering from here, and its formal protocols momentarily override the tactical discussion belowdecks.

Atmosphere Formally urgent and procedural—brief, clipped communications that carry high consequence.
Function Communications center and command nexus that interjects a life‑and‑death prioritization into Engineering's plan.
Symbolism Represents institutional command and the competing demands of centralized protocol versus field improvisation.
Access Restricted to command and tactical staff; communications routed through secured channels.
Curved LCARS consoles and amber/blue lighting Status chimes and clipped orders over comms Worf's tactical voice transmitted V.O.
Main Engineering

Main Engineering is the operational stage where tactical improvisation is engineered: consoles hum, technicians cluster, and Sonya moves from the pool table to the anti‑matter systems. It is both a technical workshop and moral fulcrum where command decisions are translated into risky technical actions.

Atmosphere Tense and focused—shifting from skeptical curiosity to urgent, compressed readiness when the medical summons arrives.
Function Staging area for the deception plan and the point of execution for the simulated weapons …
Symbolism Embodies the ship's practical heart—where human expertise confronts ethical triage under institutional pressure.
Access Effectively restricted to senior engineering staff and command during the operation; technical consoles are controlled …
Warm console glow and coolant hisses Pool table with scuff marks Low processor hum and shifting status chimes Sonya moving to anti‑matter systems (implied machinery noises)
Mondor (Pakled ship)

The Mondor is the disabled Pakled ship that houses Geordi and the adversary systems; it is the far site of the rescue and the target of the staged bluff. Its failing systems and sparking interiors intensify the risk to the away team and make timing essential.

Atmosphere Fragile and unreliable—flickering lights, sparking junctions, and an atmosphere of mechanical neglect.
Function Battleground/target where Geordi must improvise and where the Pakleds' reaction to the bluff will determine …
Symbolism A crude, precarious nest—the moral compromise of rescuers confronting an opponent who trades in opportunism …
Access Functionally hazardous and potentially hostile; requires careful boarding procedures and tactical oversight.
Grainy viewscreen images of a disabled vessel Flickering corridor lights and sparking junctions Sluggish power readouts and audible mechanical failures

Narrative Connections

How this event relates to others in the story

What this causes 3
Character Continuity

"Sonya doubts the plan but steps up and executes the decisive hydrogen bluff that saves Geordi."

Crimson Bluff — The Bussard Gambit
S2E17 · Samaritan Snare
Escalation

"News that Picard is near death heightens pressure, yet Riker doubles down on saving Geordi first."

Riker's Calculated Bluff to Save Geordi
S2E17 · Samaritan Snare
Escalation

"News that Picard is near death heightens pressure, yet Riker doubles down on saving Geordi first."

Countdown Bluff: Riker's Nonlethal Rescue
S2E17 · Samaritan Snare

Key Dialogue

"SONYA: Are you sure he can do it? He's an engineer, not a weapons specialist."
"DATA: Ongoing scanning indicates progressive weapons potential. The timing will be crucial. He must correctly interpret our intentions."
"WORF (V.O.): I am receiving an emergency summons from Starbase five one five... Captain Picard is close to death!"