Skip to content

NO_DOCK_INFORMATION

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
NO_DOCK_INFORMATION
Likely outcomes (1,286,999 missions, 9,695 issues) — click to expand

Based on 1,286,999 missions where this alarm fired in the last 90 days as of 2026-10-13

Grounding vs discrepancy (of 9,695 ZERP issues filed on these missions)

Grounding 41.1% (3,987 of 9,695 issues) Discrepancy 58.9% (5,708 of 9,695 issues)

Top work orders

  • EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 623
  • Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 427
  • EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 337
  • Reset Droid after DLB · REPAIR 283
  • V4 Zipping Point: Inspect Zipping Point after Droid Left Behind (DLB) - Ranger · MAINTENANCE_ACTION 155

Frequently replaced parts

Part P/N Removals
SERVO, ASSY, UNIVERSAL, P2 20398 2,183
CCW HOVER MOTOR ASSY, ZIP, P2 19607 1,727
TAIL ASSY STBD(RH), PRE-EV2, ZIP, P2 21840 1,390
PRE-PREG TAIL ASSY, AL, PORT(LH), ZIP, P2 31280 1,322
ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 48477 1,227

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

This alarm is set when the navigation system doesn’t know about any docks. It blocks takeoff, because without information about which dock we are taking off from, navigation cannot perform its preflight checks.

The navigation system is informed about the docks involved in a mission when the mission is first received from the cloud. This alarm is expected to clear upon the reception of the first mission.

1 escalation
Escalate to P2 Routing On Call.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.