RTK_POSITION_UNAVAILABLE
Applicable alarms (1)
Likely outcomes — click to expand
Based on 795,235 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 6,592 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 537
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 340
- EV2/EV3 Diagnostics Test Without Motors · INSPECTION 294
- Reset Droid after DLB · REPAIR 265
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 251
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 1,588 |
| HOVER MOTOR ASSY, CCW MOTOR, ZIP, P2 | 19607 | 1,359 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 926 |
| TAIL ASSY STBD(RH), PRE-EV2, ZIP, P2 | 21840 | 907 |
| TAIL PORT DEPOP, ZIP, P2 | 31280 | 863 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The aircraft uses a precision GNSS navigation system known as RTK in order to achieve centimeter-level accuracy during flight. If this level of accuracy is unable to be acquired prior to takeoff, we prevent flight.
RTK requires four components to operate:
- One or more nearby base stations must provide information to the cloud,
- The aircraft must be able to receive that information from the cloud,
- The solution engine must be able to resolve that information into an accurate position,
- The navigation system must agree with the position provided by the solution engine.
Each of these components is verified by this alarm.
This is a launch-blocking alarm. There is no in-flight response to this signal. If this condition occurs in flight, the vehicle will continue to navigate while slowly accumulating drift. It will automatically attempt to re-acquire RTK.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
wait-10-minutes-to-see-if-the-error-cle["<small><b>Step 1</b></small><br/>Action: Wait 10 minutes to see if the error c..."]
send-the-aircraft-another-mission["<small><b>Step 2</b></small><br/>Action: If the alarm persists, send the Aircr..."]
is-the-issue-resolved-after-mission{"<small><b>Step 3</b></small><br/>Question: Is the issue resolved after the missi..."}
if-the-alarm-persists-follow-the-proced["<small><b>Step 4</b></small><br/>Action: If the alarm persists after the missi..."]
is-the-issue-resolved{"<small><b>Step 5</b></small><br/>Question: Is the issue resolved?"}
aircraft-is-approved-to-return-to-serv("<small><b>Step 6</b></small><br/>Reference: Aircraft is approved to return to ser...")
attempt-power-cycle-the-aircraft-up-to["<small><b>Step 7</b></small><br/>Action: Attempt to power cycle the aircraft..."]
is-the-issue-resolved-after-additional{"<small><b>Step 8</b></small><br/>Question: Is the issue resolved after the addit..."}
aircraft-is-approved-to-return-after("<small><b>Step 9</b></small><br/>Reference: Aircraft is approved to return to ser...")
escalate-to-p2-navigation{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Nav On Call."}}
wait-10-minutes-to-see-if-the-error-cle --> send-the-aircraft-another-mission
send-the-aircraft-another-mission --> is-the-issue-resolved-after-mission
is-the-issue-resolved-after-mission -->|Yes| aircraft-is-approved-to-return-to-serv
is-the-issue-resolved-after-mission -->|No| if-the-alarm-persists-follow-the-proced
if-the-alarm-persists-follow-the-proced --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| aircraft-is-approved-to-return-to-serv
is-the-issue-resolved -->|No| attempt-power-cycle-the-aircraft-up-to
attempt-power-cycle-the-aircraft-up-to --> is-the-issue-resolved-after-additional
is-the-issue-resolved-after-additional -->|Yes| aircraft-is-approved-to-return-after
is-the-issue-resolved-after-additional -->|No| escalate-to-p2-navigation
style wait-10-minutes-to-see-if-the-error-cle fill:#dcfce7,stroke:#22c55e,color:#14532d
style send-the-aircraft-another-mission fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-mission fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style if-the-alarm-persists-follow-the-proced fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style aircraft-is-approved-to-return-to-serv fill:#f3e8ff,stroke:#a855f7,color:#581c87
style attempt-power-cycle-the-aircraft-up-to fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved-after-additional fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style aircraft-is-approved-to-return-after fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-navigation 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.