Autonomy Watchdog Alarms
Applicable alarms (4)
Likely outcomes — click to expand
Based on 888,256 missions where this alarm fired in the last
90 days
(for PROXIMITY_CHECK_RESULT_UNAVAILABLE) as of 2026-10-13
Grounding vs discrepancy (of 5,798 ZERP issues filed on these missions)
Top work orders
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 215
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 77
- EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 71
- Reset Droid Lid · TROUBLESHOOTING 57
- EV2: ZCO-2026-08-03 Lower Foam Wear Pad Retrofit (FRCO-286 / SB-2026-023) · UPGRADE_RETROFIT 35
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 972 |
| CCW HOVER MOTOR ASSY, EV3 ZIP, P2 | 19607 | 822 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 782 |
| PRE-PREG TAIL ASSY STBD(RH), ZIP, P2 | 21840 | 684 |
| PRE-PREG TAIL ASSY PORT(LH), ZIP, P2 | 31280 | 651 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This guide covers Exec watchdog alarms owned by P2 Autonomy On Call.
These alarms generally indicate stale or unavailable planning, motion, V2V, or autonomy outputs.
Included Exec watchdog alarms
Section titled “Included Exec watchdog alarms”- PROXIMITY_CHECK_RESULT_UNAVAILABLE
- V2V_METRICS_UNAVAILABLE
- ZIP_MOTION_RESPONSES_UNAVAILABLE
- DELIVERY_ASSIST_TRIGGER_RESPONSE_UNAVAILABLE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-aircraft["<small><b>Step 1</b></small><br/>Action: Power cycle the aircraft. Reference: ..."]
check-autonomy-outputs["<small><b>Step 2</b></small><br/>Action: Check for stale or missing V2V and au..."]
confirm-alarm-clears{"<small><b>Step 3</b></small><br/>Question: Did the watchdog alarm clear?"}
return-to-service("<small><b>Step 4</b></small><br/>Reference: The aircraft may return to service.")
escalate-to-p2-autonomy{{"<small><b>Step 5</b></small><br/>Escalation: Escalate to P2 Autonomy On Call."}}
power-cycle-aircraft --> check-autonomy-outputs
check-autonomy-outputs --> confirm-alarm-clears
confirm-alarm-clears -->|Yes, the alarm cleared| return-to-service
confirm-alarm-clears -->|No, the alarm persists or r...| escalate-to-p2-autonomy
style power-cycle-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-autonomy-outputs fill:#dcfce7,stroke:#22c55e,color:#14532d
style confirm-alarm-clears fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-autonomy 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
Open pull requests
There are no open pull requests.