Fly-Away Prevention and Response
A true fly-away is rarer than a lost link, but far more serious, because it means the aircraft is no longer behaving predictably at all — not simply out of communication, but actively doing something the remote pilot did not command and cannot easily stop. This lesson has no dedicated Part 107 regulation number of its own; it is grounded in the same 14 CFR 107.21 deviation authority and 107.19 responsibility covered in the previous lesson, plus 14 CFR 107.23's hazardous-operation standard, which continues to apply to the pilot's response even during a genuine fly-away.
Defining a true fly-away
A fly-away is a situation in which the small unmanned aircraft is flying in a way the remote pilot did not command, and often cannot correct even though the control link itself may still be technically connected. This is the critical distinction from a lost link, covered in the previous lesson: a lost link is a communication problem with a known, predictable failsafe response; a fly-away is a behavior problem, where the aircraft's own flight controller is doing something unexpected — ignoring inputs, executing an incorrect autonomous maneuver, or drifting in a direction with no apparent cause — regardless of whether commands are getting through.
14 CFR 107.23: the standard that never goes away, even in a fly-away
14 CFR 107.23 states, in full: "No person may: (a) Operate a civil small unmanned aircraft system in a careless or reckless manner so as to endanger the life or property of another; or (b) Allow an object to be dropped from a civil small unmanned aircraft system in a manner that creates an undue hazard to persons or property." This regulation matters enormously during a fly-away because it does not pause just because an emergency is underway. 14 CFR 107.21 permits the remote pilot to deviate from a rule to meet the emergency, but it never authorizes a careless or reckless response, and it never authorizes creating an undue hazard through how the response is carried out. Every action taken during a fly-away must still meet the 107.23 standard.
Common causes of a true fly-away
Several distinct failure modes can produce a genuine fly-away, and understanding them is the foundation of prevention. Magnetic interference near large metal structures, power lines, or rebar-reinforced concrete can corrupt the aircraft's compass reading, causing it to believe it is pointed in a direction it is not and fly accordingly. GPS multipath errors, common in dense urban environments where satellite signals bounce off buildings before reaching the aircraft's receiver, can feed the flight controller inaccurate position data. Electronic speed controller (ESC) or motor desynchronization can cause a sudden, uncommanded change in one motor's output, destabilizing the aircraft. Firmware or software bugs, though rare in mature, well-tested products, can occasionally cause a flight controller to misinterpret sensor data or execute an incorrect autonomous behavior.
- Compass/magnetic interference: most preventable through a proper preflight compass calibration performed away from metal structures and vehicles.
- GPS multipath: most likely in urban canyons and near tall reflective buildings; harder to eliminate entirely but worth recognizing as elevated risk.
- ESC/motor desync: often preceded by warning signs during preflight motor checks, reinforcing the value of Module 10's preflight inspection procedures.
- Firmware/software bugs: a reason to apply manufacturer firmware updates thoughtfully, as covered in Module 10's manufacturer maintenance lesson, rather than ignoring them indefinitely.
Worked scenario: recognizing and responding to a fly-away in progress
During a commercial inspection flight, your aircraft suddenly drifts sideways despite no stick input, then begins climbing on its own while the controller shows the link as still connected. This is not a lost link — the aircraft is disobeying inputs while still receiving them, which is the signature of a true fly-away. Under 107.21, you may deviate from normal procedure to meet this emergency: attempting a mode reset, cycling the GPS mode off and back to a manual attitude mode to regain some predictable control, or, if the aircraft remains uncontrollable and is over an unpopulated area, considering a controlled power cutoff to bring it down quickly rather than let it continue toward people or property. Whatever action is taken, 107.23 still requires that the choice not be careless or reckless — cutting power directly over a crowd to "regain control" faster would trade one hazard for a worse one, and would not meet the 107.23 standard even under emergency pressure.
A lost link is a communication problem with a predictable failsafe; a true fly-away is a behavior problem where the aircraft disobeys commands even while still connected.
View Larger| Cause | How it manifests | Primary prevention |
|---|---|---|
| Compass/magnetic interference | Aircraft flies in a direction inconsistent with commanded heading | Compass calibration away from metal structures and vehicles |
| GPS multipath error | Aircraft drifts or jumps position unexpectedly | Awareness of elevated risk in urban canyons; consider manual flight modes |
| ESC/motor desynchronization | Sudden, uncommanded instability or erratic motion | Thorough preflight motor and propeller inspection (Module 10) |
| Firmware/software bug | Incorrect autonomous behavior or misread sensor data | Thoughtful, tested firmware update practices (Module 10) |
Responding to a Suspected Fly-Away
A response sequence that keeps 14 CFR 107.23 in view throughout, even under time pressure.
Confirm this is genuinely a fly-away, not a lost link
Check whether the aircraft is disobeying commands while the link still shows connected — the signature of a fly-away, distinct from a lost-link failsafe executing as designed.
Attempt a mode reset or switch to a more basic flight mode
Try cycling GPS-assisted mode off in favor of a manual attitude mode, which can sometimes bypass whatever sensor issue is driving the erratic behavior.
Continuously reassess whether the aircraft poses a hazard to people or property
Track the aircraft's trajectory relative to bystanders, vehicles, and structures, updating your assessment as the situation develops.
If control cannot be regained and the aircraft threatens people or property, consider a controlled power cutoff only over a genuinely clear area
Weigh a deliberate motor cutoff against the alternative of letting the aircraft continue on its current path, choosing whichever option creates the least hazard.
Alert bystanders and any ground crew immediately
Warn people in the aircraft's likely path as early as possible, using the communication procedures established in your contingency plan.
Document the event thoroughly afterward
Record what was observed, what actions were taken and why, and the outcome — needed for a possible 107.21(b) report and for identifying the root cause to prevent a repeat.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Treating every lost-link event as a fly-away | Both involve the aircraft not doing what was expected | A lost link with a working failsafe is a communication issue; a fly-away is a behavior issue where the aircraft ignores or misinterprets commands. | 14 CFR 107.19 |
| Believing 14 CFR 107.21 excuses any response taken during a fly-away | The deviation authority feels like it removes all constraints during an emergency | 14 CFR 107.23's careless/reckless prohibition still applies; the response itself must not create a worse hazard. | 14 CFR 107.23 |
| Skipping compass calibration because "it worked fine last time" | Calibration feels like an unnecessary extra step | Compass/magnetic interference is one of the most common and most preventable causes of a fly-away. | Preflight best practice (14 CFR 107.15 context) |
| Assuming a fly-away can only be caused by a hardware failure | Mechanical explanations feel more intuitive than software ones | Firmware or software bugs, GPS multipath, and magnetic interference are all common non-mechanical causes. | N/A (technical cause, not a regulation) |
Is every erratic aircraft movement a fly-away?
No. A brief wind gust correction or a normal failsafe activation can look alarming without being a true fly-away. A fly-away specifically means the aircraft is ignoring or misinterpreting commands in a way that is not explained by a known cause like wind or an expected failsafe behavior.
Does 14 CFR 107.21 allow a remote pilot to do anything necessary to stop a fly-away?
No. 107.21 authorizes deviation from a rule to the extent necessary to meet the emergency, but 14 CFR 107.23's prohibition on careless or reckless operation still applies to how that response is carried out.
What is the single most preventable cause of a fly-away?
Compass and magnetic interference errors are generally the most preventable, since a proper preflight compass calibration performed away from metal structures and vehicles substantially reduces this risk.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.