Preflight Routing Error Codes
This alarm is covered by this guide. Applicable alarms (30)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x60002) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
These troubleshooting steps apply to the following preflight routing error codes:
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
- 0x60006 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_INVALID
- 0x60007 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTING_RESPONSE_INVALID
- 0x60008 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_MANAGER_INTERNAL_PROGRAMMING_ERROR
- 0x60009 ZIP_ONBOARD_PLANNING_ERROR_CODES_PPS_RESPONSE_ERROR
- 0x60010 ZIP_ONBOARD_PLANNING_ERROR_CODES_FAILING_MIDFLIGHT_MOTION_CHECK
- 0x60011 ZIP_ONBOARD_PLANNING_ERROR_CODES_NO_ROUTE_STATE
- 0x60012 ZIP_ONBOARD_PLANNING_ERROR_CODES_EMPTY_CONTINGENCY_ROUTES
- 0x60013 ZIP_ONBOARD_PLANNING_ERROR_CODES_NO_VIABLE_CONTINGENCY_ROUTE
- 0x60014 ZIP_ONBOARD_PLANNING_ERROR_CODES_CANNOT_COMPUTE_TRANSIT_LEGS
- 0x6000B ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_MANAGER_INTERRUPTED
- 0x6000C ZIP_ONBOARD_PLANNING_ERROR_CODES_PPS_RESPONSE_REJECTED
- 0x6000D ZIP_ONBOARD_PLANNING_ERROR_CODES_GLOBAL_PLANNER_RESPONSE_REJECTED
- 0x6000E ZIP_ONBOARD_PLANNING_ERROR_CODES_TIMEOUT_ON_PPS_ROUTE
- 0x6000F ZIP_ONBOARD_PLANNING_ERROR_CODES_TIMEOUT_ON_GLOBAL_PLANNER_ROUTE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
wait-one-1-minute-and-then-try-to-send{"<small><b>Step 1</b></small><br/>Question: Wait one 1 minute and then try to s..."}
the-aircraft-may-return-to-service("<small><b>Step 2</b></small><br/>Reference: The Aircraft may return to service.")
match-the-errors-that-you-see-in-the-er{"<small><b>Step 3</b></small><br/>Question: Match the errors that you see in the ..."}
scenario-1-escalate-to-p2-routing-on-ca{{"<small><b>Step 4</b></small><br/>Escalation: The error report includes: - **0x6000..."}}
scenario-2-check-for-weather-conditions["<small><b>Step 5</b></small><br/>Action: The error report includes: - **0x6000..."]
scenario-3-escalate-to-p2-aircraft-auton{{"<small><b>Step 6</b></small><br/>Escalation: The error report includes: - **0x6000..."}}
scenario-4-escalate-to-p2-aircraft-auton{{"<small><b>Step 7</b></small><br/>Escalation: The error report includes: - **0x6001..."}}
scenario-5-these-error-codes-should-neve["<small><b>Step 8</b></small><br/>Action: The error report includes **ANY of th..."]
scenario-6-confirm-the-following-error-c["<small><b>Step 9</b></small><br/>Action: The other scenarios do not apply **AN..."]
scenario-7-confirm-the-following-error-c["<small><b>Step 10</b></small><br/>Action: The other scenarios do not apply **AN..."]
wait-one-1-minute-and-then-try-to-send -->|Yes| the-aircraft-may-return-to-service
wait-one-1-minute-and-then-try-to-send -->|No| match-the-errors-that-you-see-in-the-er
match-the-errors-that-you-see-in-the-er -->|**0x6000C** and **0x60002**...| scenario-1-escalate-to-p2-routing-on-ca
match-the-errors-that-you-see-in-the-er -->|**0x6000E** and **0x60002**| scenario-2-check-for-weather-conditions
match-the-errors-that-you-see-in-the-er -->|**0x60008** and **0x60002**...| scenario-3-escalate-to-p2-aircraft-auton
match-the-errors-that-you-see-in-the-er -->|**0x60014** and **0x60002**| scenario-4-escalate-to-p2-aircraft-auton
match-the-errors-that-you-see-in-the-er -->|ANY of **0x6000B**, **0x600...| scenario-5-these-error-codes-should-neve
match-the-errors-that-you-see-in-the-er -->|Other scenarios do not appl...| scenario-6-confirm-the-following-error-c
match-the-errors-that-you-see-in-the-er -->|Other scenarios do not appl...| scenario-7-confirm-the-following-error-c
style wait-one-1-minute-and-then-try-to-send fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style match-the-errors-that-you-see-in-the-er fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style scenario-1-escalate-to-p2-routing-on-ca fill:#fef3c7,stroke:#f59e0b,color:#78350f
style scenario-2-check-for-weather-conditions fill:#dcfce7,stroke:#22c55e,color:#14532d
style scenario-3-escalate-to-p2-aircraft-auton fill:#fef3c7,stroke:#f59e0b,color:#78350f
style scenario-4-escalate-to-p2-aircraft-auton fill:#fef3c7,stroke:#f59e0b,color:#78350f
style scenario-5-these-error-codes-should-neve fill:#dcfce7,stroke:#22c55e,color:#14532d
style scenario-6-confirm-the-following-error-c fill:#dcfce7,stroke:#22c55e,color:#14532d
style scenario-7-confirm-the-following-error-c fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
- 0x6000C ZIP_ONBOARD_PLANNING_ERROR_CODES_PPS_RESPONSE_REJECTED
AND
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
NOTE: Other error codes may be present.
Escalate to P2 Routing On Call and include the entire error report chain as context.
- 0x6000E ZIP_ONBOARD_PLANNING_ERROR_CODES_TIMEOUT_ON_PPS_ROUTE
AND
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
Check for weather conditions or Zipline flight restrictions that could impact ability to route between requested locations for mission.
If weather or Zipline flight restrictions, wait until conditions / restrictions pass / are lifted and try again.
If neither, escalate to P2 Routing On Call and include the entire error report chain as context.
If access to full error message and contains:
-
Bad waypoint: Invalid waypoint for either Violating ZFR or Violates WeatherKeepout then the mission is failing for valid reasons.- 0x60008 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_MANAGER_INTERNAL_PROGRAMMING_ERROR
AND
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
NOTE: Other error codes may be present.
Escalate to P2 Aircraft Autonomy On Call and include the entire error report chain as context.
- 0x60014 ZIP_ONBOARD_PLANNING_ERROR_CODES_CANNOT_COMPUTE_TRANSIT_LEGS
AND
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
Escalate to P2 Aircraft Autonomy On Call.
- 0x6000B ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_MANAGER_INTERRUPTED
- 0x6000D ZIP_ONBOARD_PLANNING_ERROR_CODES_GLOBAL_PLANNER_RESPONSE_REJECTED
- 0x6000F ZIP_ONBOARD_PLANNING_ERROR_CODES_TIMEOUT_ON_GLOBAL_PLANNER_ROUTE
- 0x60010 ZIP_ONBOARD_PLANNING_ERROR_CODES_FAILING_MIDFLIGHT_MOTION_CHECK
- 0x60011 ZIP_ONBOARD_PLANNING_ERROR_CODES_NO_ROUTE_STATE
- 0x60012 ZIP_ONBOARD_PLANNING_ERROR_CODES_EMPTY_CONTINGENCY_ROUTES
- 0x60013 ZIP_ONBOARD_PLANNING_ERROR_CODES_NO_VIABLE_CONTINGENCY_ROUTE
1. These error codes should never cause preflight failures.
2. Troubleshoot every other error code in the error report
3. If these are the ONLY errors, escalate to P2 Aircraft Autonomy On Call.
- 0x60006 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTE_INVALID
- 0x60007 ZIP_ONBOARD_PLANNING_ERROR_CODES_ROUTING_RESPONSE_INVALID
- 0x60009 ZIP_ONBOARD_PLANNING_ERROR_CODES_PPS_RESPONSE_ERROR
1. Confirm the following error codes are NOT present in the error report:
1. 0x60008
2. 0x6000C
3. 0x6000E
4. 0x60014
2. Troubleshoot all other error codes in the error report
3. If unresolved and these are the only errors, escalate to P2 Aircraft Autonomy On Call
- 0x60002 ZIP_ONBOARD_PLANNING_ERROR_CODES_MOTION_CHECK_ROUTE_MANAGER_REJECTED
1. Confirm the following error codes are NOT present in the error report:
1. 0x60008
2. 0x6000C
3. 0x6000E
4. 0x60014
2. Troubleshoot all other error codes in the error report
3. If unresolved and these are the only errors, escalate to P2 Aircraft Autonomy 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.