AAE5304 Chap.3 UAV Systems, Control and Failure Paths
UAV Systems, Control and Failure Paths
Follow the control loop
Pilot or mission intent travels through the command link, flight controller and electronic speed controllers to motors and propellers. Sensor and health information returns so the controller can correct position, attitude, altitude and power.
Write failures as chains
A component fault is not the final safety statement.
Identify the lost function, immediate system effect, aircraft behaviour and operational outcome before selecting redundancy or procedure.
Keep control modes distinct
Equal rotor-speed changes alter total lift. Front-to-rear and side-to-side imbalances create pitch and roll.
Torque-pair imbalance creates yaw, subject to the actual rotation convention.
Trace command and feedback separately
The command path carries intended action from pilot or mission logic to actuators. The feedback path carries position, attitude, altitude, speed and health information back to the controller. A failure can corrupt either path, and the observable symptom may look similar.
State where information is generated, transmitted, interpreted and acted upon. That sequence helps distinguish a failed motor command from a false sensor input or lost communication link.
Expand the fault into a consequence
Use five links: initiating fault, lost function, immediate system effect, aircraft behaviour and operational outcome.
A battery fault might reduce available power, limit thrust, cause descent and create a ground-impact hazard. The chain prevents the analysis from stopping at a component name.
It also identifies where detection, isolation, redundancy, contingency action or route design can interrupt the progression before the consequence occurs.
Test common causes before claiming redundancy
Two components do not create two independent safety paths when they share power, software, sensors, cooling, mounting or communication. Draw both claimed paths and circle every shared dependency.
Then ask whether the initiating event can remove both at once. A credible redundancy claim needs independence, detection of the failed channel, a switching or control strategy and enough remaining performance to reach a safe state.
Connect failure handling to the environment
Return-to-home, hover, landing and flight termination are not universally safe responses.
A stored home point can be obstructed, hover can consume energy during link loss, and immediate landing can expose people below. Evaluate the automated response against route geometry, remaining energy, navigation confidence and ground exposure. The correct control is the one that reduces the actual consequence in the stated mission.
What this chapter covers
- 01
Airframe and propulsion functions
- 02
Flight controller and sensors
- 03
Command and communication links
- 04
GPS, barometer and return-to-home
- 05
Pitch, roll, yaw and reaction torque
- 06
Fault, effect and outcome chains
Worked example · free
Diagnose a return-to-home hazard
- 3Name the initiating fault and automatic response.
- 3Identify the stale assumption.
- 3Select controls that address the actual chain.
Key terms
- Flight Controller
- The processor that interprets sensor data and commands aircraft control action.
- Electronic Speed Controller
- The device that converts control commands into motor-speed changes.
- Return To Home
- An automated response that navigates the aircraft toward a recorded home point.
UAV Systems, Control and Failure Paths FAQ
Why is a component list not a failure analysis?
A list does not show which safety function is lost or what the aircraft then does. Failure analysis connects fault, immediate effect, aircraft behaviour and consequence. That chain reveals whether redundancy, monitoring, a route change or an emergency procedure can actually control the risk.
How does a quadcopter create yaw?
Opposing rotor pairs turn in opposite directions so their reaction torques normally balance. Changing the speed balance between clockwise and counterclockwise pairs creates a net torque and rotates the aircraft. Always state the rotor numbering and direction convention before naming left or right yaw.
Can video fail while command remains available?
Yes. Video or payload data and control commands can use different paths or performance thresholds. If steering still responds, diagnose degraded video separately from total command-link loss, while applying the visibility and contingency rules relevant to the mission.
When is a safe-state claim incomplete?
It is incomplete until the response is checked against remaining energy, navigation confidence, route geometry and the people or property exposed below throughout the manoeuvre.
Exam move
Draw the command path and feedback path from memory. For battery, GPS, barometer, radio, flight controller, ESC and motor, write one fault, one lost function, one observable symptom and one control. Reject any proposed redundancy that shares the same cause. For each control, state how the failure is detected, what safe state is commanded and which mission assumption makes that state acceptable.
Then change the route environment and check whether the response still reduces risk. Practise distinguishing control-link loss, video loss and navigation degradation from the symptoms alone. For rotor questions, state the rotation convention before assigning a yaw direction and separate equal thrust change from differential thrust.
Close every scenario with a common-cause check across power, software, sensors, cooling and mounting. The goal is a traceable failure chain, not a list of components or generic claims that redundancy improves safety.
