Fabula
S7E4 · Gambit, Part I

Enterprise Loses Contact with Away Team

The bridge crew of the Enterprise—led by Data in Riker’s absence—receives a frantic, garbled distress call from Geordi La Forge, who reports the away team is under attack. The transmission cuts off abruptly, replaced by static, as Romulan jamming disrupts all communications. Data immediately orders a transporter lock to extract the team, but the interference is too severe, leaving the crew powerless to intervene. The failure to establish contact or effect a rescue escalates the tension, deepening the mystery of Picard’s fate and the away team’s vulnerability. The scene underscores the crew’s helplessness and the escalating stakes of the mission, as the bridge crew is forced to confront their inability to protect their colleagues on the surface.

Plot Beats

The narrative micro-steps within this event

2

Geordi's comm signal breaks through reporting an attack, immediately followed by an abrupt loss of contact with the away team due to jamming.

urgency to concern

Data tries to ascertain the nature of the communications breakdown, and tasks the Transporter Room to lock onto the away team's signal, but is met with negative results due to the intense interference.

concern to frustration

Who Was There

Characters present in this moment

4

Panicked, desperate, and acutely aware of the away team's immediate danger

Geordi La Forge's voice, garbled and panicked, cuts through the bridge coms with the desperate plea 'Repeat, we are under attack...' before being swallowed by static. His transmission is the sole evidence of the away team's peril, a fleeting but visceral moment that forces the bridge crew into action. Though physically absent, his voice haunts the scene, a reminder of the stakes and the crew's inability to intervene.

Goals in this moment
  • Warn the *Enterprise* of the attack to trigger a rescue
  • Survive the assault long enough for extraction
Active beliefs
  • The *Enterprise* bridge is their only hope for survival
  • The attack is coordinated and potentially Romulan-backed
Character traits
Vulnerable (in this moment) Urgent and direct in communication Dependent on the bridge crew's response
Follow Geordi La …'s journey

Controlled concern with a hint of underlying frustration at the system's vulnerability

Ensign Giusti, stationed at Ops, reacts with focused urgency as Geordi's distress call is abruptly cut by static. She swiftly diagnoses the com system's integrity, confirming external jamming from the planet's surface. Her precise, no-nonsense demeanor contrasts with the rising tension, grounding the bridge crew with technical clarity.

Goals in this moment
  • Accurately diagnose the source of the communication disruption
  • Provide Data with actionable intelligence to mitigate the crisis
Active beliefs
  • The com system's malfunction is external, not a ship-wide failure
  • Data's leadership will guide the crew through the emergency
Character traits
Methodical Unflappable under pressure Technically precise Supportive of command authority
Follow Giusti's journey

Calm exterior masking deep concern for the away team's safety and frustration at the Romulan interference

Data, assuming command in Riker's absence, processes Geordi's distress call with calculated urgency. He methodically interrogates the situation—first verifying system integrity, then ordering a transporter lock—while maintaining a composed demeanor. His android precision masks the gravity of the moment, but his rapid-fire commands reveal the stakes. The failure to establish a lock leaves him momentarily silent, a rare pause in his usual fluid responses.

Goals in this moment
  • Restore communication with the away team to assess their status
  • Execute a successful transporter lock to extract the team from danger
Active beliefs
  • The away team's survival depends on immediate action
  • Romulan involvement is highly probable given the jamming technology
Character traits
Decisive under pressure Logically prioritized Emotionally restrained (but not detached) Protective of the crew
Follow Data's journey
Supporting 1

Frustrated and professionally disappointed, but maintaining composure

The Transporter Chief, though off-screen, delivers the crushing 'Negative, sir' in response to Data's order. His voice carries the weight of failure, a stark contrast to the bridge's usual efficiency. The interference from the planet's surface renders his equipment useless, leaving the away team stranded. His role, though secondary, underscores the crew's collective helplessness in the face of Romulan technology.

Goals in this moment
  • Attempt to establish a transporter lock despite the interference
  • Provide Data with a clear assessment of the situation
Active beliefs
  • The jamming is too sophisticated to overcome with current resources
  • Data will make the best strategic decision given the constraints
Character traits
Professionally resigned Technically competent but limited by external forces Supportive of Data's authority
Follow Transporter Officer's journey

Objects Involved

Significant items in this scene

3
Away Team-to-Bridge Communications System (Enterprise-D)

The Enterprise bridge comm system becomes the focal point of the crisis as Geordi's garbled distress call erupts through the speakers, only to be violently interrupted by Romulan jamming static. Ensign Giusti's diagnostic checks confirm the system itself is functional, redirecting attention to the external interference. The comm system's failure to relay critical information forces the crew into a state of helpless vigil, its usual reliability shattered by the Romulans' technological superiority.

Before: Operational, with standard subspace communication capabilities
After: Jammed and inoperative, filled with disruptive static, unable …
Before: Operational, with standard subspace communication capabilities
After: Jammed and inoperative, filled with disruptive static, unable to transmit or receive signals from the away team
Enterprise Transporter Lock (Away Team Rescue Attempt)

Data's order to lock onto the away team's transporter signal activates the Enterprise's transporter systems, but the Romulan jamming from the planet's surface renders them ineffective. The Transporter Chief's failed attempt to establish a lock symbolizes the crew's impotence, as the away team remains stranded. The transporter lock, usually a reliable tool for rescue, becomes a painful reminder of the Romulans' control over the situation.

Before: Functional and ready for standard away team extractions
After: Inoperative due to surface interference, unable to lock …
Before: Functional and ready for standard away team extractions
After: Inoperative due to surface interference, unable to lock onto or beam out the away team
Romulan Jamming Static on Bridge Comms

The Romulan jamming static bursts through the bridge comms, swallowing Geordi's distress call mid-sentence. This disruptive noise isn't just a technical obstacle—it's a psychological weapon, amplifying the crew's sense of isolation and urgency. The static serves as a constant, oppressive reminder of the Romulans' unseen presence and their ability to dictate the terms of the crisis. Its harsh, unrelenting nature mirrors the desperation of the moment.

Before: Absent; standard subspace communication channels are clear
After: Dominant and pervasive, filling the bridge with white …
Before: Absent; standard subspace communication channels are clear
After: Dominant and pervasive, filling the bridge with white noise, blocking all signals from the away team

Location Details

Places and their significance in this event

2
Transporter Room Two (USS Enterprise-D)

Transporter Room Two becomes a secondary hub of frustration as the Transporter Chief attempts—and fails—to lock onto the away team's signal. The compact bay, usually a place of precise operations, is filled with the weight of helplessness. The dark transporter pads remain inactive, a visual metaphor for the crew's inability to act. This location, though off-screen, mirrors the bridge's tension, reinforcing the theme of systemic failure in the face of Romulan technology.

Atmosphere Frustrated and tense, with a sense of urgent inactivity—equipment is operational, but the mission cannot …
Function Attempted rescue coordination point, rendered useless by external interference
Symbolism Embodies the crew's reliance on technology and its limitations when faced with superior adversaries
Access Restricted to authorized personnel; currently focused on the away team extraction attempt
Dark, inactive transporter pads Consoles displaying failed lock attempts Transporter Chief's voice reporting the inability to establish a lock
Greenish Planet Surface (Silva's Ship Crash Site)

The greenish planet's surface, though not physically present on the bridge, looms as a silent antagonist. Its jamming pulses disrupt all subspace links and scatter transporter beams, cutting Geordi's frantic distress call short. The location's unseen terrain isolates the away team, forcing the Enterprise bridge crew into helpless vigil. The planet's hostility is felt through the static and failed transporter locks, making it a battleground of technological warfare where the Romulans hold the advantage.

Atmosphere Tense, oppressive, and filled with unanswered questions—the bridge crew's focus is fixated on the unseen …
Function Source of Romulan jamming interference, blocking all communication and rescue attempts
Symbolism Represents the unseen threat and the crew's vulnerability to external forces beyond their control
Access Restricted to away team members; bridge crew cannot physically intervene due to jamming
Jamming pulses disrupting subspace communication Failed transporter locks preventing extraction Unseen terrain isolating the away team

Organizations Involved

Institutional presence and influence

2
Romulan Star Empire Forces

The Romulans' involvement is implied but palpable through their jamming technology, which disrupts all Enterprise communications and transporter locks. Their unseen presence looms over the bridge, dictating the terms of the crisis. The static-filled comms and failed rescue attempts serve as a reminder of the Romulans' capability to outmaneuver Starfleet, even from a distance. Their influence is exerted not through direct confrontation but through technological superiority, forcing the Enterprise crew into a reactive, defensive posture.

Representation Via technological disruption (jamming static, transporter interference) and implied tactical coordination (mercenary attack on the …
Power Dynamics Exercising dominance over the Enterprise crew through superior technology and unseen control of the battlefield
Impact The Romulans' actions highlight the asymmetry of power between the two factions, where Starfleet's ideals …
Internal Dynamics The Romulans operate with calculated precision, using mercenaries as deniable assets while maintaining plausible deniability …
Disrupt Starfleet operations to prevent interference with their objectives (likely artifact acquisition) Maintain secrecy and control over the away team's fate to advance their agenda Through advanced jamming technology, blocking all communication and rescue attempts By proxy (mercenaries attacking the away team, forcing the Enterprise into a defensive position)
Starfleet

Starfleet's protocols and values are tested as the Enterprise crew scrambles to respond to the away team's distress. Data's leadership reflects Starfleet's emphasis on rapid, decisive action under pressure, while the failed rescue attempt highlights the organization's vulnerability to advanced Romulan technology. The crew's adherence to chain of command—Data assuming authority in Riker's absence—underscores Starfleet's reliance on trained officers, even in crises. However, the inability to protect the away team forces a confrontation with the limits of Starfleet's capabilities.

Representation Through institutional protocol (chain of command, emergency response procedures) and the actions of its officers …
Power Dynamics Exercising authority over individual crew members (Data's commands) but being challenged by external forces (Romulan …
Impact The event exposes the tension between Starfleet's ideals (protection of its crew) and the harsh …
Internal Dynamics Chain of command is reinforced (Data assumes authority), but the crew's helplessness creates internal frustration …
Protect and extract the away team from the planet's surface Identify and neutralize the source of the Romulan jamming interference Through trained officers following emergency protocols Leveraging advanced technology (transporters, sensors) to assess and respond to the crisis

Narrative Connections

How this event relates to others in the story

No narrative connections mapped yet

This event is currently isolated in the narrative graph


Key Dialogue

"GEORDI'S COM VOICE: "Repeat, we are under attack...""
"GIUSTI: "Commander, we've lost contact with the Away Team.""
"DATA: "Is there a malfunction?""
"GIUSTI: "No, sir... the com system is being jammed...""
"DATA: "What is the source?""
"GIUSTI: "Somewhere on the surface...""
"DATA: "Bridge to Transporter Room Two. Can you get a lock on the Away Team?""
"TRANSPORTER CHIEF: "Negative, sir. There's too much interference.""