Skip to content

IMPACT_DETECTED_WHILE_DOCKED

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (1)
IMPACT_DETECTED_WHILE_DOCKED
Likely outcomes (8,953 missions, 51 issues) — click to expand

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

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

Grounding 58.8% (30 of 51 issues) Discrepancy 41.2% (21 of 51 issues)

Frequently replaced parts

Part P/N Removals
LONG WING ASSY, DEPOPULATED, STBD (RH), ZIP, P2 0108493 18
LONG WING ASM, PORT(LH), ZIP, P2 0100553 18
SERVO, ASSY, UNIVERSAL, P2 20398 11
ASSY, SPOOL AND LINE, DOCKING FIN 48477 8
BATTERY ASSY, ZIP, P2 27158 5

Frequently co-occurring alarms (% of the 8,953 missions above)

AMB_TEMP_TIMED_OUT 13.9% of missions HUMIDITY_TIMED_OUT 13.9% of missions ADSB_NOT_READY 9.9% of missions CONTROLLER_RAN_OUT_OF_SPLINE 9.5% of missions UNTRUSTED_CLOCK_REFERENCE 2.8% of missions

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

This alarm triggers when a docked Zips feels an unusually high impact.

This alarm was implemented as a prerequisite to removing pre-flight visual inspections. The rationale being that if a Zip experiences significant physical damage while docked, it should be detectable as an impact.

Therefore these impacts, and subsequent alarms, require a visual inspection of the Zip before returning it to operations.

Also see the summary slide for this feature in Software Spotlights Series.

1 question
Was the impact captured on video?

Obtain the video from the site cameras (request access from IT if you do not have it). Note the alarm timestamp and review the video to see if the impact is captured.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.