Fabula
S7E19 · Genesis
S7E19
· Genesis

Picard and Data discover the Enterprise missing

After a three-day search for a lost torpedo, Picard and Data return to the prearranged coordinates in their shuttlecraft, only to find the Enterprise inexplicably absent. Data’s scans confirm the ship’s disappearance, leaving no trace of its location or status. Picard’s initial assumption of a delay is quickly dismissed as Data fails to raise the ship on any communication channel. The absence of the Enterprise—and with it, the crew’s only hope for reversing the de-evolution—plunges the duo into a crisis. The moment forces Picard to confront the reality that their mission has just become exponentially more dire: without the ship, they lack the resources, medical facilities, and crew expertise needed to synthesize the retro-virus. The scene underscores the fragility of their situation, shifting the narrative from a race against time to a fight for survival in an unknown, potentially hostile environment. The tension escalates as Picard’s leadership is tested—he must now decide how to proceed with limited information and dwindling options, while Data’s analytical precision highlights the gravity of their predicament. This event serves as a narrative turning point, transforming the story from a contained crisis aboard the Enterprise into a desperate, open-ended struggle for Picard and Data to reunite with their crew—or find another way to save them.

Plot Beats

The narrative micro-steps within this event

2

Picard and Data are en route back to the Enterprise after a three-day search for a stray torpedo.

normal to concerned ['SHUTTLECRAFT']

Data discovers that the Enterprise is not at its pre-arranged coordinates and cannot be reached through any communication channels, prompting Picard to order a scan of the vicinity.

concerned to worried ['SHUTTLECRAFT']

Who Was There

Characters present in this moment

1

Analytical detachment with underlying curiosity. Data is not afraid, but the discrepancy between expectation and reality triggers a subroutines-level inquiry: What protocol governs a starship’s disappearance? His emotional state is secondary to his need to resolve the anomaly.

Data sits at the shuttlecraft’s helm, his golden eyes flickering as he processes the anomaly. His fingers move with precision over the console, but his voice carries an uncharacteristic note of puzzlement—'I do not know'—as he fails to raise the Enterprise on any channel. When Picard orders the scan, Data complies without hesitation, his attention narrowing to the task. The absence of the ship doesn’t provoke fear in him, but it does introduce a variable his positronic brain cannot immediately reconcile: a starship does not vanish without explanation. His confusion is not emotional but logical, a glitch in the expected sequence of events.

Goals in this moment
  • Execute Picard’s orders to scan for the *Enterprise* with maximum efficiency, leveraging all available sensors.
  • Identify the cause of the *Enterprise*’s absence to restore logical continuity and aid Picard’s decision-making.
Active beliefs
  • The *Enterprise*’s disappearance is explicable through systematic analysis; no phenomenon is beyond detection if the correct parameters are applied.
  • Picard’s authority must be deferred to, even in unprecedented situations, as his human judgment may fill gaps in Data’s logical framework.
Character traits
Unshakable focus on problem-solving Clinical detachment in crises Curiosity about the illogical Reliance on Picard’s direction when protocols fail
Follow Data's journey

Objects Involved

Significant items in this scene

2
Shuttlecraft Thirteen

The recovered photon torpedo, now secured in the shuttlecraft, is a hollow victory. Its retrieval was the mission’s original purpose, but its presence aboard the shuttlecraft is a bitter reminder of how quickly priorities have shifted. The torpedo’s functional role is obsolete—it cannot help reverse the de-evolution or locate the Enterprise—yet it occupies physical space, a tangible symbol of the crew’s misplaced efforts. Its involvement is symbolic: it represents the futility of past actions in the face of the current crisis, a relic of a time when the Enterprise’s problems were solvable.

Before: Recovered and stowed aboard the shuttlecraft, its mission …
After: Irrelevant to the immediate crisis; its presence is …
Before: Recovered and stowed aboard the shuttlecraft, its mission complete.
After: Irrelevant to the immediate crisis; its presence is a distraction from the urgent need to find the Enterprise or devise an alternative solution.
USS Enterprise-D Tactical Systems (Including Weapon System Upgrades)

The Enterprise’s weapon upgrades, once a symbol of tactical readiness and operational confidence, now serve as a cruel irony. Their presence in the ship’s logs—mentioned in Picard’s supplemental log—highlights the crew’s misplaced focus on mechanical threats while an organic crisis (the de-evolution) unfolds. The upgrades are irrelevant here; the shuttlecraft’s sensors, though advanced, cannot compensate for the Enterprise’s vanished medical and scientific capabilities. The object’s involvement is passive but thematically resonant: it underscores the narrative’s shift from external conflict to internal survival, where Starfleet’s weapons are useless against biological mutation.

Before: Functional and logged as operational in the Enterprise’s …
After: Irrelevant to the immediate crisis; their absence aboard …
Before: Functional and logged as operational in the Enterprise’s tactical systems, though physically aboard the missing starship.
After: Irrelevant to the immediate crisis; their absence aboard the shuttlecraft reinforces the crew’s vulnerability.

Location Details

Places and their significance in this event

1
Shuttlecraft (Rogue Torpedo Retrieval Mission)

The shuttlecraft’s interior, once a functional and somewhat sterile workspace, transforms into a claustrophobic chamber of dread. The hum of the consoles, the glow of the viewports, and the confined space amplify the isolation Picard and Data now face. The location’s practical role shifts from transit vehicle to last refuge, its limited resources (fuel, sensors, life support) suddenly critical. Symbolically, the shuttlecraft embodies the crew’s fragility: a speck of technology in the vastness of space, with no safety net. The absence of the Enterprise outside the viewport turns the shuttle into a metaphor for human (and android) insignificance in the cosmos.

Atmosphere Tense and oppressive, with a creeping sense of dread. The shuttle’s usual efficiency feels like …
Function Last refuge and only operational base for Picard and Data, though severely limited in capabilities.
Symbolism Represents the crew’s sudden vulnerability and the fragility of their mission. The shuttle, once a …
Access Restricted to Picard and Data; no other crew members or external entities can enter.
The hum of the shuttle’s consoles, a constant reminder of their limited resources. The viewport showing empty space where the Enterprise should be, amplifying the sense of abandonment. The cramped interior, making the absence of the crew feel even more acute.

Narrative Connections

How this event relates to others in the story

What this causes 1
NARRATIVELY_FOLLOWS

"Picard and Data's journey back to the Enterprise and their observation that it is adrift creates suspense for the audience, before entering."

Picard manually docks with the stricken Enterprise
S7E19 · Genesis

Part of Larger Arcs

Key Dialogue

"PICARD: ((V.O.)) Captain's Log, supplemental. Commander Data and I have recovered the stray torpedo after a three-day search. We are enroute back to the *Enterprise*."
"DATA: Captain, the ship is not at the pre-arranged coordinates."
"PICARD: Have they been delayed?"
"DATA: I do not know. I am unable to raise them on any communication channel."