Fabula
S6E4 · Relics
S6E4
· Relics

Scott demands his lost ship

After leaving Ten Forward drunk and disoriented, Scott stumbles to the Holodeck, desperate to recreate the bridge of his beloved USS Enterprise (NCC-1701). His frustration mounts as the computer’s impersonal prompts force him to confront the reality that his past—even its registry number—has been overshadowed by progress. The exchange underscores his alienation in the 24th century, where technology has moved on without him, and his stubborn insistence on precision only deepens his sense of irrelevance. The scene foreshadows his struggle to reconcile his legacy with a future that no longer needs him, setting up his eventual confrontation with his own obsolescence.

Plot Beats

The narrative micro-steps within this event

3

Carrying a bottle and glass from Ten Forward and slightly drunk, Scott arrives at the Holodeck, ready to try and experience his old ship.

hope to determination ['Holodeck doors']

Scott struggles with the Holodeck computer, unable to initially specify the correct parameters to load his old ship's bridge.

frustration to resolve

Growing impatient, Scott angrily specifies the exact registry number of his Enterprise, pointedly differentiating it from later iterations.

annoyance to satisfaction

Who Was There

Characters present in this moment

2

None (as an AI). However, its responses function as a narrative device to highlight Scott’s alienation—the computer’s lack of recognition or empathy mirrors the 24th century’s indifference to his legacy.

The Enterprise-D computer responds to Scott’s commands with clinical precision, its voice neutral and uninflected. It first requests ‘program parameters,’ then lists the five Enterprises as if reciting a catalog, before finally conceding to Scott’s demand for NCC-1701. Its ‘Program complete’ acknowledgment is devoid of warmth or recognition, treating Scott’s emotional plea as just another input to process. The computer’s impersonality underscores the gulf between Scott’s romanticized past and the sterile efficiency of the 24th century.

Goals in this moment
  • To fulfill Scott’s request with the minimum necessary interaction, adhering to Starfleet protocols.
  • To operate as a neutral interface, unaffected by the emotional weight of Scott’s demands.
Active beliefs
  • That all requests must be processed through standardized parameters (e.g., registry numbers).
  • That historical context (e.g., Scott’s attachment to NCC-1701) is irrelevant to operational function.
Character traits
Impersonal Logically rigid Unemotional Bureaucratic Responsive but indifferent
Follow USS Enterprise-D …'s journey

A volatile mix of defiance and despair—his outburst masks a deep, gnawing fear of irrelevance, but the computer’s indifference leaves him momentarily hollow, as if the very ship he loved has been erased by progress.

Scott stands unsteadily outside the holodeck doors, green bottle and glass in hand, his face flushed with drink and frustration. He activates the bulkhead terminal with a drunken swagger, his voice slurring as he demands the computer recreate his Enterprise—only to be met with bureaucratic precision. His insistence on the registry number (NCC-1701) is less a technical correction than a desperate claim to identity, his hands gripping the terminal as if it’s the last tether to his past. The computer’s response—‘Program complete’—hangs in the air like a mockery, leaving him momentarily still, the weight of his obsolescence pressing down.

Goals in this moment
  • To recreate the bridge of the *original* USS *Enterprise* (NCC-1701) as a way to reclaim his identity and cope with displacement.
  • To assert his technical authority and knowledge, even if it’s futile, as a means of proving he still belongs in Starfleet.
Active beliefs
  • That his ship and his era represent the ‘true’ Starfleet—one of heroism and direct action, not bureaucratic protocols.
  • That the 24th century has no place for him, and that his skills (and thus his worth) are obsolete.
Character traits
Defiant Nostalgic Technically precise (even when drunk) Emotionally volatile Physically unsteady (drunkenness) Verbally combative (with the computer)
Follow Montgomery Scott's journey

Objects Involved

Significant items in this scene

1
Holodeck Corridor Interactive Computer Interface

The bulkhead computer terminal is the physical and narrative fulcrum of this event. Scott activates it with a drunken swipe, and it becomes the battleground for his clash with the 24th century. The terminal’s voice prompts—‘Please enter program,’ ‘Insufficient data’—are the embodiment of institutional indifference, forcing Scott to articulate his request in cold, technical terms. His insistence on the registry number (NCC-1701) turns the terminal into a symbol of the past he’s trying to reclaim, while its final ‘Program complete’ feels like a hollow victory. The terminal’s design (a wall-mounted interface) reinforces its role as an unyielding mediator between Scott’s emotions and the ship’s logic.

Before: Inactive, mounted on the corridor bulkhead near the …
After: Active but inert—it has processed Scott’s request and …
Before: Inactive, mounted on the corridor bulkhead near the holodeck doors. Ready to receive voice commands but otherwise dormant.
After: Active but inert—it has processed Scott’s request and awaits his entry into the holodeck. The interaction leaves it unchanged physically, but narratively, it has served as the catalyst for Scott’s confrontation with his own obsolescence.

Location Details

Places and their significance in this event

1
Holodeck Access Corridor (USS Enterprise-D)

The corridor outside the holodeck doors is a liminal space—neither the warmth of Ten Forward nor the escapism of the holodeck, but a transitional zone where Scott’s drunkenness and disorientation are laid bare. The narrow, metallic confines amplify his unsteadiness, the hum of the Enterprise-D’s engines a distant reminder of the ship’s indifference to his plight. The bulkhead terminal, mounted like a sentinel, becomes the focal point of his frustration, while the holodeck doors behind him symbolize the future’s empty promises. The corridor’s sterility contrasts with the lived-in grit of the original Enterprise, reinforcing Scott’s sense of being out of time.

Atmosphere Tense and claustrophobic, with a hum of distant engine noise. The air is thick with …
Function A transitional space where Scott’s internal conflict (past vs. present) plays out physically. It’s the …
Symbolism Represents the threshold between Scott’s past and the future he’s struggling to accept. The corridor’s …
Access Open to all crew, but in this moment, it feels like a private purgatory for …
The hum of the Enterprise-D’s engines, a constant but distant reminder of the ship’s indifference. The sterile, metallic bulkheads, reflecting the 24th century’s efficiency and lacking the warmth of the original Enterprise. The holodeck doors, slightly ajar or closed, symbolizing the future’s empty promises. The bulkhead computer terminal, mounted like a sentinel, its voice the only ‘presence’ in the corridor.

Organizations Involved

Institutional presence and influence

1
Starfleet

Starfleet’s influence permeates this event through the Enterprise-D’s computer, which operates under Starfleet’s protocols for holodeck access and data specificity. The computer’s insistence on the registry number (NCC-1701) reflects Starfleet’s bureaucratic evolution—where once a captain’s word might have sufficed, now precision and standardization are paramount. Scott’s frustration with the computer isn’t just personal; it’s a microcosm of his struggle with Starfleet’s institutional memory, or lack thereof. The organization’s presence is felt in the impersonal efficiency of the terminal, the holodeck’s ability to recreate the past, and the unspoken expectation that Scott adapt to its ways.

Representation Via institutional protocol (holodeck access rules, data specificity requirements) and through the Enterprise-D computer’s voice, …
Power Dynamics Starfleet exercises indirect authority over Scott in this moment. Its protocols (e.g., registry number requirements) …
Impact This event underscores the tension between individual legacy and institutional progress. Scott’s resistance to Starfleet’s …
Internal Dynamics None explicitly depicted, but the event hints at the broader institutional tension between honoring the …
To maintain operational efficiency and standardization across all starships, even in recreational systems like the holodeck. To ensure that historical data (e.g., ship registries) is accessed with precision, reflecting Starfleet’s commitment to accuracy and continuity. Through institutional protocols (e.g., holodeck program parameters, data specificity). Via the Enterprise-D computer, which enforces these protocols with neutral, unyielding logic. Through the symbolic weight of the holodeck itself—a tool that can recreate the past but cannot resurrect it, reinforcing Starfleet’s forward-looking ethos.

Narrative Connections

How this event relates to others in the story

What led here 2
Character Continuity

"Scott takes Data up on his offer and heads to the Holodeck."

Scott Rejects Synthetic Comfort
S6E4 · Relics
Character Continuity

"Scott takes Data up on his offer and heads to the Holodeck."

Scott Rejects Synthetic Comfort
S6E4 · Relics
What this causes 2
Causal

"Drunk, Scott retreats to the Holodeck to create a simulation of his old ship."

Scott confronts his obsolescence
S6E4 · Relics
Causal

"Drunk, Scott retreats to the Holodeck to create a simulation of his old ship."

Scott Rejects the Holodeck Illusion
S6E4 · Relics

Key Dialogue

"SCOTT: The android at the bar said you could show me my old ship... so lemme see it."
"COMPUTER VOICE: There have been five Federation ships with that name. Please specify by registry number."
"SCOTT: NCC-One-Seven-Oh-One. No bloody A, B, C, or D."