DROID_BRAIN_UNHEALTHY
Applicable alarms (1)
Likely outcomes — click to expand
Based on 798 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 160 ZERP issues filed on these missions)
Top work orders
- Droid Asset ID Recovery · REPAIR 10
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| ASSM, FLIGHT COMPUTER, AFT, ZIP, P2 | 48409 | 9 |
| AFT MOTOR ASSY, ZIP, P2 | 23548 | 7 |
| MIXED PROPELLER BLADE, ZIP, P2 | 26014 | 4 |
| ASSM, FLIGHT COMPUTER, FORE, ZIP, P2 | 48408 | 4 |
| BRAIN, LRU, DROID, P2 | 31920 | 4 |
Frequently co-occurring alarms (% of the 798 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 there are issues with the Droid Executive. That is, the Droid executive watchdog is alerting and there are no wired comms between the Aircraft and Droid. In this state, any missions involving the Droid (delivery, lower, raise, etc.) are likely to fail; therefore, the recommended maintenance action should be taken.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-droid-power-cycle-droi["<small><b>Step 1</b></small><br/>Action: Power cycle the Droid Power Cycle Dr..."]
wait-for-a-minimum-of-60-seconds["<small><b>Step 2</b></small><br/>Action: Wait for a minimum of 60 seconds."]
is-the-alarm-still-set{"<small><b>Step 3</b></small><br/>Question: Is the alarm still set?"}
escalate-to-p2-droid-autonomy-on-call{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Droid Autonomy On Call."}}
the-aircraft-may-return-to-service("<small><b>Step 5</b></small><br/>Reference: The Aircraft may return to service.")
power-cycle-the-droid-power-cycle-droi --> wait-for-a-minimum-of-60-seconds
wait-for-a-minimum-of-60-seconds --> is-the-alarm-still-set
is-the-alarm-still-set -->|Yes| escalate-to-p2-droid-autonomy-on-call
is-the-alarm-still-set -->|No| the-aircraft-may-return-to-service
style power-cycle-the-droid-power-cycle-droi fill:#dcfce7,stroke:#22c55e,color:#14532d
style wait-for-a-minimum-of-60-seconds fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-alarm-still-set fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-droid-autonomy-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
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.
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.