Ambush and Escape: Danar's Transport Break
Plot Beats
The narrative micro-steps within this event
Worf ambushes Danar in the cargo bay, praising his cunning but declaring the battle over.
An explosion disables sensors and distracts Worf, allowing Danar to disarm him and initiate a fierce fight.
Danar overwhelms Worf but chooses not to kill him, instead escaping via transporter to the Angosian ship.
Who Was There
Characters present in this moment
Shocked and off‑balance; procedural composure is broken by the unexpected appearance of a fugitive aboard his vessel.
Wagnor appears stunned aboard his ship's cockpit when Roga materializes in his aft compartment — his presence ties the Angosian transport into the escape and converts the diplomatic transfer into an immediate hostage/transfer complication.
- • Reassert control aboard his transport and secure his crew
- • Clarify legal custody and immediate safety concerns
- • Report or respond according to Angosian protocol
- • Custody transfers should be orderly and procedurally secure
- • An unexpected fugitive aboard his ship constitutes a breach of protocol
- • Angosian authorities must be informed and involved
Gravely concerned and controlled; an emerging moral outrage tempered by procedural restraint as he contends with the political consequences of the escape.
Picard issues containment orders from the bridge (posting guards at emergency airlocks), asks Data to verify Danar's location, and accepts the grim reality when informed tracking is impossible — balancing command authority with the diplomatic stakes of the escape.
- • Prevent shipboard breach and external escape routes
- • Preserve diplomatic protocol with Angosian authorities
- • Obtain reliable tracking data to continue custody
- • Chain of command and procedure are essential in crisis
- • Failure to track Danar endangers both crew safety and diplomatic relations
- • Moral responsibility compels thorough investigation even under pressure
Clinically concerned and frustrated by systemic failure; composed but aware of the tactical implications of information loss.
Data detects and announces the Jefferies‑tube explosion and the resulting external sensor failure, attempts to route control to backups but reports he cannot transfer control or verify Danar's location, conveying the technical blackout to command.
- • Diagnose and restore sensor/control functions
- • Provide accurate situational data to command
- • Enable pursuit by recovering backup systems
- • Technical systems should supply objective situational awareness
- • Backup pathways exist but may be compromised under physical damage
- • Command must have reliable sensor data to make lawful tactical decisions
Alert, authoritative shifting to stunned and disoriented; professional composure fractures into shock and pain as he is defeated but still dutifully reports the breach.
Worf leads the cargo‑bay sweep, confronts Danar with a phaser, is thrown off balance by the Jefferies‑tube explosion, is disarmed and knocked nearly unconscious by Danar, discovers the jury‑rigged phaser in the transporter console and reports the escape to the bridge.
- • Secure and detain the intruder
- • Protect shipboard assets (photon launchers, airlocks)
- • Inform command and preserve chain of custody
- • The intruder is best controlled through direct force and Starfleet procedure
- • Security protocol and immediate containment can prevent political fallout
- • Starfleet systems (transporters/sensors) will reliably support containment
Focused and suspicious; professional impatience at technical limitations and a drive to convert incomplete data into actionable plans.
Riker suggests tactical implications (the missing pressure suit implies external entry), reacts to Data's sensor report by urging backup systems, and interprets Danar's escape as premeditated — moving quickly from tactical hypothesis to operational planning with Picard.
- • Identify Danar's method of escape
- • Coordinate immediate tactical responses and pursuit
- • Limit political fallout by anticipating Angosian reaction
- • Patterns (pressure suit missing) indicate deliberate planning
- • Quick tactical decisions can mitigate long‑term diplomatic damage
- • Starfleet must act decisively even with incomplete information
Objects Involved
Significant items in this scene
The discarded cargo bay pressure suit functions as the physical clue that triggers suspicion (missing suit implies external entry). It anchors Danar's concealment and indicates deliberate preparation for an external escape route.
The transporter pad in Cargo Bay Three becomes the physical stage for dematerialization — it responds to the jury‑rigged console and dematerializes Danar, converting the pad from routine equipment to the decisive escape mechanism.
Auxiliary backup systems (sensors & lighting) fail to pick up when primary feeds are knocked out by the Jefferies‑tube overload; Data attempts to route control but backups are unresponsive, turning a local outage into a shipwide information blackout.
The cargo transporter console is forcibly engaged by Danar as he runs past; its safety interlocks are overridden (via the jury‑rigged phaser lead) and it energizes the pad to effect the unauthorized transport to the Angosian ship, making it the mechanical enabler of his escape.
Photon torpedo launchers are referenced by Worf as potential exit points Danar might exploit; they serve narratively as a guarded defensive asset and a reminder of hard military options available to command.
A phaser is the improvised power source and weapon: it is used by Danar to disarm Worf, later found jury‑rigged into the cargo transporter circuitry to energize a beam. It is both the instrument of violence and the technical key to his escape.
Location Details
Places and their significance in this event
Shuttlebay Two is referenced as a plausible external entry/exit route implied by the missing pressure suit; it functions as an alternative explanation for how Danar might have bypassed posted guards.
The Jefferies Tube (section T‑nine‑five) is the site of the timed phaser overload explosion that disables lights and external sensors — a small, off‑axis conduit becomes the technical catalyst that creates the information vacuum Danar exploits.
Cargo Bay Three is the battleground and technical node where the confrontation, system failure and escape converge: crates provide concealment, the transporter console sits central to the action, and the bay’s industrial clutter enables ambush tactics and the improvisation of sabotage.
Decks Thirty‑Seven through Thirty‑Nine are invoked as the containment perimeter where Picard orders security posted at emergency airlocks to prevent external or internal egress, framing the shipwide containment response.
Narrative Connections
How this event relates to others in the story
"Worf's discovery of the missing pressure suit directly leads to the confrontation that allows Danar to escape via transporter."
"Worf's discovery of the missing pressure suit directly leads to the confrontation that allows Danar to escape via transporter."
"Worf's discovery of the missing pressure suit directly leads to the confrontation that allows Danar to escape via transporter."
"Worf's discovery of the missing pressure suit directly leads to the confrontation that allows Danar to escape via transporter."
Key Dialogue
"WORF: "You are cunning, Danar... you must have Klingon blood. But the battle is over.""
"ROGA: "My battle is never over.""
"DATA: "Explosion in Jefferies Tube section T-nine-five. All external sensors are inoperative.""
"WORF: "Worf to bridge. Danar has escaped. He used a phaser to power the cargo transporter. Coordinates indicate he beamed aboard the Angosian transport ship.""