GPS Rescue is Betaflight’s autonomous return-to-home feature. When your radio link drops, the quad climbs to a safe altitude, flies back to the home point, descends, and disarms. Or it’s supposed to. When I first enabled it in 2019, my quad climbed to altitude and then flew directly away from me at 60kph because the magnetic declination was set to zero. GPS Rescue done wrong is worse than no GPS Rescue at all — it actively flies your quad into the distance instead of bringing it home. Here’s the setup that actually works.
How GPS Rescue Actually Works (Not What the Marketing Says)
When GPS Rescue triggers — either from a failsafe (Stage 2) or a manual switch — the flight controller does three things in sequence:
- Climb phase: The quad levels out and climbs to the configured altitude at the configured climb rate. It maintains heading (doesn’t turn yet).
- Return phase: The quad yaws toward the home point and flies there at the configured ground speed, maintaining altitude.
- Descent phase: When the quad reaches home position, it descends at the configured descent rate. At a configurable altitude above ground, it either disarms (drop) or attempts a controlled landing (land).
The whole sequence depends on three sensor systems: GPS for position, barometer for altitude (more reliable than GPS altitude), and compass for heading. If any of these gives bad data, the rescue becomes a flyaway.
Step 1: Hardware Requirements
You need: a GPS module with a working compass (BN-880, BN-220 w/ external compass, or Matek M8Q-5883), a barometer (most modern FCs include one — BMP280 or DPS310), and enough satellites for a solid 3D fix (minimum 8, preferably 12+).
The compass is the most failure-prone component. If your FC includes an onboard magnetometer (common on Matek and some Diatone boards), use that instead of the GPS module’s compass. Two compasses fighting each other is worse than one — disable the one you’re not using in the Configuration tab.
Step 2: GPS Configuration (Ports and Configuration Tabs)
In the Ports tab, assign the UART connected to your GPS module to “Sensor Input” → GPS, with the correct baud rate (9600 for older modules, 115200 for modern M10 modules). Enable “Auto Config” to let Betaflight negotiate the protocol (UBLOX is standard).
In the Configuration tab, enable GPS under “Other Features.” Set the protocol to UBLOX. Enable “Auto Baud” if your module supports it.
Go to the GPS tab and verify you’re getting a 3D fix with at least 8 satellites indoors (by a window) or 12+ outdoors. Altitude and ground speed should update in real time.
Step 3: Magnetic Declination (The Setting That Caused My 2019 Flyaway)
Magnetic declination is the angle between true north (what GPS reports) and magnetic north (what your compass reads). This angle varies by location — it’s about +7° in New York, -2° in London, and +14° in parts of Australia.
In the CLI:
set mag_declination = [your value]
Find your value at ngdc.noaa.gov/geomag/calculators/magcalc.shtml. If you skip this or set it to zero, the quad’s computed heading will be off by the declination amount, and the return-to-home bearing will be wrong by that same angle. At 500 meters, a 10° heading error is an 87-meter miss.
Step 4: GPS Rescue Configuration (Failsafe Tab)
In the Failsafe tab, under Stage 2 — GPS Rescue:
- Angle: 35-45 degrees. How aggressively the quad tilts during return. Higher = faster return but more altitude loss. On a 5-inch, 35° returns at about 45kph. On a 7-inch, 30° is safer for altitude hold.
- Initial climb altitude: 30-50 meters. Climb this high above the trigger altitude before turning toward home. Higher = more battery consumed but more obstacle clearance. If you fly in forested areas, set 50m minimum.
- Descend distance: 100-200 meters. How far from home the quad starts descending. Shorter = more battery saved but less time to spot the quad visually.
- Ground speed: 1000-1500 cm/s (10-15 m/s, 36-54 kph). Return speed in still air. Set conservatively — the quad holds this ground speed, which means it uses more throttle into a headwind.
- Throttle min/max: 1200-1900. The throttle range the rescue logic is allowed to use. Min 1200 prevents the motors from stopping during descent. Max 1900 prevents the quad from rocketing upward and burning battery.
- Min satellites: 8 minimum, I set mine to 10. If the GPS lock drops below this, rescue aborts and the quad does whatever Stage 1 is configured for (usually drop).
Step 5: Sanity Check Before Every Flight
GPS Rescue should be a switch-activated test on every pre-flight. Arm, hover at 5 meters, flip the GPS Rescue switch. The quad should immediately level, climb to the rescue altitude, and hold position. If it does anything else — yaws randomly, climbs without stopping, flies sideways — land immediately and diagnose.
GPS Module Comparison Table
| GPS Module | Chipset | Compass | Update Rate | Time to First Fix (cold) | Weight |
|---|---|---|---|---|---|
| Matek M10Q-5883 | M10 | QMC5883 | 10Hz | 26s typical | 9g |
| BN-880 | M8N | HMC5883 | 10Hz | 30s typical | 18g |
| BN-220 | M8N | None (GPS only) | 10Hz | 30s typical | 5g |
| TBS GPS M10 | M10 | Yes | 10Hz | 24s typical | 12g |
| HGLRC M100 Mini | M10 | Yes | 10Hz | 22s typical | 5g |
Common Mistakes & What Most Pilots Get Wrong
Mistake 1: Testing GPS Rescue at the field without verifying mag_declination first. The most common cause of “GPS Rescue flew the wrong way.” On the bench, look at the Setup tab’s heading indicator. Rotate the quad 360° slowly. The heading should change smoothly with no jumps or reversals. If it’s jumpy or shows the wrong direction when pointing at a known landmark, the compass needs calibration or the declination is wrong.
Mistake 2: Setting climb throttle too low for heavy builds. The default throttle settings assume a 5-inch quad under 700g. A 7-inch long-range quad with a GoPro and a 3300mAh pack weighs 1.2kg. At default climb throttle, it’ll struggle to gain altitude against any wind. Increase throttle max to 2000 and throttle min to 1250 for heavy builds.
Mistake 3: Not adjusting minimum satellites for the environment. In open sky, 8 satellites is fine. In a canyon or dense tree cover, 8 satellites can drop to 6 before the quad finishes the climb phase. Set the minimum to 10 and the sanity check type to “RESCUE_SANITY_FS_ONLY” if you fly in challenging GPS environments.
Mistake 4: Forgetting that GPS Rescue uses barometer altitude, not GPS altitude. If your barometer isn’t foam-covered (to block wind and light), the climb altitude will be erratic and the quad may climb to the moon or descend into the trees. Cover the barometer chip with open-cell foam — the kind that comes with most flight controller boxes.
Mistake 5: Trusting GPS Rescue as a substitute for a solid radio link. GPS Rescue is a safety net, not a flight mode. If you’re triggering it regularly, fix your receiver setup. Every GPS Rescue activation is a single point of failure away from a flyaway. The compass can fail, the GPS can lose lock, the barometer can drift. It’s a last resort, and it should be treated as such.
⚠️ Regulatory Notice: GPS Rescue may cause your drone to fly autonomously beyond visual line of sight (BVLOS). In many jurisdictions — including the US under FAA Part 107 and recreational rules — BVLOS flight without a waiver is prohibited. GPS Rescue should be configured as an emergency failsafe system, not as a routine autonomous flight mode. Verify the latest 2026 regulations from the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities before relying on GPS Rescue in flight. Some regions require a Remote ID module that continues transmitting during autonomous return.
GPS Rescue depends on a solid failsafe configuration — the Stage 1/Stage 2 triggers are covered in depth in our Betaflight failsafe guide. And before you trust GPS Rescue at range, make sure your ELRS binding and telemetry are rock-solid — the best GPS Rescue is the one that never triggers because your link never drops.
For long-range builds where GPS Rescue is a critical safety system, the Matek M10Q-5883 GPS module has the fastest satellite acquisition of any module I’ve tested — it locks 12+ satellites in 15 seconds cold and holds 20+ in flight. That satellite count margin means even when you fly into a valley where the GPS constellation is partially blocked, you still have enough satellites for the rescue logic to work.