ERROR_INCORRECTLY_PROVISIONED_MOTOR
Applicable alarms (3)
Likely outcomes — click to expand
Based on 252 missions where this alarm fired in the last
90 days
(for MAINTENANCE_ACTION_REQUIRED) as of 2026-10-13
Grounding vs discrepancy (of 346 ZERP issues filed on these missions)
Top work orders
- EV2: Replace Hover Motor on Aircraft · MAINTENANCE_ACTION 31
- EV2: Replace Hover Propeller on Aircraft · MAINTENANCE_ACTION 25
- EV2/EV3 Diagnostics Test Without Motors · INSPECTION 22
- EV2: Replace Aft Motor Assembly on Aircraft · MAINTENANCE_ACTION 18
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 17
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| HOVER MOTOR ASSY, CCW MOTOR, ZIP, P2 | 19607 | 256 |
| CW EV3 HOVER MOTOR ASSY, ZIP, P2 | 33333 | 190 |
| AFT MOTOR ASSY, ZIP, P2 | 23548 | 134 |
| CCW HOVER PROPELLER BLADE, ZIP, P2 | 29857 | 103 |
| T800 CW HOVER PROPELLER, ZIP, P2 | 31101 | 103 |
Frequently co-occurring alarms (% of the 252 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 motor firmware detects a mismatch between the hardware’s configured part number and its actual type. It commonly occurs in units mislabeled during the transition to non-folding motors.
A batch of ~50 units originally labeled as 19607-001 B (folding CW) were actually 19607-003 D (non-folding CW/CCW).These units were not re-dyno tested after label replacement, resulting in firmware/hardware configuration mismatches. They function correctly and have the correct firmware on them, but the fact that the part number is incorrect is getting flagged by recent validators. If an Aircraft attempts to fly with one of these motors, the validator will flag an auto discrepancy that downs the Aircraft until maintenance follows the procedure below.
Troubleshooting Steps
Section titled “Troubleshooting Steps”Affected Serial Numbers
Section titled “Affected Serial Numbers”| Batch | Serial Range | Notes |
|---|---|---|
| 1 | 43550001 – 43550020 | CCW 19607-001B |
| 2 | 43600001 – 43600029 | CCW 19607-001B |
| 3 | 43610011, 500700001 | CCW 19607-001B |
graph TD
1-confirm-the-alarm-condition-alarm-ma["<small><b>Step 1</b></small><br/>Action: 1. Confirm the Alarm Condition. - Ala..."]
2-verify-the-motor-check-the-serial-nu["<small><b>Step 2</b></small><br/>Action: 2. Verify the Motor - Check the **ser..."]
3-correct-the-firmware-configuration-i["<small><b>Step 3</b></small><br/>Action: 3. Correct the Firmware Configuration..."]
4-verify-update-power-cycle-the-motor["<small><b>Step 4</b></small><br/>Action: 4. Verify Update - Power-cycle the mo..."]
5-if-alarm-persists-confirm-reflashed{{"<small><b>Step 5</b></small><br/>Escalation: 5. If Alarm Persists - Confirm reflas..."}}
1-confirm-the-alarm-condition-alarm-ma --> 2-verify-the-motor-check-the-serial-nu
2-verify-the-motor-check-the-serial-nu --> 3-correct-the-firmware-configuration-i
3-correct-the-firmware-configuration-i --> 4-verify-update-power-cycle-the-motor
4-verify-update-power-cycle-the-motor --> 5-if-alarm-persists-confirm-reflashed
style 1-confirm-the-alarm-condition-alarm-ma fill:#dcfce7,stroke:#22c55e,color:#14532d
style 2-verify-the-motor-check-the-serial-nu fill:#dcfce7,stroke:#22c55e,color:#14532d
style 3-correct-the-firmware-configuration-i fill:#dcfce7,stroke:#22c55e,color:#14532d
style 4-verify-update-power-cycle-the-motor fill:#dcfce7,stroke:#22c55e,color:#14532d
style 5-if-alarm-persists-confirm-reflashed fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
- Alarm: MAINTENANCE_ACTION_REQUIRED
- Off-nominal: INCORRECTLY_PROVISIONED_MOTOR
- Check the serial number against the affected list (see bottom of SOP).
- Visually confirm whether the motor is folding or non-folding (helix for folding vs bottom pin hole for non-folding).
Run:
fw-zip-power -i enp3s0 all-onfw-update --ip fe80::<interface>%<port> --port 50051 read-config-protoExample:
fw-update --ip fe80::33%enp3s0 --port 50051 read-config-proto- Note the reported LRU part number.
If the motor is non-folding (should be
19607-003D):Run:
fw-update -i fe80::<interface>%<port> update-config-proto --lru-part-number 19607003DExample:
fw-update -i fe80::30%enp3s0 update-config-proto --lru-part-number 19607003DReplace
<interface> and <port> with the actual network interface for that motor (e.g. enp3s0, eth0).- Power-cycle the motor.
Re-run:
fw-update --ip fe80::<interface>%<port> --port 50051 read-config-proto- Confirm LRU part number = 19607003D.
- Confirm the alarm no longer appears after restart.
- Confirm reflashed PN persisted post reboot.
- If mismatch remains:
- Escalate to P2 Firmware Motors On Call
- Include:
- Serial number
- Output of
fw-update - Dyno logs
- Screenshot/logs showing recurring alarm
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.