0x60004 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_TIMEOUT
Applicable alarms (6)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x60004) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The aircraft motion planner has a fixed allotment of time (3 minutes) in preflight to get all the artifacts needed to fly a mission, which involves (in order) downloading maps, fetching routes from the cloud, and then performing an energy estimate. Each of these have their own timeouts and error codes. This error indicates that none of these checks hit their individual timeouts, but the whole process did, which likely means that both maps and routes were slower than expected (though not slow enough to hit their timeouts).
Since maps can be cached between missions, we expect that a second attempt to be faster than the first. However if a second attempt also fails, no additional attempts should be made, as anything after the second attempt is expected to hit the same failure.
Troubleshooting Step
Section titled “Troubleshooting Step”graph TD
resend-the-mission-is-the-issue-resolve{"<small><b>Step 1</b></small><br/>Question: Resend the mission. Is the issue reso..."}
the-aircraft-may-return-to-service("<small><b>Step 2</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-aircraft-autonomy-on{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to P2 Aircraft Autonomy On C..."}}
the-aircraft-is-clear-to-fly-to-other["<small><b>Step 4</b></small><br/>Action: The Aircraft is clear to fly to other..."]
resend-the-mission-is-the-issue-resolve -->|Yes| the-aircraft-may-return-to-service
resend-the-mission-is-the-issue-resolve -->|No| escalate-to-p2-aircraft-autonomy-on
escalate-to-p2-aircraft-autonomy-on --> the-aircraft-is-clear-to-fly-to-other
style resend-the-mission-is-the-issue-resolve fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-aircraft-autonomy-on fill:#fef3c7,stroke:#f59e0b,color:#78350f
style the-aircraft-is-clear-to-fly-to-other fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
This is expected to be an issue with cloud speed, but it will need triage before confirming and shifting responsibility to that team.
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.