IMU_TIMESTAMP_ERROR_HIGH
Applicable alarms (1)
Likely outcomes — click to expand
Based on 210 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 24 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| BATTERY ASSY, ZIP, P2 | 27158 | 34 |
| DISTRO ASSY, ZIP, P2 | 0109371 | 12 |
| ASSM, FLIGHT COMPUTER, FORE, ZIP, P2 | 48408 | 12 |
| ASSM, FLIGHT COMPUTER, AFT, ZIP, P2 | 48409 | 11 |
| LEFT DOOR ASSY, DROID, P2 | 21830 | 8 |
Frequently co-occurring alarms (% of the 210 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”IMU_TIMESTAMP_ERROR_HIGH means an IMU sample timestamp check failed on one of the Aircraft computes. The recovery is to power cycle the Aircraft, then send a Run Health Checks mission from Fleet Wrangler. The Aircraft must complete that mission successfully before returning to service.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft. Refer to P..."]
what-is-the-preflight-outcome{"<small><b>Step 2</b></small><br/>Question: What is the outcome after the power c..."}
return-the-aircraft-to-service("<small><b>Step 3</b></small><br/>Reference: Return the Aircraft to service.")
follow-the-guide-for-that-error("<small><b>Step 4</b></small><br/>Reference: Follow the troubleshooting guide for ...")
escalate-to-p2-avionics-hardware{{"<small><b>Step 5</b></small><br/>Escalation: Keep the Aircraft out of service. Esc..."}}
power-cycle-the-aircraft --> what-is-the-preflight-outcome
what-is-the-preflight-outcome -->|Run Health Checks failed: ...| escalate-to-p2-avionics-hardware
what-is-the-preflight-outcome -->|Run Health Checks failed: a...| follow-the-guide-for-that-error
what-is-the-preflight-outcome -->|Run Health Checks succeeded...| return-the-aircraft-to-service
style power-cycle-the-aircraft fill:#dcfce7,stroke:#22c55e,color:#14532d
style what-is-the-preflight-outcome fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-aircraft-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style follow-the-guide-for-that-error fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-avionics-hardware fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.