Skip to content

TRAFFIC_IN_TAKEOFF_AIRSPACE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
TRAFFIC_IN_TAKEOFF_AIRSPACE
Likely outcomes (5,526 missions, 56 issues) — click to expand

Based on 5,526 missions where this alarm fired in the last 90 days as of 2026-10-13

Grounding vs discrepancy (of 56 ZERP issues filed on these missions)

Grounding 50% (28 of 56 issues) Discrepancy 50% (28 of 56 issues)

Frequently replaced parts

Part P/N Removals
SERVO, ASSY, UNIVERSAL, P2 20398 34
WING PORT, ZIP, P2 24762 30
WING ASM FULL, STRBRD(RH), ZIP, P2 25266 30
CW/CCW HOVER MOTOR ASSY, ZIP, P2 19607 16
ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 48477 11

Frequently co-occurring alarms (% of the 5,526 missions above)

TRAFFIC_IN_DELIVERY_AIRSPACE 3.9% of missions SOFTWARE_CONFIGURATION_MISMATCH 2.2% of missions CROSS_COMPUTE_EDGE_SKEW_NOT_READY 1.4% of missions ANGLE_OF_ATTACK_CALIBRATION_FAILURE 1.4% of missions IRQ_AFFINITY_SETUP_INCOMPLETE 1.2% of missions

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

The Aircraft has detected another aircraft in the takeoff space. Takeoff will only be allowed after the airspace clears. You may see this alarm persist if the Aircraft was put to sleep while traffic was in the area.

1 action
Wake the Aircraft up, if applicable.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.