0x50002 COMMANDER_CODE_UNDOCKING_CANCELLED_BY_EXECUTIVE
Viewing this guide for
Applicable alarms (2)
0x50002COMMANDER_CODE_UNDOCKING_CANCELLED_BY_EXECUTIVE
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x50002) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This error can occur during the start of undocking. The Aircraft Executive is telling the GNC Zip commander to cancel the undocking behavior.
The Aircraft Executive can tell the GNC Zip commander to cancel undocking if:
- It has sent a LATCH_OPEN command to the Dock
- It does not receive a command acknowledgement from the Dock.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
check-the-bays-latch-service-state-on-f{"<small><b>Step 1</b></small><br/>Question: Check the bay’s latch service state o..."}
this-means-that-the-dock-never-tried-to{"<small><b>Step 2</b></small><br/>Question: This means that the Dock never tried ..."}
send-the-flight-again-is-the-issue-reso{"<small><b>Step 3</b></small><br/>Question: Send the flight again. Is the issue r..."}
the-aircraft-and-dock-may-return-to-serv-yes["<small><b>Step 4</b></small><br/>Action: The Aircraft and Dock may return to s..."]
manually-remove-the-aircraft-from-the-d-no["<small><b>Step 5</b></small><br/>Action: Complete the following actions: 1. Ma..."]
manually-remove-the-aircraft-from-the-d-pair["<small><b>Step 6</b></small><br/>Action: 1. Manually remove the Aircraft from ..."]
manually-remove-the-aircraft-from-the-d-dock["<small><b>Step 7</b></small><br/>Action: 1. Manually remove the Aircraft from ..."]
manually-remove-the-aircraft-from-the-d-ac["<small><b>Step 8</b></small><br/>Action: 1. Manually remove the Aircraft from ..."]
this-means-that-something-went-wrong-wi["<small><b>Step 9</b></small><br/>Action: This means that something went wrong ..."]
the-dock-thought-that-it-opened-but-the["<small><b>Step 10</b></small><br/>Action: The Dock thought that it opened but t..."]
if-none-of-the-above-apply-escalate-to{{"<small><b>Step 11</b></small><br/>Escalation: If none of the above apply, escalate ..."}}
check-the-bays-latch-service-state-on-f -->|Latch service state is RETR...| this-means-that-the-dock-never-tried-to
check-the-bays-latch-service-state-on-f -->|Latch service state is FAULTED| this-means-that-something-went-wrong-wi
check-the-bays-latch-service-state-on-f -->|Latch service state is OPEN...| the-dock-thought-that-it-opened-but-the
check-the-bays-latch-service-state-on-f -->|None of the above apply| if-none-of-the-above-apply-escalate-to
this-means-that-the-dock-never-tried-to -->|Yes - This is the first tim...| send-the-flight-again-is-the-issue-reso
this-means-that-the-dock-never-tried-to -->|No - This pair is a repeat ...| manually-remove-the-aircraft-from-the-d-pair
this-means-that-the-dock-never-tried-to -->|No - Only the Dock is a rep...| manually-remove-the-aircraft-from-the-d-dock
this-means-that-the-dock-never-tried-to -->|No - Only the Aircraft is a...| manually-remove-the-aircraft-from-the-d-ac
send-the-flight-again-is-the-issue-reso -->|YES| the-aircraft-and-dock-may-return-to-serv-yes
send-the-flight-again-is-the-issue-reso -->|NO| manually-remove-the-aircraft-from-the-d-no
style check-the-bays-latch-service-state-on-f fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style this-means-that-the-dock-never-tried-to fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style send-the-flight-again-is-the-issue-reso fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-and-dock-may-return-to-serv-yes fill:#dcfce7,stroke:#22c55e,color:#14532d
style manually-remove-the-aircraft-from-the-d-no fill:#dcfce7,stroke:#22c55e,color:#14532d
style manually-remove-the-aircraft-from-the-d-pair fill:#dcfce7,stroke:#22c55e,color:#14532d
style manually-remove-the-aircraft-from-the-d-dock fill:#dcfce7,stroke:#22c55e,color:#14532d
style manually-remove-the-aircraft-from-the-d-ac fill:#dcfce7,stroke:#22c55e,color:#14532d
style this-means-that-something-went-wrong-wi fill:#dcfce7,stroke:#22c55e,color:#14532d
style the-dock-thought-that-it-opened-but-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style if-none-of-the-above-apply-escalate-to fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Check the bay’s latch service state on Fleet Wrangler and take the appropriate action below depending on what it says:
2 question
This means that the Dock never tried to open the latch. There is likely a comms issue with the Dock or the Aircraft.
Is this the first time this has happened on this Aircraft and/or this Dock?
Is this the first time this has happened on this Aircraft and/or this Dock?
3 question
Send the flight again. Is the issue resolved?
4 action
The Aircraft and Dock may return to service.
5 action
Complete the following actions:
1. Manually remove the Aircraft from the dock using Actuate Latch Commands.
2. Move the Aircraft to another Dock.
3. The Aircraft and Dock may return to service.
1. Manually remove the Aircraft from the dock using Actuate Latch Commands.
2. Move the Aircraft to another Dock.
3. The Aircraft and Dock may return to service.
6 action
1. Manually remove the Aircraft from the Dock using Actuate Latch Commands.
2. Move the Aircraft to another Dock.
3. The Aircraft and Dock may return to service.
2. Move the Aircraft to another Dock.
3. The Aircraft and Dock may return to service.
7 action
1. Manually remove the Aircraft from the Dock using Actuate Latch Commands.
2. Move the Aircraft to another Dock.
3. The Aircraft may return to service.
4. Make discrepancy against the Dock.
5. Follow the steps in Dock Not Communicating with Aircraft to determine what component is broken in the Dock to cause intermittent comms. Since this is an intermittent issue, you may need to wiggle connections to reproduce the failure.
6. Escalate to P2 Dock Hardware On Call if there is no resolution.
2. Move the Aircraft to another Dock.
3. The Aircraft may return to service.
4. Make discrepancy against the Dock.
5. Follow the steps in Dock Not Communicating with Aircraft to determine what component is broken in the Dock to cause intermittent comms. Since this is an intermittent issue, you may need to wiggle connections to reproduce the failure.
6. Escalate to P2 Dock Hardware On Call if there is no resolution.
8 action
1. Manually remove the Aircraft from the Dock using Actuate Latch Commands.
2. Continue flying on Dock.
3. Make a discrepancy against the Aircraft.
4. Follow the steps in Dock Not Communicating with Aircraft to determine what component is broken in the Aircraft to cause intermittent comms. Since this is an intermittent issue, you may need to wiggle connections to reproduce the failure.
5. Escalate to P2 Zip Hardware On Call if there is no resolution.
2. Continue flying on Dock.
3. Make a discrepancy against the Aircraft.
4. Follow the steps in Dock Not Communicating with Aircraft to determine what component is broken in the Aircraft to cause intermittent comms. Since this is an intermittent issue, you may need to wiggle connections to reproduce the failure.
5. Escalate to P2 Zip Hardware On Call if there is no resolution.
9 action
This means that something went wrong with the latch between the start of preflight and takeoff.
1. Remove the Aircraft from the Dock using the RESET command, for steps see Actuate Latch Commands.
2. Ground the Dock.
3. Escalate to P2 Dock Embedded On Call.
1. Remove the Aircraft from the Dock using the RESET command, for steps see Actuate Latch Commands.
2. Ground the Dock.
3. Escalate to P2 Dock Embedded On Call.
10 action
The Dock thought that it opened but the Aircraft did not exit.
1. Remove the Aircraft from the Dock using Actuate Latch Commands.
2. Ground the Dock.
3. Escalate to P2 Dock Embedded On Call.
1. Remove the Aircraft from the Dock using Actuate Latch Commands.
2. Ground the Dock.
3. Escalate to P2 Dock Embedded On Call.
11 escalation
If none of the above apply, escalate to Executive On-Call for support.
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.