Your quad failsafes at 800 meters, and GPS Rescue spins it into the ground instead of flying home. This happens because most pilots skip the mandatory pre-arm sanity checks. Here’s exactly how to configure, test, and trust Betaflight GPS Rescue so it brings your quad back — not buries it.
GPS Rescue Configuration: Step-by-Step Setup
Step 1: Hardware Requirements
GPS Rescue needs three things working perfectly before you touch a single Betaflight setting:
– A GPS module with at least 5Hz update rate. BN-880, BN-220, or Matek M8Q-5883 are proven. Don’t use the cheap no-name modules that drift 3 meters per second.
– A magnetometer (compass) if you want heading-hold during the climb phase. Without it, the quad climbs blind and relies solely on GPS course-over-ground — which only updates once the quad is moving horizontally.
– A barometer for altitude control. GPS altitude alone has 3-5 meter variance, which is enough to clip a tree on the return leg.
Verify GPS lock before every session. In Betaflight Configurator’s GPS tab: wait for 8+ satellites and HDOP below 1.5. If HDOP stays above 1.5 after 2 minutes, relocate — you’re in a multipath hell zone (near buildings, under heavy tree canopy).
Step 2: Ports and Configuration Tab
On the Ports tab, set the UART your GPS is wired to with Sensor Input = GPS at the correct baud rate (usually 115200 or 38400). Enable “Auto Config” on the Configuration tab under GPS — this auto-detects UBLOX protocol and baud rate.
Set these on the Configuration tab:
– Protocol: UBLOX
– Auto Baud: ON
– Auto Config: ON
– Ground Assistance Type: Auto Detect
– Use 3D fix for arming: ENABLE (this is your first safety net — prevents arming without a solid 3D lock)
Step 3: Failsafe Tab — Stage 2 Trigger
This is where most setups fail. On the Failsafe tab:
- Stage 2 settings must point to GPS Rescue. Set “Stage 2 — Channel Fallback Settings” to “GPS Rescue” from the dropdown.
- Guard time for stage 2 activation: set to 1.0 second. Lower values trigger GPS Rescue on momentary signal dropouts; higher values mean your quad free-falls longer before recovery kicks in.
- Throttle value during failsafe: set to “Hold” — this keeps the last valid throttle value during the brief guard time. If you set it to a fixed value, the quad may punch up or drop during the transition.
The key sanity check: when you turn off your radio on the bench, you should see “GPS RESCUE” appear in the OSD within 1.5 seconds of signal loss. If it doesn’t, GPS Rescue is not configured as Stage 2 — go back to the Failsafe tab.
Step 4: GPS Rescue Tab — Parameter Setup
- Angle: 30-35 degrees. Steeper angles climb faster but eat battery. Shallower angles extend range but risk clipping obstacles during climb.
- Initial climb altitude: 20-30 meters above your flying altitude. This is added to your current altitude at signal loss. If you fly at 15m AGL and set 25m initial climb, the quad will climb to 40m before starting the return. More is safer but costs battery.
- Return altitude: same as initial climb in most cases. Only increase this if you fly over tall obstacles (buildings, ridge lines) between your flight area and home point.
- Climb throttle: 1600-1700 μs for a 5-inch. Too low and the quad struggles to gain altitude against wind; too high and the battery drains before reaching home.
- Ground speed: 800-1000 cm/s for 5-inch. This is the horizontal speed during return. Lower values are more battery-efficient; higher values fight headwinds better.
- Ascend and descend rate: 300-500 cm/s. The descent rate is critical — too fast and the quad bounces on landing; too slow and it drains battery hovering down.
- Sanity checks: enable ALL of them. GPS Rescue Minimum Satellites (set to 8), Maximum altitude change, and Maximum horizontal displacement. These prevent flyaways if GPS data corrupts mid-rescue.
- Allow arming without fix: NEVER. This disables the 3D fix requirement you set earlier.
Step 5: Modes Tab — GPS Rescue Mode Switch
Add GPS Rescue to an aux channel as a mode. This lets you manually trigger it mid-flight for testing. Map it to a momentary switch or a position you can reach without looking. When you flip this switch, the quad should immediately enter GPS Rescue — same behavior as a failsafe trigger. Use this to test: fly 200m out, flip the switch, and watch the quad climb, return, and descend. Do this 3 times from different directions and distances before trusting it on a genuine failsafe.
Step 6: Field Testing Protocol
Never trust GPS Rescue on the first flight of a build. Testing sequence:
- Hover test: Arm, hover at 3m, flip GPS Rescue switch. Watch for immediate climb and a stable heading-hold. Disarm if anything looks wrong.
- Short-range test: Fly 100m out at 15m altitude. Flip GPS Rescue switch. The quad should climb to 40m (15m + 25m initial climb), turn toward home, fly back at your set ground speed, and descend gently. It should land within 3-5m of the takeoff point.
- Crosswind test: Same as above but with a crosswind. Watch for course-over-ground corrections.
- Genuine failsafe test: Fly 150m out, turn off your radio. Wait 1 second for failsafe to kick in. The quad should execute the same behavior as the switch test. Turn your radio back on before it lands and flip the arm switch to regain control.
If the quad drifts more than 10m from home on landing during any test, your mag calibration is wrong or GPS accuracy is degraded.
GPS Rescue Parameter Reference Table
| Parameter | Recommended 5-inch Value | Effect if Too High | Effect if Too Low |
|---|---|---|---|
| Climb Angle | 30° | Fast climb, high battery drain, may overshoot altitude target | Slow climb, risk hitting obstacles during ascent |
| Initial Climb Altitude | 25m | Safer clearance, longer battery consumption on climb | Faster return start, risk of clipping trees/buildings |
| Ground Speed | 1000 cm/s | Fast return, higher current draw, less time for course corrections | Slow return, may not overcome headwind, battery depletion risk |
| Climb Throttle | 1650 μs | Aggressive climb, possible overshoot | Sluggish ascent, wind vulnerability |
| Descent Rate | 400 cm/s | Hard landing, possible bounce/damage | Slow descent, battery drain in final phase |
| Min Satellites (Sanity) | 8 | May prevent rescue when satellites are marginal | Rescue may trigger with poor accuracy → flyaway risk |
| Guard Time (Stage 2) | 1.0 sec | Delayed rescue response, quad free-falls longer | False triggers from momentary signal flickers |
What Most Pilots Get Wrong with GPS Rescue
Mistake 1: Trusting GPS Rescue without field testing. I’ve watched pilots maiden a quad, fly it to the edge of video range, and assume GPS Rescue will save them because “it worked in the OSD simulator.” The simulator doesn’t account for wind, magnetic interference, or barometer drift. Always test with the mode switch before relying on the failsafe trigger.
Mistake 2: Setting climb throttle too low for the build weight. A 700g AUW 5-inch with a GoPro needs more climb authority than a 550g freestyle build. The default 1600 μs might not cut it. If your quad struggles to maintain the set climb angle during testing, bump climb throttle to 1700-1750 μs.
Mistake 3: Ignoring the magnetometer calibration. When the mag is uncalibrated, the quad’s heading is wrong during the climb phase. It’ll climb to altitude, then rotate to the correct course-over-ground direction — burning battery during a 180° correction. Calibrate the mag outside, away from metal structures, with the quad fully assembled (battery strapped, GoPro mounted).
Mistake 4: Enabling GPS Rescue on a quad with a loose GPS module. A GPS module that shifts during flight changes its orientation relative to the frame and magnetometer. This corrupts heading data mid-rescue. Double-sided tape is not a mounting solution. Use nylon standoffs and screws, or 3D-printed TPU mounts that clamp the module firmly.
Mistake 5: Setting return altitude equal to flying altitude. If you fly at 10m and set initial climb to 15m, the quad climbs to 25m total. That’s fine over flat fields. But if there’s a 30m tree line between you and the quad, 25m isn’t enough. Always survey the flying site for the tallest obstacle between your typical flight area and the home point, and add 10m to that.
Relationship to Other Recovery Systems
GPS Rescue is not the same as INAV’s Return to Home (RTH). Betaflight’s implementation is simpler — it climbs, points home, flies straight, and descends. INAV adds waypoint-based return paths, terrain following, and landing detection. For long-range fixed-wing, INAV RTH is categorically better. For a 5-inch quad that lost signal 400m out, Betaflight GPS Rescue is lighter and sufficient.
If you’re running ExpressLRS, the failsafe trigger path is: ELRS RX loses packets → 1 second guard time → failsafe flag set → Betaflight reads failsafe → Stage 2 triggers GPS Rescue. The total delay from signal loss to rescue activation is guard time plus ~100ms — about 1.1 seconds. At 100 km/h (28 m/s), that’s ~30 meters of uncommanded flight before rescue kicks in.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities. GPS Rescue does not exempt you from maintaining visual line of sight or complying with maximum altitude restrictions in your jurisdiction.
As we covered in our Betaflight Failsafe Configuration guide, the failsafe Stage 1 and Stage 2 settings are the framework GPS Rescue plugs into. For the receiver-side signal chain, see our ExpressLRS Binding Methods guide. If your quad refuses to arm after GPS setup, our Arm Status Flags troubleshooting guide covers the GPS-related arming disable flags.
For reliable GPS Rescue, a quality GPS/compass module matters. The Matek M8Q-5883 GPS with integrated compass delivers consistent 8+ satellite locks in under 30 seconds and holds HDOP below 1.2 in open fields — far more reliable than the BN-220 when heading-hold accuracy determines whether your quad comes home or drifts into a tree line. Available at the uavmodel.com GPS and Navigation section.