Aft Motor Temperature Unavailable
This alarm is covered by this guide. Applicable alarms (2)
Likely outcomes — click to expand
Based on 851,846 missions where this alarm fired in the last
90 days
(for MOTOR_TEMP_HOVER_PORT_AFT_UNAVAILABLE) as of 2026-10-13
Grounding vs discrepancy (of 4,450 ZERP issues filed on these missions)
Top work orders
- EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 231
- EV3: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 214
- Inspect Droid after Droid Left Behind (DLB) · MAINTENANCE_ACTION 184
- Reset Droid after DLB · REPAIR 117
- Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 77
Frequently replaced parts
| Part | P/N | Removals |
|---|---|---|
| SERVO, ASSY, UNIVERSAL, P2 | 20398 | 977 |
| CCW HOVER MOTOR ASSY, ZIP, P2 | 19607 | 791 |
| ASSY, SPOOL AND LINE, DOCKING FIN, AIRCRAFT, P2 | 48477 | 779 |
| TAIL STBD DEPOP, ZIP, P2 | 21840 | 624 |
| TAIL PORT, ZIP, P2 | 31280 | 594 |
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”These alarms occur when Zip Exec has not received a temperature status message reported by an aft hover motor within the watchdog timeout. This usually occurs if a motor service is crashing, running at too slow of a rate, or publishing too infrequently.
This alarm could indicate a hardware issue. This alarm can also be caused by compute performance issues and IPC issues (these cases often see multiple watchdog alarms). If the alarm occurs during preflight once we attempt motor checks, or in flight, follow the troubleshooting steps below.
Exec watchdog alarms
Section titled “Exec watchdog alarms”- MOTOR_TEMP_HOVER_PORT_AFT_UNAVAILABLE
- MOTOR_TEMP_HOVER_STBD_AFT_UNAVAILABLE
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
use-the-active-alarms-feature-in-baraz["<small><b>Step 1</b></small><br/>Action: Use the **Active Alarms** feature in ..."]
if-there-is-no-troubleshooting-guide{{"<small><b>Step 2</b></small><br/>Escalation: Follow the guide for the alarm. If th..."}}
use-the-active-alarms-feature-in-baraz --> if-there-is-no-troubleshooting-guide
style use-the-active-alarms-feature-in-baraz fill:#dcfce7,stroke:#22c55e,color:#14532d
style if-there-is-no-troubleshooting-guide 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.