DROID_COMMS_UNHEALTHY
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 825 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 249 ZERP issues filed on these missions)
Top work orders
- EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 53
- Replace Droid in Aircraft · MAINTENANCE_ACTION 27
- Replace Droid Receiver Flex Harness (Receiver Ring) on Aircraft · MAINTENANCE_ACTION 13
- Displace and Reinstall Droid on Aircraft · MAINTENANCE_ACTION 11
- Install Droid on Aircraft · MAINTENANCE_ACTION 11
Frequently co-occurring alarms (% of the 825 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when the Aircraft Droid link state is intermittent or down, indicating comms issues between the Aircraft and the Droid. In this state, any missions involving the Droid (delivery, lower, raise, etc.) are likely to fail, so the recommended maintenance action should be taken.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft-and-the-droid["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
wait-for-a-minimum-of-two-2-minutes-fo["<small><b>Step 2</b></small><br/>Action: Wait for a minimum of two 2 minutes..."]
is-the-alarm-still-set{"<small><b>Step 3</b></small><br/>Question: Is the alarm still set?"}
reseat-the-droid["<small><b>Step 4</b></small><br/>Action: Reseat the Droid Reseat Droid/pro..."]
is-the-issue-resolved{"<small><b>Step 5</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-and-droid-may-return-to-service("<small><b>Step 6</b></small><br/>Reference: The Aircraft and Droid may return to ...")
follow-droid-to-aircraft-electrical-contacts-debugging["<small><b>Step 7</b></small><br/>Action: Follow Droid to Aircraft Electrical ..."]
the-aircraft-may-return-to-service("<small><b>Step 8</b></small><br/>Reference: The Aircraft may return to service.")
power-cycle-the-aircraft-and-the-droid --> wait-for-a-minimum-of-two-2-minutes-fo
wait-for-a-minimum-of-two-2-minutes-fo --> is-the-alarm-still-set
is-the-alarm-still-set -->|Yes| reseat-the-droid
is-the-alarm-still-set -->|No| the-aircraft-may-return-to-service
reseat-the-droid --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-and-droid-may-return-to-service
is-the-issue-resolved -->|No| follow-droid-to-aircraft-electrical-contacts-debugging
style power-cycle-the-aircraft-and-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-for-a-minimum-of-two-2-minutes-fo fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-alarm-still-set fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style reseat-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-and-droid-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style follow-droid-to-aircraft-electrical-contacts-debugging fill:#dcfce7,stroke:#22c55e,color:#14532d
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87 Hover or focus a block to preview it. Select the block to keep the preview open.
- The alarm has a 60 second hysteresis on it, so the Aircraft must be in Intermission for 60 seconds before the alarm will be set again after the power cycle.
- The task name can be viewed on FleetWrangler with the View Zip Exec Task Info button.
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.