Aircraft Stuck During Undocking After OPEN Command Received
This alarm is covered by this guide. Background
Section titled “Background”If an aircraft detects it is stuck on undocking after the open command has been received by the dock, this usually points to some physical issue with the fin<->latch interface. Historically, we’ve seen issues with:
- Latch faulting on opening
- Delayed latch opening
- Broken Dock lead-in funnel
- Misaligned-aligned zip fin sockets
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
please-ensure-that-both-the-dock-and-zi["<small><b>Step 1</b></small><br/>Action: Ground both the dock and zip while wo..."]
at-this-point-it-is-forbidden-to-reposi["<small><b>Step 2</b></small><br/>Action: **At this point, it is forbidden to r..."]
is-the-latch-service-state-faulted{"<small><b>Step 3</b></small><br/>Question: In FleetWrangler, open the Dock's **D..."}
escalate-faulted-latch-to-p2-dock-hardware{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Dock Hardware On Call ..."}}
issue-aircraft-socket-and-dock-latch-inspection-work-orders["<small><b>Step 5</b></small><br/>Action: Issue the Aircraft Socket Inspection..."]
please-ensure-that-both-the-dock-and-zi --> at-this-point-it-is-forbidden-to-reposi
at-this-point-it-is-forbidden-to-reposi --> is-the-latch-service-state-faulted
is-the-latch-service-state-faulted -->|Yes| escalate-faulted-latch-to-p2-dock-hardware
is-the-latch-service-state-faulted -->|No| issue-aircraft-socket-and-dock-latch-inspection-work-orders
style please-ensure-that-both-the-dock-and-zi fill:#dcfce7,stroke:#22c55e,color:#14532d
style at-this-point-it-is-forbidden-to-reposi fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-latch-service-state-faulted fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-faulted-latch-to-p2-dock-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f
style issue-aircraft-socket-and-dock-latch-inspection-work-orders fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
LATCH_SERVICE_STATE_FAULTED?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.