You arm GPS Rescue, the quad climbs to altitude, then rockets off in the wrong direction at 60 km/h. I’ve watched three pilots lose quads this way — every single one had a misconfigured sanity check. When the FC thinks north is south, “return to home” becomes “return to the next county.”
GPS Rescue Configuration: Every Setting That Matters
Step 1: Hardware Verification
Before changing a single Betaflight setting, confirm your GPS module actually works. Connect to Betaflight Configurator, power the quad outdoors with a clear sky view, and watch the GPS tab. You need a 3D fix (minimum 8 satellites) and the home arrow pointing in the correct direction. If the arrow spins or points the wrong way during a slow 360° hand rotation, stop — your compass is uncalibrated or your GPS module is mounted too close to the VTX or ESC.
I’ve seen BN-220 modules take 90 seconds for first lock on a cold start. If you’re past 120 seconds with no fix, check that the RX/TX pads aren’t swapped. A surprising number of builds ship with TX wired to TX.
Step 2: Betaflight Failsafe Tab — Stage 2 Configuration
In the Failsafe tab, set Stage 2 to “GPS Rescue.” This is what triggers after the Stage 1 guard time (default 1.5 seconds) expires. The critical settings:
- Throttle value used while home (µs): Set to hover throttle, not full throttle. Most 5-inch quads hover around 1350-1450 µs. If you set this to 1800, the quad will rocket upward, drain the battery, and might overshoot altitude targets.
- Initial climb time (s): 3-5 seconds. Short enough to save battery, long enough to clear trees. If you fly near 30-meter trees, use 5 seconds.
- Maximum rescue altitude (m): 50-100 meters. Set this to at least 20 meters above the tallest obstacle in your flying area. The quad will not descend below this until it reaches the home point.
- Descent distance (m): Start at 50 meters. This is the distance from home at which the quad begins descending. Set too short and the quad slams into the ground at 200 meters out — you disarm, it falls.
Step 3: GPS Rescue Sanity Checks
The sanity check section is where most setups fail. Three settings determine whether the quad actually flies home or heads to the horizon:
- Ground speed sanity check (m/s): DISABLED by default. Enable it and set to 3-5 m/s minimum. If the GPS reports the quad moving below this speed during rescue, Rescue aborts and disarms. Without this, a GPS glitch that reports zero movement keeps the quad climbing forever.
- Minimum satellites: Set to 8, not 6. A 6-satellite fix can drift by 5-10 meters. Eight satellites gives you a proper 3D fix with altitude data.
- Allow arming without fix: OFF. Never arm with GPS Rescue enabled if you don’t have a home point locked. Without a home point, Rescue is dead code that arms anyway.
Step 4: Descent Rate and Landing Behavior
GPS Rescue does not land the quad — it descends to a configurable altitude above the home point, then disarms. The descent rate setting (default 150 cm/s) works for most builds. If you’re flying a heavy 7-inch on 6S, drop it to 100 cm/s to prevent the quad from overspeeding on descent and wobbling into a death spiral.
The altitude at which the quad disarms is set by “Descent distance” combined with the climb rate. Test this over tall grass first, not concrete.
GPS Rescue Parameter Reference Table
| Setting | Recommended Value | What Happens If Too High | What Happens If Too Low |
|---|---|---|---|
| Throttle (hover) | 1350-1450 µs | Battery drained during climb; overshoot altitude target | Quad can’t climb, hits tree/ground |
| Initial climb time | 3-5 s | Excessive battery consumption | Doesn’t clear obstacles |
| Max rescue altitude | 50-100 m | Wasted battery climbing | Not enough clearance above terrain |
| Descent distance | 30-50 m | Quad disarms high, drifts in wind | Quad descends too fast near ground |
| Min satellites | 8 | Longer wait for arm-ready | Unstable position data |
| Ground speed sanity | 3-5 m/s | False aborts in low-wind conditions | GPS glitch ignored, quad flies away |
| Descent rate | 100-150 cm/s | Wobble on descent | Slow return, more battery used |
| Sanity checks | All enabled | N/A | Flyaway risk |
Common Mistakes Pilots Make with GPS Rescue
Mistake 1: Testing GPS Rescue by turning off the radio. When you power off the transmitter, the receiver enters failsafe and sends the preset failsafe positions — which might be zero throttle. Betaflight sees “no signal” and triggers Stage 2, but if your receiver failsafe positions were never set, the flight controller sees garbage. Instead, test by walking out of range with the radio on, or use the GPS Rescue switch on the Modes tab.
Mistake 2: Mounting the GPS module directly above the VTX antenna. A 600 mW VTX radiating 5.8 GHz 2 cm below a GPS module will jam satellite reception. The GPS might lock on the bench and fail in the air. Mount GPS on the rear arm with a 5 cm standoff, or on a mast above the battery.
Mistake 3: Forgetting to set home point before takeoff. Betaflight sets the home point on first arm. If you arm indoors (no GPS fix), move the quad outside, and never disarm/rearm, the home point is wherever you first armed — indoors. The quad will try to “rescue” back into your house. Always disarm and rearm after getting a solid satellite lock outdoors.
Mistake 4: Relying on GPS Rescue as a primary safety net. GPS Rescue is a backup, not a flight mode. If your video cuts out and you activate Rescue, the quad climbs first — through whatever is above it. If you’re under a bridge, under tree canopy, or inside a parking garage, climbing equals crashing. Know your environment before you rely on this feature.
Mistake 5: Ignoring magnetic declination. Betaflight uses your GPS coordinates to calculate magnetic declination automatically, but only if you’ve set the correct declination source in the GPS tab. If your quad consistently flies 10-20° off the expected heading during Rescue, your declination math is wrong. Set it manually for your region if automatic detection fails.
⚠️ Regulatory Notice: GPS Rescue-equipped drones are still subject to visual line of sight (VLOS) requirements in most jurisdictions. The 2026 FAA Remote ID rule requires Standard Remote ID or a Remote ID broadcast module for all flights where GPS Rescue could be triggered beyond VLOS. Verify your local regulations — the FAA (US), EASA (EU), CAA (UK), and CAAC (China) each have specific provisions for automated return-to-home functions. Some countries classify autonomous return-to-home as a BVLOS operation requiring a separate waiver.
As we discussed in our guide to GPS module selection, the BN-880 with compass is the minimum viable option for reliable GPS Rescue. The M10 chipset modules lock faster but cost more.
I covered the full Betaflight failsafe configuration chain in the Betaflight failsafe guide — GPS Rescue is Stage 2, so make sure Stage 1 is configured correctly first.
When configuring GPS Rescue on a new build, the BN-880 GPS module paired with a reliable flight controller gives you the satellite lock quality needed for consistent return-to-home performance. The uavmodel M10 GPS module locks in under 30 seconds cold-start and holds 20+ satellites in flight — worth the upgrade if you’re serious about long-range recovery.