SW_INSTANTANEOUS_OVERCURRENT
Applicable alarms (1)
Likely outcomes — click to expand
Based on 2 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 2 ZERP issues filed on these missions)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when the Aircraft battery pack has experienced an overcurrent event. Treat it as safety-critical because an overcurrent can indicate an unsafe battery state and damaged battery pack. For Aircraft in the test fleet, rebooting the Aircraft or restarting Zip Executive is sufficient to clear the alarm and return the Aircraft to service without Powertrain review. For all other Aircraft, do not return the Aircraft to service until Powertrain On Call reviews the event and confirms that there is no serious hardware damage. For Commercial Aircraft, the length and severity of the fault determine the course of action, as determined by engineering.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-aircraft-in-the-test-fleet{"<small><b>Step 1</b></small><br/>Question: Is this Aircraft in the test fleet?"}
reboot-the-aircraft-or-restart-zip-executive["<small><b>Step 2</b></small><br/>Action: Reboot the Aircraft or restart Zip E..."]
load-the-failed-mission-and-inspect-the-plot["<small><b>Step 3</b></small><br/>Telemetry: Enter the mission ID from the failed ..."]
did-the-overcurrent-exceed-420-amps{"<small><b>Step 4</b></small><br/>Question: Did the overcurrent exceed 420 amps?"}
swap-battery["<small><b>Step 5</b></small><br/>Action: Escalate to Powertrain On Call."]
escalate-to-pwt-on-call-so-that-engineering-can-review{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to Powertrain On Call so tha..."}}
is-the-aircraft-in-the-test-fleet -->|Yes| reboot-the-aircraft-or-restart-zip-executive
is-the-aircraft-in-the-test-fleet -->|No| load-the-failed-mission-and-inspect-the-plot
load-the-failed-mission-and-inspect-the-plot --> did-the-overcurrent-exceed-420-amps
did-the-overcurrent-exceed-420-amps -->|Confirmed exceeded 420 amps| swap-battery
did-the-overcurrent-exceed-420-amps -->|Did NOT exceed 420 amps| escalate-to-pwt-on-call-so-that-engineering-can-review
style is-the-aircraft-in-the-test-fleet fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style reboot-the-aircraft-or-restart-zip-executive fill:#dcfce7,stroke:#22c55e,color:#14532d
style did-the-overcurrent-exceed-420-amps fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style swap-battery fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-pwt-on-call-so-that-engineering-can-review 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.