Betaflight GPS Rescue Mode: Complete Setup and Testing Guide
GPS Rescue Mode in Betaflight is one of the most valuable safety features available to FPV pilots. When signal is lost or you trigger it manually, the drone autonomously climbs, turns toward home, and flies back — potentially saving hundreds of dollars in equipment. However, a poorly configured GPS Rescue can turn a minor failsafe into a flyaway or a crash. This guide walks through every step of hardware setup, software configuration, and safe testing so your rescue mode works when it matters most.
GPS Module Selection and Wiring
A quality GPS module is the foundation of reliable rescue. The BN-220, BN-880, and Matek M8Q-5883 are popular choices, all supporting GPS and GLONASS constellations for faster satellite locks. For Betaflight 4.3 and later, consider modules with the M10 chipset (like the HGLRC M100 or Flywoo GOKU M10) — they acquire satellites significantly faster and maintain lock better in challenging environments.
Wiring is straightforward: connect the GPS module’s TX to a free UART’s RX pad, and RX to TX. Power the module with 5V and ground from your flight controller. If your module includes a compass (magnetometer), connect SDA and SCL to the corresponding I2C pads — typically on the same connector as the GPS UART. Note that many modern builds skip the compass entirely, as Betaflight’s GPS Rescue does not require it, and magnetometers on miniquads are notoriously difficult to calibrate reliably due to motor and ESC interference.
Mount the GPS module with the ceramic patch antenna facing skyward, as far as possible from the VTX antenna and carbon fiber frame. Carbon fiber blocks GPS signals, so avoid mounting directly under frame plates. A 3D-printed TPU mount on a rear arm or top plate works well. Keep the module at least 3-5 cm from the VTX antenna to minimize RF interference on the GPS L1 frequency (1575.42 MHz).
Betaflight Configuration: Ports and GPS Tab
In the Betaflight Configurator, navigate to the Ports tab and enable “GPS” under Sensor Input for the UART connected to your GPS module. Set the baud rate to 115200 for most modules, or 9600 if using an older unit. Save and reboot. Next, go to the GPS tab in Configuration and enable GPS for navigation. Set the protocol to UBLOX for Ublox-based chipsets (the vast majority) or NMEA for generic modules. Select auto-baud and auto-config if your module supports it — most modern Betaflight builds handle this automatically.
After saving, take the drone outside with a clear sky view. Within 30-90 seconds on first power-up (cold start), the GPS icon should turn solid in the Betaflight top bar, and you should see latitude, longitude, and satellite count. A warm start after recent use should lock in under 15 seconds. If you see 0 satellites after 2 minutes, check wiring, UART assignment, and baud rate.
Failsafe Tab Configuration
The Failsafe tab is where GPS Rescue behavior is configured. Under Stage 1 — Failsafe Procedure, select “GPS Rescue” from the dropdown. The guard time determines how long Betaflight waits after signal loss before initiating rescue; the default of 1.0 second is reasonable, preventing false triggers from momentary signal drops.
Stage 1 and Stage 2 Behavior
GPS Rescue operates in two distinct stages. Stage 1 begins immediately when rescue triggers: the drone stops any forward motion, levels itself, and climbs to the configured altitude. During this phase, it does not turn toward home yet. Stage 2 activates once the drone completes its climb and minimum satellite requirements are met — the drone then yaws toward the home point and begins flying back at the configured ground speed.
Critical Stage 1 settings include the climb throttle percentage and maximum climb rate. Set climb throttle to 1600-1700 in the throttle value field (roughly 65-70% throttle for most builds). This must be high enough to climb with authority but not so aggressive that it drains the battery before reaching altitude. The maximum climb rate of 500-700 cm/s is reasonable for most builds. For minimum satellites, the default of 8 is sensible — fewer risks inaccurate position data. Set the sanity check type to “Maximum Altitude” to prevent flyaway if altitude data becomes unreliable.
Return Altitude and Ground Speed
The return home altitude is the single most important setting — and the most common cause of rescue failures. Set this higher than any obstacle in your flying area. If you fly around trees and buildings, set it to at least 50-80 meters above your takeoff altitude. In mountainous terrain or urban environments, 100-150 meters may be necessary. The drone will climb to this altitude (Stage 1) before beginning the return journey (Stage 2), even if it was below your set altitude when rescue triggered.
Ground speed determines how fast the drone travels during Stage 2 return. 8-12 m/s is a safe range for most 5-inch builds — fast enough to make progress against wind, slow enough to maintain stability. Too slow and a headwind may prevent the drone from reaching home; too fast and the flight controller may struggle with oscillation at high tilt angles. If your rescue tests show wobbling during the return leg, reduce ground speed by 2-3 m/s.
Sanity Checks and Safety Features
Betaflight includes several sanity checks to prevent a GPS Rescue from turning catastrophic. Maximum rescue altitude prevents the drone from climbing indefinitely if a barometer or GPS glitch occurs — set this to 20-30 meters above your return altitude. If altitude exceeds this threshold, rescue disengages and the drone drops (controlled by the Stage 2 failsafe setting, typically “Drop”). The minimum home distance check ignores rescue if the drone is within 50 meters of home — in that case it simply drops, as a close-range rescue climb and return would be unnecessary and potentially dangerous.
An often-overlooked setting is the failsafe delay for GPS Rescue. The default of 1 second works for most scenarios, but if you fly behind mountains or large structures where signal can briefly drop, consider 1.5-2.0 seconds to reduce false triggers. However, longer delays mean the drone flies uncontrolled for longer before rescue engages — balance this carefully.
How to Test GPS Rescue Safely
Never test GPS Rescue for the first time over water, concrete, or people. Find a large open field with soft grass and a clear sky view. Follow this graduated testing procedure:
- Stationary lock test: Arm the drone with props on, holding it firmly. Confirm a solid 3D fix with 12+ satellites. Verify the home point is set (distance shows 0m in OSD).
- Low-altitude manual trigger: Fly 50 meters out at 15 meters altitude. Switch to GPS Rescue mode on your radio. The drone should climb and return. Be ready to override by switching back to Angle or Acro mode. If anything looks wrong, disarm immediately.
- Higher and farther: Gradually increase distance to 200-300 meters and altitude to 30 meters. Trigger rescue and observe behavior. The drone should climb to return altitude, turn to home, and fly back smoothly.
- Full failsafe test: Fly 200 meters out. Turn off your radio (this simulates a genuine signal loss). After the guard time, rescue should engage automatically. Turn the radio back on to regain control before the drone lands.
- Wind test: Test in moderate wind conditions (10-15 km/h). Ensure the drone can make headway against the wind during return. If it cannot, increase ground speed.
Always configure your OSD to display GPS satellite count, GPS rescue status, home direction arrow, and distance to home. These elements provide situational awareness during testing and are invaluable if rescue triggers unexpectedly in normal flight. After successful testing, GPS Rescue becomes a reliable safety net — but never rely on it as a substitute for good flying judgment and solid radio link quality.