0x0002002e DROID_ERROR_WIND_NOT_ALIGNED
Applicable alarms (2)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0002002e) 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 means the Aircraft did not point into the wind before delivery.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
re-attempt-the-delivery["<small><b>Step 1</b></small><br/>Action: Re-attempt the delivery."]
if-the-issue-reoccurs-escalate-to-p2-d{{"<small><b>Step 2</b></small><br/>Escalation: If the issue reoccurs, escalate to P2..."}}
re-attempt-the-delivery --> if-the-issue-reoccurs-escalate-to-p2-d
style re-attempt-the-delivery fill:#dcfce7,stroke:#22c55e,color:#14532d
style if-the-issue-reoccurs-escalate-to-p2-d 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.