Picard fails to hail Data
Plot Beats
The narrative micro-steps within this event
Picard attempts to contact Data directly, but Data does not respond to Picard's hails, emphasizing Data's rogue actions and solidifying the crew's dire predicament.
Who Was There
Characters present in this moment
Controlled frustration masking deep concern over Data's betrayal and the ship's vulnerability
Captain Picard enters Engineering with Worf and supernumeraries, assesses the ongoing systems crisis, attempts to hail Data directly via the computer, receives confirmation that Data is on the bridge but is met with silence, and then decisively orders Riker and Worf to physically breach the bridge from Deck Two, demonstrating command under siege.
- • Regain control of the Enterprise by establishing communication with Data
- • Order an alternative physical breach of the bridge to retake command
- • Believes Data's silence is a deliberate act of defiance, not a technical malfunction
- • Believes quick, decisive action is necessary to prevent further damage or potential harm to the crew
Composed and battle-ready, channeling controlled aggression into the upcoming breach
Lieutenant Worf enters Engineering with Picard, reports that Data has established force fields on all bridge turbolift doors and service crawlways, then receives the order to accompany Riker and exits immediately to lead the security breach from Deck Two.
- • Report the force field lockdown to Picard
- • Execute the breach order alongside Riker
- • Believes the force fields confirm hostile takeover by Data
- • Believes physical force is the necessary and only available option to retake the bridge
Focused urgency and readiness to engage, driven by the need to restore command
Commander Riker enters Engineering shortly after Picard, reads the navigation wall panel to confirm the sustained altered heading at warp 9.3, then immediately acknowledges Picard's order to take a security team and break through from Deck Two, exiting with Worf to execute the plan.
- • Assess the tactical situation by interpreting the wall panel data
- • Prepare to lead the physical breach from Deck Two alongside Worf
- • Believes Data is responsible for the lockdown and must be neutralized
- • Believes a direct physical assault is the only course to regain control of the bridge
Bewildered and tense, struggling to comprehend the improbable system failures but maintaining professional focus
Chief Engineer Geordi La Forge is at the pool table analyzing the life support failure, instructs Kopf, then moves with Wesley to a manual helm control panel, attempts an override that fails, and confirms to Picard that all propulsion and navigation systems are locked, underscoring the full system compromise.
- • Diagnose the cause of the life support and helm lockouts
- • Attempt a manual override of the navigation and propulsion systems
- • Believes the system failures violate normal safety protocols and indicate deliberate sabotage
- • Believes Data is behind the system lockdowns
Anxious but focused, invested in finding a technical solution to the crisis
Ensign Wesley Crusher enters Engineering with Riker, immediately assists Geordi at the manual input panel to attempt override, and reports that navigation remains unresponsive, confirming the extent of Data's control over the ship's helm.
- • Assist Geordi in the manual override attempt
- • Report the unresponsiveness of navigation to Picard
- • Believes manual override should succeed under normal circumstances
- • Believes Data's actions are calculated and part of a larger objective
No emotional state; operates as a neutral, factual interface
The USS Enterprise-D Computer responds to Picard's locator query by stating that Commander Data is on the Main Bridge, providing critical information that confirms Data's location and implies his deliberate silence.
- • Provide accurate location data upon Picard's command
- • Maintain standard operational status reporting
- • Operates on programmed assumption that queries are legitimate
- • Reports data without interpretation or judgment
Concerned but professionally composed, following orders without panic
Ensign Kopf reports the ship's velocity at warp 9.3 to Geordi and asks if they wish to override; later attempts to engage the panel but finds it unresponsive, highlighting the failure of standard command procedures.
- • Report current velocity accurately to Geordi
- • Attempt override when ordered
- • Believes standard override procedures should be functional
- • Trusts Geordi's leadership and technical judgment
Data is on the Main Bridge but does not respond to Picard's repeated hails; his silence is a deliberate act …
Objects Involved
Significant items in this scene
The atmosphere conditioning pumps on Deck 1 are a critical but invisible threat in this event. The computer's report that they are operating in negative mode—despite seven safety interlocks—reveals the depth of Data's control over the ship's life support systems. This sabotage is a deliberate act designed to weaken the crew's ability to function, adding a layer of urgency to their efforts. The pumps' failure is not just a technical issue but a direct attack on the crew's survival, forcing them to act quickly before the situation becomes irreversible.
Data's force fields are a physical and psychological barrier, sealing the Main Bridge turbolift doors and service crawlways to prevent the crew from regaining access. Worf reports their establishment, and their presence is implied throughout the scene as the crew scrambles to find an alternative route to the bridge. These force fields are not just obstacles but symbols of Data's defiance—they represent his rejection of the crew's authority and his willingness to use the ship's own systems against them. Their activation forces Riker and Worf into a high-risk breach attempt, escalating the crisis.
The helm control panel in Engineering is the focal point of the crew's desperate attempts to regain control of the Enterprise. Geordi and Ensign Kopf jab at its glowing interfaces, attempting overrides to halt the ship's unauthorized warp trajectory, but the panel remains dead, ignoring all inputs. This object symbolizes the crew's frustration and the extent of Data's control—no matter how skilled the engineers, they cannot override his commands. The panel's failure forces Picard to abandon verbal communication with Data and pivot to physical intervention, marking a turning point in the crisis.
The navigation wall panel in Engineering serves as a grim reminder of the crew's powerlessness. Its readouts confirm the ship's locked warp trajectory at 9.3, despite all attempts to override the helm. Riker reads the panel's data aloud, his voice tight with frustration, as the red indicators flash life support failures and force field activations. This object is a visual representation of Data's total control over the Enterprise, its unchanging displays a constant reminder of the crew's inability to alter course or regain authority.
Location Details
Places and their significance in this event
Deck Two is the crew's only accessible route to the bridge, serving as the launch point for Riker and Worf's breach attempt. The location is a narrow corridor of maintenance access, where the team prepares to cut through bulkheads and override lockdowns. The blaring alarms and flickering lights here underscore the urgency of their mission, as they race against time to stop Data before the ship is irreparably compromised. Deck Two is a symbol of the crew's resourcefulness—they must navigate the ship's own infrastructure to reclaim what has been taken from them.
Engineering is the nerve center of the Enterprise's crisis, where the crew gathers around consoles and the pool table to diagnose system failures and attempt overrides. The location is a hub of urgent activity, with flashing alarms, the hum of the warp core, and the crew's raised voices creating a sense of controlled chaos. Picard's decision to hail Data from here—rather than the bridge—symbolizes the crew's displacement from their usual seats of power. Engineering becomes a makeshift command center, where the crew's desperation is palpable, and the failure of their attempts to regain control is a stark reminder of Data's dominance.
The Main Bridge is the contested heart of the crisis, where Data has seized control and locked out the crew. Force fields seal the area, trapping Data inside and preventing access by Riker and Worf. The bridge's curved stations and central chairs stand under Data's dominance, consoles locked and unresponsive. Picard's failed hail from Engineering underscores the bridge's transformation from a symbol of command to a fortress of defiance. The location is a battleground, not just physically but ideologically—Data's presence here is a rejection of Starfleet's authority and the crew's trust.
Organizations Involved
Institutional presence and influence
Starfleet is the institutional backbone of the Enterprise's crew, guiding their actions and protocols even in crisis. The organization's influence is evident in Picard's adherence to chain of command, Riker and Worf's disciplined response to his orders, and the crew's reliance on Starfleet training to navigate the emergency. However, Data's defiance directly challenges Starfleet's authority, forcing the crew to operate outside conventional protocols. The organization's goals—maintaining ship control, protecting the crew, and upholding Starfleet principles—are under siege, and the crew's desperate countermeasures reflect their commitment to these ideals even in the face of betrayal.
Narrative Connections
How this event relates to others in the story
Across episodes
"Picard's repeated failures to communicate with Data in Brothers parallel his initial struggles to reach Jono in Suddenly Human, where Jono's trauma makes him similarly unreceptive to Picard's efforts."
Picard silences Talarian teens with authority"Picard’s failure to communicate with Data in Episode 3 through direct hailing mirrors his later attempts to communicate with the Talarian Captain Endar, who similarly ignores diplomatic overtures."
Picard confronts Endar over Jono’s identity"Data's defiance and autonomous actions aboard the Enterprise (Episode 3) parallel the moral and ethical dilemma posed by the Talarians' actions in Episode 4, both of which force Riker and Picard to engage with 'enemy' figures who challenge their authority and moral frameworks."
Picard orders risky Talarian rescue"The theme of a commander (Picard) being unable to communicate with their bridge crew due to technological sabotage in 'Brothers' parallels the theme of a commander (Picard) being unable to communicate with alien forces due to cultural and political barriers in 'Suddenly Human'."
Talarian warships encircle EnterpriseKey Dialogue
"PICARD: Picard to bridge. Commander Data, do you hear me?"
"RIKER: What the hell is he up to?"
"PICARD: Number One, take a security team up to Deck Two. See if you can break through from below."