NO_DOCK_STATUS
Applicable alarms (1)
Likely outcomes — click to expand
Based on 851,061 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 7,300 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 634
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 430
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 338
- Reset Droid after DLB · REPAIR 294
- 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,879 |
| CW/CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 1,548 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 1,232 |
| TAIL ASSY STBD(RH), PRE-EV2, ZIP, P2 | 21840 | 907 |
| CW HOVER MOTOR ASSY, ZIP, P2 | 33333 | 904 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”Prior to takeoff, the navigation system performs checks to ensure that the Aircraft\u2019s position and orientation are consistent with the provided mission and Dock survey. This prevents paralands due to an incorrect mission arriving at an Aircraft, or if a Dock has moved significantly while the Aircraft was docked, and so on. These checks are only valid when the Aircraft is fully latched and retracted on the Dock, and so the navigation system must monitor the Dock status.
This is a launch-blocking alarm. It is set when the navigation system has not received any updated information about the Dock within the last 5 seconds. This is expected while in flight. This alarm only indicates a problem if the Aircraft has not yet taken off.
This alarm will not cause any response if it occurs in flight. It should clear upon successful docking.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-aircraft-in-a-dock{"<small><b>Step 1</b></small><br/>Question: Is the Aircraft in a Dock?"}
reboot-the-dock-for-steps-see-reboot-do["<small><b>Step 2</b></small><br/>Action: Reboot the Dock. For steps, see Rebo..."]
did-the-issue-resolve{"<small><b>Step 3</b></small><br/>Question: Did the issue resolve?"}
the-aircraft-may-return-to-service("<small><b>Step 4</b></small><br/>Reference: The Aircraft may return to service.")
power-cycle-the-aircraft-for-steps-see["<small><b>Step 5</b></small><br/>Action: Power cycle the Aircraft. For steps, ..."]
did-the-issue-resolve-after-power-cycle{"<small><b>Step 6</b></small><br/>Question: Did the issue resolve?"}
the-aircraft-may-return-to-service-2("<small><b>Step 7</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-dock-on-call{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to P2 dock on call."}}
this-alarm-is-expected-it-will-clear-aft["<small><b>Step 9</b></small><br/>Action: This alarm is expected. It will clear..."]
is-the-aircraft-in-a-dock -->|Yes| reboot-the-dock-for-steps-see-reboot-do
is-the-aircraft-in-a-dock -->|No| this-alarm-is-expected-it-will-clear-aft
reboot-the-dock-for-steps-see-reboot-do --> did-the-issue-resolve
did-the-issue-resolve -->|Yes| the-aircraft-may-return-to-service
did-the-issue-resolve -->|No| power-cycle-the-aircraft-for-steps-see
power-cycle-the-aircraft-for-steps-see --> did-the-issue-resolve-after-power-cycle
did-the-issue-resolve-after-power-cycle -->|Yes| the-aircraft-may-return-to-service-2
did-the-issue-resolve-after-power-cycle -->|No| escalate-to-p2-dock-on-call
style is-the-aircraft-in-a-dock fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style reboot-the-dock-for-steps-see-reboot-do fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-issue-resolve fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style power-cycle-the-aircraft-for-steps-see fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-issue-resolve-after-power-cycle fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service-2 fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-dock-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style this-alarm-is-expected-it-will-clear-aft fill:#dcfce7,stroke:#22c55e,color:#14532d 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.