Skip to content

TRAFFIC_IN_DELIVERY_AIRSPACE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
TRAFFIC_IN_DELIVERY_AIRSPACE
Likely outcomes (1,365 missions, 14 issues) — 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)

Grounding 28.6% (4 of 14 issues) Discrepancy 71.4% (10 of 14 issues)

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)

HIGH_VERT_WINDS_DETECTED 28.4% of missions TRAFFIC_IN_TAKEOFF_AIRSPACE 15.6% of missions STALE_CYCLE_METRICS_RECORD 8.1% of missions DIFFERENTIAL_PRESSURE_INPUT_TIMED_OUT 7% of missions ABSOLUTE_PRESSURE_INPUT_TIMED_OUT 6.9% of missions

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

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.

1 action
If the alarm is recurring, monitor FleetView for air traffic near the delivery site, and wait for the traffic to clear.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.