Skip to content

ATTITUDE_TRACKING_FAILURE

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
ATTITUDE_TRACKING_FAILURE
Likely outcomes (12 missions, 21 issues) — click to expand

Based on 12 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)

Grounding 9.5% (2 of 21 issues) Discrepancy 90.5% (19 of 21 issues)

Frequently replaced parts

Part P/N Removals
BATTERY ASSY, ZIP, P2 27158 55
T800 CCW HOVER PROPELLER, ZIP, P2 29857 15
PARALAND ASSY, AIRCRAFT, P2 18480 10
T800 CW HOVER PROPELLER, ZIP, P2 31101 10
NOSECONE ASSY, DEPOP, ZIP, P2 26121 9

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

DISTRO_A_COMPUTE_A_DISQUALIFIED 100% of missions DISTRO_B_FAILOVER_TO_COMPUTE_B_ACTIVE 100% of missions DISTRO_B_COMPUTE_A_DISQUALIFIED 100% of missions COMPUTE_A_SELF_DISQUALIFIED 100% of missions LATERAL_TRACKING_FAILURE 100% of missions

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

This alarm is triggered when the navigation roll or pitch value exceeds a set limit. In flight, this will trigger a paraland.

The underlying reasons could include but is not limited to: control instability, hardware faults, or poor nav state estimates.

1 escalation

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.