SW_EXTENDED_OVERCURRENT
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 16 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 13 ZERP issues filed on these missions)
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 12 |
| CW HOVER MOTOR ASSY, ZIP, P2 | 33333 | 8 |
Frequently co-occurring alarms (% of the 16 missions above)
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 extended overcurrent event.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
load-the-failed-mission-into-the-battery-health-overcurrent-check["<small><b>Step 1</b></small><br/>Telemetry: Enter the mission ID from the failed ..."]
did-pack-current-exceed-300-a{"<small><b>Step 2</b></small><br/>Question: Did **/distro_a.zip_battery_telemetry..."}
measure-overcurrent-duration-and-escalate{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to Powertrain On Call to con..."}}
confirm-return-to-service-with-powertrain{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to Powertrain On Call to con..."}}
load-the-failed-mission-into-the-battery-health-overcurrent-check --> did-pack-current-exceed-300-a
did-pack-current-exceed-300-a -->|Yes, above 300 A| measure-overcurrent-duration-and-escalate
did-pack-current-exceed-300-a -->|No, 300 A or below| confirm-return-to-service-with-powertrain
style did-pack-current-exceed-300-a fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style measure-overcurrent-duration-and-escalate fill:#fef3c7,stroke:#f59e0b,color:#78350f
style confirm-return-to-service-with-powertrain 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.