USS Enterprise (NCC-1701-D)
Sub-Locations
Detailed Involvements
Events with rich location context
The USS Enterprise as a location (the ship as whole) provides the physical platform whose maneuvering and status enable the transfer; its decks, transporter room and systems are implicated by the decision to commence personnel movement.
Procedural calm shipwide with focused readiness localized to the bridge and transporter areas.
Mobile base of operations and staging area for personnel transfers between starbase and ship.
Represents Federation order and institutional safety that underwrites risky diplomatic exchanges.
Transport and transfer areas operate under normal Starfleet security and access protocols.
The USS Enterprise as a location (the ship as a whole) functions as a mobile diplomatic platform and a protective institution. It stages the transfer, houses the bridge procedures, and provides the logistical and hierarchical context that lets Riker volunteer and then depart for the Klingon exchange.
Professional, well‑ordered, and mission‑oriented — a vessel prepared to convert routine navigation into diplomatic action.
Operating base and logistic support for the transfer; it physically positions itself near the starbase and provides personnel and systems for the exchange.
Represents Federation reach and Starfleet institutional reliability in frontline diplomacy.
Shipboard access subject to Starfleet protocols; movement for off‑ship transfers requires authorization and coordination with the starbase.
The USS Enterprise is the organizational home and protective locus for Data and Picard; the ship's identity and command norms frame Picard's objections and provide the stakes—loss of Data means loss to the vessel and crew.
Operationally steady but morally unsettled as command protocol clashes with crew loyalty.
Home base and protective institution whose custody is being challenged by external orders.
Embodies crew cohesion and the moral obligations of command.
Enterprise command authority normally controls crew movements; pending transfer threatens that control.
The USS Enterprise is the broader setting and institutional home of Data and Picard; the ship's identity as protective vessel frames Picard's resistance to off-ship reassignment and provides context for the conflict between individual crew loyalty and Starfleet authority.
Humming, functional, and suddenly politicized — the ship's routines are disrupted by the legal imposition.
Ally/protective institution for Data and Picard; the locale being compelled to yield personnel by external orders.
Embodies family/community loyalty that clashes with bureaucratic reach.
Operates under Starfleet regulations; internal areas like the Observation Lounge are limited to senior staff.
The USS Enterprise is referenced as being in parking orbit, framing the dispute: Picard's crew member is aboard that ship and the ship's systems are used as legal analogies—Enterprise's presence makes the conflict immediate and operationally consequential.
Distant but present; the ship's hum is an implied backdrop that adds urgency to procedural choices.
Contextual locus of the contested subject (Data) and the operational consequences of any ruling.
Represents the living community and practical realities affected by abstract legal decisions.
Operational vessel under command authority; standard Starfleet chain of command applies.
The Enterprise is present only as contextual backdrop—parked in orbit near Starbase 173—but functions narratively as Data's home and the institutional body whose regulations are being invoked and defended by Picard.
A restrained mechanical hum looms in the background; the ship is both refuge and site of bureaucratic challenge.
Symbolic locus of the crew's loyalty and the organization whose rules and culture are at stake in the dispute.
Represents community, operational context, and the human (and android) relationships endangered by legal reclassification.
Standard command-structure controlled access; not directly part of the JAG meeting but implicated.
The USS Enterprise is the institutional context framing the conversation: Picard's command, the vessel whose personnel and policies are threatened by the precedent he names. The ship's bureaucratic identity presses on his private feelings and decisions.
Underlying hum of shipboard life—mechanical heartbeat beneath the intimate scene.
Broader organizational stage—the employer and chain of command whose rulings will implement the legal precedent discussed.
Embodies institutional power and the bureaucratic systems that can convert individuals into property if precedent allows.
Standard Starfleet access controls in effect across the ship, though Ten-Forward itself is open to crew.
The USS Enterprise as a whole provides institutional resources — tractor control, medical teams, and engineering expertise — and it is the entity threatened by the temporal anomaly. Decisions made in the bay reverberate to the ship's mission and safety.
A living vessel with a low mechanical heartbeat, its systems and people collectively tense and responsive to emergent threat.
Employer and protector; the platform whose continuity is at stake and which must marshal departments to diagnose the problem.
Represents institutional continuity and the moral burden of command responsible for crew and mission.
Ship-wide protocols apply; access to certain engineering and medical systems requires authorization.
The USS Enterprise as a location/institution frames the event — the ship's systems provide tractor power and diagnostic resources, and its command structure is being invoked to investigate a problem that may directly threaten the vessel's timeline and hierarchy.
A ship under sudden strain: low mechanical heartbeat, procedural urgency, and the ripple of alarm across decks and consoles.
Home base and authoritative center whose resources and chain of command will manage the crisis.
Embodies institutional responsibility, duty, and the moral burden falling on Picard and his officers.
Normal Starfleet hierarchical access applies; incident mobilizes senior officers and specialists.
Transporter Room 4 is named as the procedural destination for the illicit beam-off. It functions as a focused, rule-bound gateway where a hazardous device might be received and immediately routed or neutralized—its invocation converts Wesley's private problem into a shipboard protocol decision.
Implied clinical and taut with quiet procedural risk; a controlled space for potentially dangerous operations.
Planned disposal destination and procedural waypoint for particalizing or otherwise neutralizing the orb.
Represents institutional procedure and the thin line between sanctioned safety measures and covert improvisation.
Operationally restricted area for trained transporter technicians; not freely accessible to all crew without authorization.
USS Enterprise Transporter Room 4 functions as the containment threshold and operational hub for the emergency: it receives the away team's beam-up request, runs diagnostics on the incoming matter stream, and becomes the point where the microbial threat is first registered and acted upon.
Clinical, tense, with a sudden spike of mechanical alarm urgency that replaces routine calm.
Containment control point and extraction/triage hub where technical diagnostics and procedural decisions are made.
Represents the limits of shipboard technology and institutional procedures when confronted with the unknown; a gate between field exposure and ship safety.
Restricted to transporter crew and authorized personnel during operations; functions under transporter chief control.
Transporter Room 4 serves as the extraction point and containment threshold where diagnostics are read and decisions are made; the room transforms from routine operational space to a focused control center managing a potential biological threat, crowding consoles and technicians around an alarming readout.
Tense, clinical, and alert — a procedural hush punctuated by alarms and terse, technical exchanges.
Operational hub and containment decision point for the attempted medevac and subsequent biohazard response.
Embodies institutional authority and technological mediation between the organic (Riker's infected body) and the ship's engineered safety systems.
Restricted to authorized transporter technicians, command, and medical personnel; not open to general crew during emergency protocols.
The transporter room serves as the operational crucible where technical procedure, medical urgency, and interpersonal duty collide; its instruments, hum, and consoles create a controlled yet tense environment that forces a moral-technical choice to be made.
Tension-filled and clinical—quiet urgency, low electrical hum, and focused personnel exchanging clipped dialogue.
Staging area and decision point for the risky away operation — where authorization, instrumentation, and personnel converge to initiate transport.
A threshold between institutional safety and biological unpredictability; the room symbolizes the ship's technological control confronting organic threat and personal loyalty.
Restricted to authorized crew and technical staff; staffed by transporter personnel and mission team members.
USS Enterprise Transporter Room 4 functions as the extraction hub receiving desperate calls from the Batris; Tasha at the consoles battles interference, attempts to lock on, and represents the technical lifeline whose failure or success will determine survival.
Clinical urgency — console lights, low electric hum, alarm flares; tense, focused technicians struggling under electronic interference.
Evacuation control hub; the only means by which the away team can be rematerialized off the Batris.
Embodies the thin margin between rescue and loss — technology as both salvation and fragile vulnerability.
Restricted to transporter technicians and senior bridge-authorized personnel during emergency operations.
USS Enterprise Transporter Room 4 functions as the remote lifeline: technicians and Tasha struggle to obtain a lock, fine-tune equipment, and fight interference. The room's efforts directly determine whether the trapped away team survives, converting technical failure into dramatic jeopardy.
Clinical panic and tense concentration — cold console light, low electric hum, rapid button-pushing and frustrated expressions as alarms and interference compromise procedure.
Rescue hub and technological lifeline attempting to extract personnel over distance under degraded conditions.
Represents institutional safety and technological authority that is nevertheless fallible under hostile conditions.
Restricted to transporter technicians and senior bridge or engineering officers; operations are tightly controlled and monitored.
The USS Enterprise in Orbit Around Ventax II provides the macro-context for this micro-strategic exchange. While the ready room is the immediate setting, the ship’s orbit above the planet serves as a reminder of the stakes: Picard and Data are not merely debating theory, but preparing to intervene in a crisis unfolding on the surface. The Enterprise’s steady systems and sensor links to Ventax II ground their analysis in real-time data, while its resources—databases, legal archives, and crew expertise—equip them to counter Ardra’s influence. The location’s role extends beyond a backdrop; it is the operational base from which Starfleet’s rationalism will challenge Ventaxian superstition.
Detached yet urgent, the ship’s ambient hum and the distant wail of Ventaxian sirens (heard via sensors) create a dissonance between Starfleet’s order and the planet’s chaos. The orbit symbolizes both a vantage point and a barrier—Picard and Data are close enough to act, but must rely on data and strategy rather than direct intervention.
Operational hub for Starfleet’s response to the Ventax II crisis, providing the crew with the tools, data, and isolation needed to counter Ardra’s psychological domination of the planet.
Embodies the tension between observation and action, rationality and emotion, and the distance between Starfleet’s ideals and the Ventaxians’ plight.
Restricted to authorized Starfleet personnel; the ready room’s privacy ensures their debate remains confidential, while the ship’s systems are accessible only to cleared officers.
The USS Enterprise in Orbit Around Ventax II serves as the distant but ever-present backdrop to this debate. While the ready room is the immediate setting, the ship's steady orbit above Ventaxia symbolizes Starfleet's role as an external force of logic and order in a crisis fueled by superstition. The Enterprise's sensors and databases provide the empirical tools Picard and Data rely on—legal archives, historical records, and scientific analysis—to challenge Ardra's claims. The ship's humming systems and sensor links to the surface create a subtle but constant reminder that their debate is not abstract but tied to real-world consequences: the fate of Ventaxia and its people. The orbit itself is a metaphor for their position—close enough to intervene, but not yet fully engaged in the planet's turmoil.
Detached yet tense. The ship's usual operational hum feels muted, as if the crew is holding its breath, awaiting Picard's next move. The orbit is stable, but the stakes below are volatile, creating a dissonance between the Enterprise's calm and Ventaxia's chaos.
Logistical and intellectual support system for Picard and Data's debate. The ship's resources—databases, sensors, and crew—equip them to counter Ardra's supernatural claims with precision and resolve. It is both a refuge from Ventaxia's turmoil and a platform for their intervention.
Embodies the clash between reason and myth. The Enterprise represents Starfleet's rationalist worldview, orbiting above Ventaxia like a beacon of logic in a sea of superstition. Its presence underscores the high stakes: Picard and Data are not just debating philosophy, but preparing to act in a crisis that could have galactic repercussions.
Restricted to authorized personnel. The Enterprise is a secure environment, but its systems are accessible to Picard and Data for their research, reflecting Starfleet's trust in their judgment.
The USS Enterprise in Orbit Around Ventax II provides the operational backdrop for this scene, its steady presence above the planet a metaphor for Starfleet’s role as an impartial observer and potential arbiter. The ship’s orbit is not just a physical location but a symbolic vantage point, allowing Picard and Data to analyze the Ventaxian crisis with detachment and precision. Its systems—sensor links, databases, and transporter networks—equip them with the tools to counter Ardra’s psychological manipulation, reinforcing the theme of reason triumphing over superstition. The orbit also creates a sense of urgency, as the Enterprise’s resources are finite and the Ventaxians’ deadline looms.
A blend of clinical efficiency and quiet tension. The ship’s steady hum and the distant glow of Ventax II through the viewport create a mood of focused resolve, where every action feels measured and deliberate. The orbit itself is a liminal space—neither fully engaged in the Ventaxian conflict nor entirely detached, mirroring Picard’s own ambivalence about Ardra’s claims.
Operational base and resource provider for Picard and Data’s investigation. The Enterprise’s databases, sensors, and legal archives are critical to their effort to expose Ardra’s fraud, while its orbit ensures they remain close enough to intervene if necessary.
Embodies Starfleet’s ideals of exploration, diplomacy, and rational inquiry. The ship’s presence above Ventax II symbolizes the tension between external intervention and respect for local autonomy, as well as the struggle between fear and self-reliance that defines the episode’s central conflict.
Restricted to authorized Starfleet personnel. The Enterprise’s security protocols and chain of command ensure that only those with clearance can access its systems and resources, maintaining the integrity of their investigation.
The USS Enterprise serves as the broader technological and cultural framework for Data’s romantic experiment. Its advanced computing systems enable Data’s multitasking and computational modeling of love, while its institutional protocols shape his interactions with Jenna. The ship’s presence looms in the background, reinforcing the contrast between Data’s mechanical nature and Jenna’s organic emotional needs.
Sterile and data-driven, contrasting with Jenna’s cluttered, warm quarters.
Technological and cultural framework for Data’s experiment
Represents the institutional and technological environment that enables Data’s detached, computational approach to romance.
Open to crew members but governed by Starfleet protocols.
Events at This Location
Everything that happens here
The Enterprise drops out of warp and Riker yards the ship into precision approach, shifting the crew from long‑haul transit to a focused diplomatic operation. Data assumes command while Wesley …
As the Enterprise drops out of warp at Starbase 179, Riker formally relinquishes the bridge to Commander Data and dispatches Ensign Wesley Crusher to accompany him for a high‑stakes personnel …
In the Observation Lounge Maddox outlines a step-by-step plan to disassemble Data for study. Data methodically probes technical gaps—most notably unresolved electron resistance across neural filaments—exposing that Maddox's model is …
What begins as a technical and moral debate over Data's disassembly abruptly becomes enforceable command when Commander Maddox produces authenticated Starfleet transfer orders reassigning Data to Starbase 173. Picard's moral …
In the JAG office Picard converts a procedural squabble into a constitutional moment. Maddox argues for commandeering Data as property for scientific progress, Phillipa probes the legal basis, and Picard …
In the JAG office Picard confronts Commander Maddox and Captain Phillipa Louvois as Maddox bluntly insists Data is a machine and must not be allowed to resign for the sake …
Late in Ten-Forward a defeated Picard sits alone until Guinan quietly breaks his isolation. Through gentle questions she teases out a confession — the old humiliation of the Stargazer court-martial …
A derelict shuttle is winched into Shuttle Bay Two and the crew's curiosity turns to dread when Riker reads its registration: it is the Enterprise's own shuttle — twice. Inside …
A derelict Enterprise shuttle is beamed into Bay Two carrying an unconscious duplicate of Captain Picard. Pulaski's scans register the duplicate's brainwaves as "out of phase," while Data discovers the …
Wesley furtively removes a delicate antimatter containment orb from his personal station and, nervously overtalking to cover his transgression, declares it 'ruined' so he can justify immediate disposal. Burke pushes …
On a routine surface survey Geordi finds Commander Riker favoring his leg, a small puncture and a speck of blood. Riker jokes to minimize it; Geordi responds with procedural caution, …
During an otherwise routine extraction, O'Brien's transporter console flashes a biohazard alarm: unidentified microbes have been detected in Commander Riker's tissue and the ship's biofilters cannot screen them. Geordi's precautionary …
In the transporter room Data, Geordi and O'Brien make a terse, high-stakes decision: Data initially argues cold logic — he should go alone to minimize biological exposure — but Geordi …
Riker cuts formalities and drives a chaotic evacuation as debris and a boiling gas cloud compress the team's escape route. Data finds a faster exit, discovers a barely-alive survivor, and …
An urgent beam-out collapses into chaos when transporter interference and collapsing debris cut off the away team's escape. Riker pushes protocol aside, insisting on evacuation while Data and Geordi locate …
In the captain’s ready room, Picard privately records his determination to expose Ardra as a fraud, framing her as a sophisticated confidence artist exploiting Ventaxian superstition. He then summons Data …
In the captain’s ready room, Picard privately records his skepticism of Ardra’s claims, framing her as a fraud exploiting Ventaxian superstition. When Data arrives, Picard outlines his theory that Ardra’s …
In the captain’s ready room, Picard—still skeptical of Ardra’s claims but privately conceding the possibility she could be the ancient Ventaxian devil—tasks Data with finding a legal loophole in the …
In Jenna’s quarters, Data arrives performing an exaggerated, scripted version of a solicitous partner—offering drinks, tidying her space, and reciting rehearsed compliments—all delivered with mechanical precision that betrays his lack …