Droid Executive Responses Wireless Unavailable
Applicable alarms (1)
Likely outcomes — click to expand
Based on 581,029 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 5,238 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 623
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 421
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 330
- Reset Droid after DLB · REPAIR 293
- V4 Zipping Point: Inspect Zipping Point after Droid Left Behind (DLB) - Ranger · MAINTENANCE_ACTION 159
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 1,229 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 1,206 |
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 999 |
| WING STBD DEPOP, ZIP, P2 | 25266 | 648 |
| WING PORT, ZIP, P2 | 24762 | 648 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The DROID_EXECUTIVE_RESPONSES_WIRELESS_UNAVAILABLE alarm occurs when Zip Executive has lost Droid executive responses over the wireless response path.
This alarm is expected to be set while the Aircraft is idle. Use this guide only when the alarm appears during a mission that exercises the Droid.
Exec watchdog alarm
Section titled “Exec watchdog alarm”- DROID_EXECUTIVE_RESPONSES_WIRELESS_UNAVAILABLE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-this-a-repeat-issue{"<small><b>Step 1</b></small><br/>Question: Is this a repeat issue? Check Fleetwr..."}
power-cycle-the-droid["<small><b>Step 2</b></small><br/>Action: Power cycle the Droid Power Cycle D..."]
wait-for-the-droid-to-fully-boot-back["<small><b>Step 3</b></small><br/>Action: Wait for the Droid to fully boot back..."]
the-aircraft-may-return-to-service("<small><b>Step 4</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-embedded-linux-repeat-issue{{"<small><b>Step 5</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
is-this-a-repeat-issue -->|Yes| escalate-to-embedded-linux-repeat-issue
is-this-a-repeat-issue -->|No| power-cycle-the-droid
power-cycle-the-droid --> wait-for-the-droid-to-fully-boot-back
wait-for-the-droid-to-fully-boot-back --> the-aircraft-may-return-to-service
style is-this-a-repeat-issue fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-for-the-droid-to-fully-boot-back fill:#dcfce7,stroke:#22c55e,color:#14532d
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-embedded-linux-repeat-issue fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.