What is the Return-to-Home function on a drone and how does it work?

Return-to-Home (RTH) is an automated safety feature found on many small unmanned aircraft systems that commands the aircraft to fly back to a pre-recorded launch point when triggered manually, by low battery, or by loss of control link signal. The drone typically uses GPS coordinates saved at the time of takeoff to navigate back and land autonomously. However, the FAA emphasizes in its small UAS guidance that remote pilots must understand RTH is a manufacturer-provided feature—not a regulatory safety net—and its reliability depends entirely on GPS signal quality, compass calibration, and obstacle-sensing capabilities.

Why might a Return-to-Home feature fail during an actual drone emergency?

RTH can fail for several reasons, including degraded or lost GPS signal, compass interference from nearby metal structures or magnetic fields, and a home point that was never properly recorded before takeoff. Additionally, if RTH altitude is set lower than surrounding obstacles such as trees or buildings, the drone may collide with them during its automated return flight. The FAA's remote pilot certification knowledge areas stress that remote pilots in command are always responsible for the safe outcome of a flight and must be prepared to intervene manually rather than rely solely on automated emergency functions.

What's the difference between a Return-to-Home failure and a flyaway, and how should a remote pilot respond?

A flyaway occurs when the drone leaves the remote pilot's intended flight path and cannot be controlled or recalled, while an RTH failure means the automated return sequence does not execute correctly or leads the aircraft into danger. Both scenarios require the remote pilot in command to take immediate manual corrective action if possible, or—if control cannot be regained—to alert people in the area and report the incident in accordance with 14 CFR Part 107 accident reporting requirements if there is resulting injury or property damage. The Airman Certification Standards for the FAA Knowledge Test for a Remote Pilot Certificate with a Small UAS Rating expects applicants to recognize these limitations and demonstrate sound aeronautical decision-making rather than over-reliance on automation.

Return-to-Home Function Limitations and Failures

The Return-to-Home (RTH) function is one of the most widely marketed safety features on consumer and prosumer small unmanned aircraft systems (sUAS). With the press of a button — or automatically, when the aircraft loses its control link — the drone is supposed to fly itself back to the launch point and land safely. It sounds like an ideal emergency backup, and in benign conditions it works well. However, as a Part 107 remote pilot, you are the pilot in command (PIC) and you bear full responsibility for the safe outcome of every flight. Understanding precisely where RTH can save the day and where it can make a bad situation catastrophically worse is not optional knowledge — it is a core emergency-procedures competency.

This article examines the technical mechanisms behind RTH, the regulatory and practical reasons you cannot treat it as a guaranteed safety net, the common failure modes you must anticipate, and the decision-making framework you should apply before and during any emergency where RTH might seem like an easy solution.

How Return-to-Home Works

RTH relies on the interaction of several onboard systems working correctly and simultaneously. When activated — either manually by the pilot or automatically by the flight controller — the aircraft typically follows a sequence: climb to a pre-programmed or auto-calculated RTH altitude, navigate back toward the recorded home-point coordinates using GNSS (Global Navigation Satellite System, most commonly GPS), descend, and land. Each one of those steps depends on a different subsystem.

GNSS and the Home Point

The home point is recorded at the moment the aircraft first acquires a sufficient GNSS fix — usually at power-on or at the moment of takeoff. If the home point was recorded indoors, in a GNSS-degraded environment (such as near large metal structures or under dense tree canopy), or before the receiver had a strong enough fix, the stored coordinates may be inaccurate by tens of meters or more. The aircraft will faithfully fly to whatever coordinates it recorded, even if those coordinates are not where you are standing.

During the return leg, the aircraft still depends on real-time GNSS reception to navigate. GNSS signal quality can degrade or drop entirely due to multipath interference from buildings, signal blocking by terrain, atmospheric disturbances, or radio frequency (RF) interference from other electronic equipment. If GNSS accuracy degrades significantly en route, the aircraft may drift, oscillate, or enter an attitude-hold mode rather than navigate home accurately.

RTH Altitude Setting

Most flight controller systems allow the remote pilot to pre-set an RTH altitude. The aircraft climbs to that altitude before beginning the return leg, in theory to clear obstacles. This only works if the pilot has set an RTH altitude that actually clears all obstacles along the entire flight path — not just near the launch point. A RTH altitude of 30 feet will not clear a 50-foot tree between the aircraft and home. A RTH altitude set too high may cause the aircraft to exceed 400 feet above ground level (AGL), which is the standard operating ceiling under 14 CFR Part 107 unless an exception applies. The remote pilot is legally and operationally responsible for ensuring the RTH altitude does not create a regulatory violation or a collision hazard.

Compass Calibration and Magnetic Interference

RTH navigation also depends on the aircraft's magnetometer (compass) for heading reference. Compass calibration errors — caused by metallic objects near the aircraft at calibration time, or by flying near structures with strong magnetic fields — can corrupt the heading reference and cause the aircraft to fly in a completely wrong direction during RTH. Some pilots have reported aircraft flying directly away from the home point because of an uncorrected compass error. This failure mode is particularly dangerous because the aircraft appears to be executing a normal RTH sequence while actually diverging.

Why RTH Cannot Substitute for PIC Judgment

Under 14 CFR Part 107.19, the remote PIC is directly responsible for and is the final authority on the operation of the small unmanned aircraft. RTH is an automated function of the aircraft's flight controller; it is not a substitute for the human judgment, situational awareness, and real-time decision-making the regulations place on the remote pilot.

Consider a scenario: you are flying in an urban corridor and you lose visual contact with the aircraft. You activate RTH. The aircraft climbs to its pre-set altitude and begins navigating home — directly toward a construction crane that was not in the area when you planned your flight. The aircraft has no way to know the crane is there. Obstacle avoidance sensors, if present, only detect objects within their limited field of view and range, and many lower-cost sUAS have no obstacle avoidance at all on their upward-facing or rear-facing surfaces. RTH does not guarantee obstacle clearance. Only the remote pilot, exercising see-and-avoid responsibilities and pre-flight planning, can provide that assurance.

Additionally, 14 CFR Part 107.31 requires that the remote PIC maintain visual line of sight (VLOS) with the sUAS, with limited exceptions. If you have lost VLOS — the very condition that often prompts a pilot to trigger RTH — you are already in a situation that may constitute a regulatory deviation. RTH does not restore your VLOS; it simply brings the aircraft back toward a position where you might eventually reacquire VLOS. During that entire return flight, you are not in compliance with the spirit and letter of the VLOS requirement.

Common RTH Failure Modes

Knowing the specific ways RTH can fail will help you plan mitigations before each flight and respond correctly when problems arise in flight.

Poor or delayed home-point lock: If the aircraft powers on and is immediately flown before acquiring a strong GNSS fix (typically indicated by a certain number of satellites and a low horizontal dilution of precision), the stored home-point coordinates may be significantly off. Always wait for a solid GNSS lock before flight.
Home-point drift after auto-recording: Some systems re-record the home point periodically or when GNSS accuracy improves. If you have walked away from your launch position while the aircraft was airborne, the home point may have updated to your current location — which might be in the middle of a roadway or inside a building.
GNSS jamming or spoofing: In some geographic areas, GNSS jamming or spoofing can cause the aircraft to receive false position data. This is an increasing concern near certain government facilities, border regions, and active conflict zones. A spoofed GNSS signal could direct the aircraft to a completely incorrect position during RTH.
Low battery RTH triggering at the wrong moment: Many systems include an automatic low-battery RTH trigger. If this occurs at a distance or altitude where the battery cannot sustain a full RTH sequence, the aircraft may land short — in water, on a road, or in another unsafe location — rather than at the intended home point.
Wind and RTH altitude interaction: Strong headwinds can dramatically reduce the aircraft's effective airspeed during RTH, increasing power consumption and potentially exhausting the battery before the aircraft reaches home. If the RTH altitude is set very high, the climb itself consumes significant battery capacity before the return leg even begins.
Compass interference during RTH: Flying past large ferromagnetic structures — steel-reinforced buildings, bridges, power lines — can temporarily corrupt the compass mid-flight, causing the aircraft to deviate from the intended RTH track.

Key Numbers and Rules

400 feet AGL: The general ceiling under 14 CFR Part 107.51 for sUAS operations (with the structure exception). RTH altitude must be set to avoid exceeding this limit.
Visual line of sight: Required under 14 CFR Part 107.31. RTH does not grant an exception to VLOS requirements.
PIC responsibility: 14 CFR Part 107.19 — the remote PIC bears final authority and responsibility for every aspect of the operation, including the outcome of any automated function.
Pre-flight planning requirement: Effective RTH use requires knowing the RTH altitude, confirming a solid home-point lock, and having mapped obstacle clearance along plausible return routes before departure.
Obstacle avoidance limitations: Even sUAS with active obstacle avoidance sensors typically have blind spots (above, behind, or below) and limited detection range. RTH should never be assumed to provide guaranteed collision avoidance.

Common Test Traps

RTH as an emergency substitute: The FAA knowledge test may present RTH as a reliable emergency fallback. The correct answer acknowledges that RTH is subject to GNSS, compass, battery, and obstacle limitations — it is not a guaranteed safety system.
Altitude ceiling and RTH: Students sometimes assume any RTH altitude the manufacturer allows is legal. You as PIC must ensure RTH altitude does not violate the 400-foot AGL ceiling or any applicable airspace authorization altitude limit.
PIC responsibility cannot be automated away: A distractor answer may suggest that activating RTH transfers responsibility for the aircraft's path to the manufacturer or the flight controller. Under 14 CFR 107.19, responsibility remains with the remote PIC at all times.
Home-point accuracy assumptions: Test questions may describe a scenario where the aircraft lands far from the intended point after RTH. The correct diagnosis is often an imprecise home-point lock at startup, not a malfunction in the strict sense.
Confusing automatic RTH trigger with deliberate PIC decision-making: The automatic low-battery or lost-link RTH is a flight controller default, not a substitute for pre-flight range and battery planning. The PIC is responsible for planning flights so that these automatic triggers, if they fire, result in safe outcomes.

Return-to-Home is a genuinely useful feature when understood and configured correctly, and when the remote pilot treats it as one tool among many rather than a universal safety guarantee. Confirm your home-point lock before every flight, set a legally compliant and obstacle-clearing RTH altitude, plan for battery margins that account for RTH in the worst expected wind conditions, and maintain the situational awareness and VLOS that the regulations require. RTH supplements good airmanship — it does not replace it.