ERROR_HOVER_PORT_AFT_RESISTANCE
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 3 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 high resistance is detected in the port aft hover motor’s DC power path.
Troubleshooting Steps
Section titled “Troubleshooting Steps”WORK ORDER TEMPLATE: Use Work Order Template #590: Troubleshoot Hover Motor Resistance on Aircraft.
NOTE: For all inspections, attach photos of the areas inspected to the ticket, including specific photos of issues.
graph TD
inspect-the-motor-in-question["<small><b>Step 1</b></small><br/>Action: Inspect the motor in question for any..."]
remove-unseat-all-bolted-connections["<small><b>Step 2</b></small><br/>Action: Remove/unseat all bolted connections ..."]
clean-and-reseat-the-bolted-connection["<small><b>Step 3</b></small><br/>Action: Clean and reseat the bolted connectio..."]
run-preflight-in-mx-dock["<small><b>Step 4</b></small><br/>Action: Run preflight in MX Dock."]
result-of-mx-dock{"<small><b>Step 5</b></small><br/>Question: Result of MX Dock"}
return-asset-to-service["<small><b>Step 6</b></small><br/>Action: Return Asset to service"]
escalate-to-p2-busbars-on-call{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Busbars On Call."}}
perform-maintenance-accordingly["<small><b>Step 8</b></small><br/>Action: Perform maintenance accordingly"]
inspect-the-motor-in-question --> remove-unseat-all-bolted-connections
remove-unseat-all-bolted-connections --> clean-and-reseat-the-bolted-connection
clean-and-reseat-the-bolted-connection --> run-preflight-in-mx-dock
run-preflight-in-mx-dock --> result-of-mx-dock
result-of-mx-dock -->|PASSES ALL CHECKS| return-asset-to-service
result-of-mx-dock -->|FAILS RESISTANCE CHECK| escalate-to-p2-busbars-on-call
result-of-mx-dock -->|FAILS FOR SEPARATE ISSUE| perform-maintenance-accordingly
style inspect-the-motor-in-question fill:#dcfce7,stroke:#22c55e,color:#14532d
style remove-unseat-all-bolted-connections fill:#dcfce7,stroke:#22c55e,color:#14532d
style clean-and-reseat-the-bolted-connection fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-preflight-in-mx-dock fill:#dcfce7,stroke:#22c55e,color:#14532d
style result-of-mx-dock fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-asset-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-busbars-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style perform-maintenance-accordingly fill:#dcfce7,stroke:#22c55e,color:#14532d 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.