TRAFFIC_IN_DELIVERY_AIRSPACE
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 1,365 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 14 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| WING ASM FULL, TRIAX, NO DAA, PORT(LH), ZIP, P2 | 24762 | 30 |
| WING STBD DEPOP, ZIP, P2 | 25266 | 30 |
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 8 |
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 6 |
| CW HOVER MOTOR ASSY, ZIP, P2 | 33333 | 4 |
Frequently co-occurring alarms (% of the 1,365 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”The aircraft has detected other non-Zipline aircraft in the delivery airspace.
The alarm will clear on its own once the airspace clears. Delivery will be aborted. No operator intervention is required.
The aircraft can be immediately returned to service.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
if-the-alarm-is-recurring-monitor-flee["<small><b>Step 1</b></small><br/>Action: If the alarm is recurring, monitor Fl..."]
style if-the-alarm-is-recurring-monitor-flee fill:#dcfce7,stroke:#22c55e,color:#14532d 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.