Safety Status Unavailable
Applicable alarms (2)
Likely outcomes — click to expand
Based on 72 missions where this alarm fired in the last
90 days
(for SAFETY_STATUS_UNAVAILABLE) as of 2026-10-13
Grounding vs discrepancy (of 24 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| LEFT DOOR ASSY, DROID, P2 | 21830 | 18 |
| RIGHT DOOR ASSY, DROID, P2 | 21827 | 18 |
| PARALAND ASSY, DROID, P2 | 18427 | 14 |
| BATTERY, DROID, P2 | 24544 | 12 |
| BRAIN, LRU, DROID, P2 | 31920 | 10 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”These alarms trigger if Zip Executive does not receive safety status messages within the watchdog timeout.
It is common to see these alarms temporarily during startup before the safety app is initialized and publishing status messages. If these alarms persist, they will prevent Zip Executive from progressing through preflight.
Exec watchdog alarms
Section titled “Exec watchdog alarms”- SAFETY_STATUS_UNAVAILABLE
- SAFETY_STATUS_B_UNAVAILABLE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
go-to-baraza-plots-and-identify-the-poi["<small><b>Step 1</b></small><br/>Action: Go to Baraza plots and identify the p..."]
plot-distro-a-safety-status-log-monotoni["<small><b>Step 2</b></small><br/>Action: Plot **/distro_a.safety_status.log_m..."]
was-the-safety-status-logged-on-compute{"<small><b>Step 3</b></small><br/>Question: Was the safety status logged on Compu..."}
power-cycle-the-aircraft-refer-to-power["<small><b>Step 4</b></small><br/>Action: Power cycle the Aircraft. Refer to P..."]
is-the-issue-resolved{"<small><b>Step 5</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 6</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-embedded-linux-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
escalate-to-p2-firmware-safety-on-call{{"<small><b>Step 8</b></small><br/>Escalation: Escalate to P2 Firmware Safety On Call."}}
go-to-baraza-plots-and-identify-the-poi --> plot-distro-a-safety-status-log-monotoni
plot-distro-a-safety-status-log-monotoni --> was-the-safety-status-logged-on-compute
was-the-safety-status-logged-on-compute -->|Yes| power-cycle-the-aircraft-refer-to-power
was-the-safety-status-logged-on-compute -->|No| escalate-to-p2-firmware-safety-on-call
power-cycle-the-aircraft-refer-to-power --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| escalate-to-p2-embedded-linux-on-call
style go-to-baraza-plots-and-identify-the-poi fill:#dcfce7,stroke:#22c55e,color:#14532d
style plot-distro-a-safety-status-log-monotoni fill:#dcfce7,stroke:#22c55e,color:#14532d
style was-the-safety-status-logged-on-compute fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-aircraft-refer-to-power fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-firmware-safety-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
NOTE: You may need to add some padding before.
/distro_a.safety_status.log_monotonic_ns on both Compute A and Compute B.Here is an example plot of what this would look like.
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.