0x130010 CONTROLLER_CODE_INVALID_ROTOR_FAULT_CONFIG
Applicable alarms (3)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for CONTROLLER_CODE_INVALID_ROTOR_FAULT_CONFIG) 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 CONTROLLER_CODE_INVALID_ROTOR_FAULT_CONFIG error code is a serious error that can cause an aircraft to failover and/or paraland. It is not a controller issue, but is indicative of some other problems in the system. Follow the steps below to resolve.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
open-the-error-flow-graph["<small><b>Step 1</b></small><br/>Action: On the failed mission P2M page in Bar..."]
check-for-mission-step-not-serviceable{"<small><b>Step 2</b></small><br/>Question: In the error graph, check whether the..."}
check-previous-incident-and-clear-latched-error["<small><b>Step 3</b></small><br/>Action: Do not treat the controller error as ..."]
identify-the-root-cause["<small><b>Step 4</b></small><br/>Action: In the error graph, follow the caused..."]
can-you-follow-a-root-cause-guide{"<small><b>Step 5</b></small><br/>Question: Can you identify the last alarm/error..."}
follow-the-root-cause-guide["<small><b>Step 6</b></small><br/>Action: Follow the troubleshooting guide for ..."]
escalate-to-p2-zip-controls{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Zip Controls On Call f..."}}
open-the-error-flow-graph --> check-for-mission-step-not-serviceable
check-for-mission-step-not-serviceable -->|Yes| check-previous-incident-and-clear-latched-error
check-for-mission-step-not-serviceable -->|No| identify-the-root-cause
identify-the-root-cause --> can-you-follow-a-root-cause-guide
can-you-follow-a-root-cause-guide -->|Yes| follow-the-root-cause-guide
can-you-follow-a-root-cause-guide -->|No| escalate-to-p2-zip-controls
style open-the-error-flow-graph fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-for-mission-step-not-serviceable fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-previous-incident-and-clear-latched-error fill:#dcfce7,stroke:#22c55e,color:#14532d
style identify-the-root-cause fill:#dcfce7,stroke:#22c55e,color:#14532d
style can-you-follow-a-root-cause-guide fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-root-cause-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-zip-controls fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Example graph icon on a P2M page:
ZIP_EXECUTIVE_V4_MISSION_STEP_NOT_SERVICEABLE executive error is above the controller error.If this error is present, the controller error is not the root cause for this flight. It indicates a failure from the previous flight was latched and not cleared correctly.
Example of
ZIP_EXECUTIVE_V4_MISSION_STEP_NOT_SERVICEABLE above a controller error:
Is
ZIP_EXECUTIVE_V4_MISSION_STEP_NOT_SERVICEABLE present above the controller error?Use ZERP to check the previous incident for this Aircraft and verify that it was resolved correctly.
If the previous incident is still unresolved, resolve that incident first. If the previous incident was resolved correctly, clear the latched error with these steps:
1. Restart Zip Executive.
2. If the latched error does not clear after restarting Zip Executive, Power Cycle Aircraft.
Example error graph with the last box highlighted as the root cause:
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.