Skip to content

SIDE_A_MISSED_COOPERATIVE_AIRCRAFT

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
SIDE_A_MISSED_COOPERATIVE_AIRCRAFT
Likely outcomes (74 missions, 2 issues) — click to expand

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

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

Grounding 100% (2 of 2 issues) Discrepancy 0% (0 of 2 issues)

Frequently co-occurring alarms (% of the 74 missions above)

ADSB_HIGH_DEVICE_CPU_LOAD 13.5% of missions

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

This is a DAA related detection performance alarm. The DAA Tracker uses the detections from the ADSB device in each compute. This alarm gets activated when the ADSB device in compute A does not get position detections that compute B sees during a minute of flight (or data streaming when docked) inside of the safety puck 5 km radius laterally and 2.5 km half height. This indicates degradation in either the device or the antennas. Compute A is considered the main source of detections.

During preflight it will block launch; during flight it will command a DockAsap so the cooperative DAA system avoids working with degraded hardware.

1 question
Does this alarm occur during preflight or flight?

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests