NOT_CRITICAL_SERVICE_RESTARTED
Applicable alarms (1)
Likely outcomes — click to expand
Based on 478 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 19 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| BATTERY ASSY, ZIP, P2 | 27158 | 27 |
| NOSECONE ASSY, ZIP, P2 | 26121 | 18 |
| PARALAND ASSY, ZIP, P2 | 18480 | 7 |
Frequently co-occurring alarms (% of the 478 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm is set when a service restarted that is NOT critical for flight. These services are not responsible for keeping the Aircraft in the air. This alarm will automatically clear on the next pre-flight attempt.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
re-attempt-preflight-is-the-issue-resol{"<small><b>Step 1</b></small><br/>Question: Re-attempt preflight. Is the issue re..."}
the-aircraft-may-return-to-service("<small><b>Step 2</b></small><br/>Reference: The Aircraft may return to service.")
identify-the-unit-name-in-the-alarm-rep["<small><b>Step 3</b></small><br/>Action: Identify the Unit Name in the Alarm R..."]
identify-the-responsible-team-name-in{{"<small><b>Step 4</b></small><br/>Escalation: Identify the Responsible Team name in..."}}
re-attempt-preflight-is-the-issue-resol -->|Yes| the-aircraft-may-return-to-service
re-attempt-preflight-is-the-issue-resol -->|No| identify-the-unit-name-in-the-alarm-rep
identify-the-unit-name-in-the-alarm-rep --> identify-the-responsible-team-name-in
style re-attempt-preflight-is-the-issue-resol fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style identify-the-unit-name-in-the-alarm-rep fill:#dcfce7,stroke:#22c55e,color:#14532d
style identify-the-responsible-team-name-in 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.