EQUIVALENT_AIRSPEED_FAILURE
Applicable alarms (1)
Likely outcomes — click to expand
Based on 9 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 21 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| BATTERY ASSY, ZIP, P2 | 27158 | 25 |
| T800 CCW HOVER PROPELLER, ZIP, P2 | 29857 | 15 |
| T800 CW HOVER PROPELLER, ZIP, P2 | 31101 | 10 |
| RIGHT DOOR ASSY, DROID, P2 | 21827 | 8 |
| LEFT DOOR ASSY, DROID, P2 | 21830 | 8 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm is triggered when the wind estimator software estimates an airspeed that exceeds a set limit.
The underlying reasons could include but is not limited to: control instability, hardware/air-data sensor faults, poor nav state estimates, or the aircraft being physically stuck against an obstruction.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-the-aircraft-paraland{"<small><b>Step 1</b></small><br/>Question: Did the aircraft paraland?"}
check-compute-b-disqualification{"<small><b>Step 2</b></small><br/>Question: On the ZERP auto issue page, open **M..."}
follow-hardware-config-mismatch-guide["<small><b>Step 3</b></small><br/>Action: This is likely because compute B has ..."]
escalate-to-p2-zip-controls-on-call{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Zip Controls On Call"}}
did-the-aircraft-paraland -->|Yes| escalate-to-p2-zip-controls-on-call
did-the-aircraft-paraland -->|No| check-compute-b-disqualification
check-compute-b-disqualification -->|Yes| follow-hardware-config-mismatch-guide
check-compute-b-disqualification -->|No/Unsure| escalate-to-p2-zip-controls-on-call
style did-the-aircraft-paraland fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style check-compute-b-disqualification fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-hardware-config-mismatch-guide fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-zip-controls-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
EQUIVALENT_AIRSPEED_FAILURE caused compute B to be disqualified and exists only under ZIP_EXECUTIVE_V4_SECONDARY_FAILED.The alarm must appear only under
ZIP_EXECUTIVE_V4_SECONDARY_FAILED. If it appears in multiple places, select No.Example of the expected failure tree:
Does
EQUIVALENT_AIRSPEED_FAILURE cause the compute B disqualification and appear only under ZIP_EXECUTIVE_V4_SECONDARY_FAILED?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.