0x60005 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_COMMAND_ERROR
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x60005) 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 was unable to complete a motion command.
Currently this error is only set if the controller fails to undock.
Troubleshooting Step
Section titled “Troubleshooting Step”graph TD
follow-the-troubleshooting-guide-for-t("<small><b>Step 1</b></small><br/>Reference: Follow the troubleshooting guide for ...")
if-there-are-no-linked-errors-escalate{{"<small><b>Step 2</b></small><br/>Escalation: If there are no linked errors, escala..."}}
follow-the-troubleshooting-guide-for-t --> if-there-are-no-linked-errors-escalate
style follow-the-troubleshooting-guide-for-t fill:#f3e8ff,stroke:#a855f7,color:#581c87
style if-there-are-no-linked-errors-escalate 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
There are no open suggestions.
Open pull requests
There are no open pull requests.