0x000a0014 CAPABILITY_DIAGNOSTIC_NAV_UNHEALTHY
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x000a0014) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when the Droid is unable to maintain a healthy navigation solution. The Droid has two completely separate navigation systems: one which runs during delivery, drone loading, and Zipping Point pickups, and another which runs exclusively during legacy portal lowers/raises.
In delivery/pickup missions
Section titled “In delivery/pickup missions”The failure of navigation software during a delivery pickup mission typically results in a DLB. If this alarm fired but there was not a DLB, then it’s likely that it was only a transient issue. In this phase of flight, this alarm doesn’t generally imply anything specific about the airworthiness of the droid. If there is an underlying hardware issue, other alarms will fire which identify the defective component.
In legacy portal missions
Section titled “In legacy portal missions”The most common cause of this error is that droids with unglued lenses (-001 droid brains) become decalibrated due to shock events. These events can occur in the portal, e.g. during the preceding lower mission, which can cause the droid to struggle on the subsequent raise mission due to poorly-calibrated cameras.
Typically the system will auto-retry raise missions up to 3 times. In most cases, even when the calibration is damaged, the droid is able to raise successfully on the second or third try. Once the droid is raised, the correct action is to continue flying the delivery mission, even if the calibration is somewhat damaged: the droid will automatically self-calibrate during the delivery flight.
The worst action we can take if a droid has marginal calibration is to lower the droid back into the kiosk. That creates a condition where the droid has a high probability of not being able to perform an autonomy raise again, leading to increased asset downtime (likely a maintenance raise followed by maintenance check flight).
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-the-alarm-occur-during-a-dlb{"<small><b>Step 1</b></small><br/>Question: Did the alarm occur during a Droid Le..."}
complete-the-dlb-work-orders["<small><b>Step 2</b></small><br/>Action: Complete the work orders listed below..."]
which-mission-type-are-you-troublesh{"<small><b>Step 3</b></small><br/>Question: Are you troubleshooting a delivery/au..."}
delivery-autokiosk-mission("<small><b>Step 4</b></small><br/>Reference: **Delivery/autokiosk Mission** May be...")
power-cycle-the-droid-power-cycle-droi["<small><b>Step 5</b></small><br/>Action: Power cycle the Droid Power Cycle D..."]
return-the-aircraft-to-service("<small><b>Step 6</b></small><br/>Reference: Return the Aircraft to service.")
if-the-failure-repeats-escalate-to-p2{{"<small><b>Step 7</b></small><br/>Escalation: If the failure repeats, escalate to P..."}}
portal-mission("<small><b>Step 8</b></small><br/>Reference: **Portal Mission** The Droid may have...")
calibrate-the-droid["<small><b>Step 9</b></small><br/>Action: Calibrate the Droid. See the Droid CM..."]
did-the-alarm-occur-during-a-dlb -->|Yes| complete-the-dlb-work-orders
did-the-alarm-occur-during-a-dlb -->|No| which-mission-type-are-you-troublesh
which-mission-type-are-you-troublesh -->|Delivery/autokiosk mission| delivery-autokiosk-mission
which-mission-type-are-you-troublesh -->|Portal mission| portal-mission
delivery-autokiosk-mission --> power-cycle-the-droid-power-cycle-droi
power-cycle-the-droid-power-cycle-droi --> return-the-aircraft-to-service
return-the-aircraft-to-service --> if-the-failure-repeats-escalate-to-p2
portal-mission --> calibrate-the-droid
style did-the-alarm-occur-during-a-dlb fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style complete-the-dlb-work-orders fill:#dcfce7,stroke:#22c55e,color:#14532d
style which-mission-type-are-you-troublesh fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style delivery-autokiosk-mission fill:#f3e8ff,stroke:#a855f7,color:#581c87
style power-cycle-the-droid-power-cycle-droi fill:#dcfce7,stroke:#22c55e,color:#14532d
style return-the-aircraft-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style if-the-failure-repeats-escalate-to-p2 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style portal-mission fill:#f3e8ff,stroke:#a855f7,color:#581c87
style calibrate-the-droid fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
- Aircraft: Complete the work order for the relevant aircraft version:
- EV2: #195: Inspect Aircraft after Droid Left Behind (DLB)
- EV3: #662: Inspect Aircraft after Droid Left Behind (DLB)
- Droid: Complete the following work orders in order:
1. #1169: Reset Droid after DLB
2. #1196: Offload Droid Logs after DLB
3. #1302: Perform Droid GNSS Status Test after DLB
May be temporary and is not critical.
The Droid may have been damaged by a recent shock event. Typically the system will automatically retry 3 times before creating a discrepancy.
WORK ORDER TEMPLATE: Use Work Order Template #794: "Maintenance Check Flight (MFC)"
If the failure persists after an attempt to recalibrate, escalate to P2 Nav On Call.
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.