Skip to content

Tail Missing Feedback

published Last Updated: Oct 9, 2026 HW: all
Applicable alarms (4)
MOTOR_CONTROL_FEEDBACK_SERVO_TAIL_PORT_FWD_UNAVAILABLEMOTOR_CONTROL_FEEDBACK_SERVO_TAIL_STBD_FWD_UNAVAILABLETAIL_PORT_MISSING_FEEDBACKTAIL_STBD_MISSING_FEEDBACK
Likely outcomes (656,635 missions, 2,993 issues) — click to expand

Based on 656,635 missions where this alarm fired in the last 90 days (for TAIL_STBD_MISSING_FEEDBACK) as of 2026-10-13

Grounding vs discrepancy (of 2,993 ZERP issues filed on these missions)

Grounding 45.9% (1,375 of 2,993 issues) Discrepancy 54.1% (1,618 of 2,993 issues)

Top work orders

  • EV2: Inspect Aircraft after Droid Left Behind (DLB) · MAINTENANCE_ACTION 234
  • EV2: Replace Aft Motor Assembly on Aircraft · MAINTENANCE_ACTION 87
  • EV2: Troubleshoot Electrical Contacts on Aircraft and Droid · INSPECTION 44
  • EV2: Replace Flight Computer on Aircraft · MAINTENANCE_ACTION 41
  • Troubleshoot Hover Motor Resistance on Aircraft · INSPECTION 40

Frequently replaced parts

Part P/N Removals
SERVO, ASSY, UNIVERSAL, P2 20398 959
CW/CCW HOVER MOTOR ASSY, ZIP, P2 19607 682
AFT MOTOR ASSY, EV.1 REWORK, ZIP, P2 23548 609
TAIL ASSY STBD(RH), PRE-EV2, ZIP, P2 21840 604
TAIL PORT, ZIP, P2 31280 575

Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.

The GNC Zip Controller faulted a tail servo because expected feedback messages were missing. The source troubleshooting treats non-rotor actuators as servo feedback paths.

1 telemetry
Check whether the affected tail servo had a poor communication connection during this mission.

Load the plot below and look only at the tail servo named by the active alarm. If the alarm is for the port tail servo, use the port tail servo traces. If the alarm is for the starboard tail servo, use the starboard tail servo traces. A spike on a different servo does not explain this alarm.

Look for signs that messages from the affected servo were being missed or corrupted. Poor comms are present if either of these is true outside a power cycle:

- The message counter jump, shown as message_sequence_number(delta), goes above 1.
- The RX frame error count goes above 10.

Ignore jumps that happen during an aircraft power cycle. A power cycle usually looks like several signals resetting at the same time, and Show Alarms should show power-cycle or reboot activity nearby. If the message counter goes negative, use Show Alarms to zoom in on the part of the mission near this missing-feedback alarm before deciding.

Representative poor-comms example:

Example plot showing message_sequence_number(delta) above the allowed threshold

Paste the mission identifier from the alarm report. The zip-node-comms-rs-485-errors plot loads in place below.

Enter the mission identifier above to load the plot.

Did this guide help you get unblocked?

Open suggestions

There are no open suggestions.

Open pull requests

There are no open pull requests.