GPS Rescue Setup Guide for Betaflight and INAV: Failsafe Configuration, Testing, and Real-World Tips
GPS Rescue is the closest thing FPV has to a parachute. When your video link drops, your radio failsafes, or you simply lose orientation at the far end of a long range run, a properly configured GPS rescue can autonomously fly your quad back to you — climbing to a safe altitude, turning toward home, and descending to a recoverable position. But GPS Rescue only works if you set it up correctly and test it thoroughly. A misconfigured rescue is worse than no rescue at all. This guide covers every setting, every test procedure, and every hard-learned lesson for getting GPS Rescue right on both Betaflight and INAV.
Minimum Hardware Requirements
Before you touch a single setting, you need the right hardware:
- GPS module: At minimum, a BN-220 or similar with functional satellite lock. Better: a BN-880Q (with compass) or Matek M10Q-5883 (modern M10 chipset, locks in under 30 seconds). Must output NMEA or UBLOX protocol at 115200 baud.
- Barometer (strongly recommended): GPS altitude is notoriously inaccurate (±5-10m at best). A BMP280 or DPS310 barometer on your flight controller gives precise altitude data. If your FC doesn’t have a barometer, GPS altitude works but increases the risk of the quad descending into terrain or obstacles.
- Magnetometer (optional for Betaflight, recommended for INAV): A compass helps determine heading when GPS speed is low. Without one, the quad estimates heading from GPS course-over-ground, which is inaccurate below ~3m/s. In Betaflight, GPS Rescue can work compass-free. In INAV, a compass is nearly essential for reliable Return-to-Home.
Betaflight GPS Rescue: Step-by-Step Configuration
Betaflight’s GPS Rescue is a simplified, robust implementation designed to get your quad home without complex waypoint navigation. It replaces the older “GPS Return to Home” feature and is available in Betaflight 4.1+ (significantly improved in 4.3+).
Step 1: Enable GPS in Betaflight
- Connect your GPS module to a free UART on your flight controller (TX to RX, RX to TX).
- In Betaflight Configurator, go to Ports tab. Find the UART your GPS is connected to. Under “Sensor Input,” select GPS and set the baud rate to 115200 (or 9600 for older modules). Save and reboot.
- Go to the Configuration tab, enable GPS under “System Configuration,” select UBLOX protocol, and enable Auto Config and Auto Baud. Save and reboot.
- On the GPS tab (top of Configurator), verify you’re getting satellite count, latitude, longitude, and altitude. Go outside if you’re not getting a lock — GPS doesn’t work well indoors.
Step 2: Configure the Rescue Mode
- Go to the Failsafe tab.
- Under “Stage 2 – Failsafe Procedure,” select GPS Rescue from the dropdown.
- Set the key parameters (see table below).
- In the Modes tab, assign a switch to GPS RESCUE mode. This lets you manually trigger rescue for testing — essential.
| Setting | Recommended Value | Explanation |
|---|---|---|
| Angle | 35-45° | How aggressively the quad tilts to fly home. 35° is safe and efficient. |
| Initial Climb | 30-50m | Altitude the quad climbs to before returning. Set this HIGHER than the tallest object in your flying area. |
| Descent Distance | 50-100m | How far from home the quad begins its descent. Too close and it’ll land on your head. |
| Ground Speed | 15-20 m/s | Target speed for the return flight. 15 m/s (54 km/h) is a safe default. |
| Throttle Min/Max | 1200 / 1800 | Throttle limits during rescue. Don’t set max too high or the quad will rocket upward. |
| Min Satellites | 8 | Rescue won’t arm unless at least 8 satellites are locked. Don’t set below 6. |
| Allow Arming Without Fix | OFF | Prevents arming without a GPS 3D fix. Turn this ON for bench testing only. |
| Sanity Checks | ON | Aborts rescue if GPS data looks invalid (impossible jumps, zero satellites, etc.). Leave this ON. |
| Use Mag | ON if you have a compass | Enable if you have a magnetometer. Otherwise leave OFF. |
INAV Return-to-Home: A Different Philosophy
INAV’s RTH is more sophisticated than Betaflight’s GPS Rescue but requires more careful setup. INAV uses full navigation — it knows its position, its heading (with compass), and can execute multi-stage autonomous flight.
Key INAV RTH Settings
- nav_rth_alt_mode: Set to “AT_LEAST” — the quad will climb to at least the RTH altitude, or stay at its current altitude if higher.
- nav_rth_altitude: Set in centimeters! 5000 = 50 meters. Set this carefully — it’s the altitude the quad maintains during the return journey.
- nav_rth_climb_first: ON. The quad climbs to RTH altitude before turning toward home. Essential for clearing obstacles on the return path.
- nav_rth_home_altitude: Altitude to descend to when reaching home. Usually set to 1000-2000 (10-20m) so you can spot the quad visually.
- nav_rth_tail_first: OFF for multirotors (they fly nose-first toward home). ON for fixed-wing (they turn and fly back).
- nav_fw_launch_land: ON if you want INAV to auto-land at the home point. This is risky — test extensively in an open field first.
INAV also requires you to set a home point. By default, INAV sets the home position on first GPS 3D fix after powering up. You can see the home point distance on your OSD. Ensure the home arrow points toward you before taking off — if the compass is miscalibrated, RTH will fly the wrong direction.
Testing GPS Rescue: The Non-Negotiable Part
I cannot overstate this: you must test GPS Rescue before you ever need it. A rescue you haven’t tested is just a firmware setting — you have no idea if it actually works. Follow this progression:
Phase 1: Bench Test
- With props off, arm the quad briefly to trigger the home point.
- Trigger GPS Rescue via your assigned switch.
- Verify the OSD shows “GPS RESCUE” active. Check that motors respond (idle or spin up slightly).
- This confirms the mode activates and the FC recognizes it.
Phase 2: Hover Test (props on, 5m altitude, open field)
- Fly to 5-10m altitude, 10m away from yourself.
- Trigger GPS Rescue via switch.
- The quad should climb (if set), then begin moving toward the home point.
- Be ready to take over immediately. The moment you move any stick, GPS Rescue disengages (in Betaflight; INAV may require mode switch toggle).
- If the quad flies the wrong direction, twitches, or descends dangerously — disarm or take over. Debug on the ground.
Phase 3: Distance Test (100m out, 50m altitude)
- Fly out 100-200m at 50m altitude. Face the quad away from you.
- Trigger rescue and observe: does it climb to the set altitude? Does it turn toward home? Is it flying a straight line?
- The quad should fly back to within ~10-20m of the home point and then descend slowly or loiter (depending on your settings).
Phase 4: True Failsafe Test (the scary one)
- Fly out 200-300m at safe altitude.
- Turn off your radio transmitter.
- The quad should detect signal loss, enter failsafe stage 2, and execute GPS Rescue automatically.
- After 10-15 seconds, turn your radio back on. The quad should return control to you.
- Do not do this on your first test flight. Only after Phases 1-3 have succeeded flawlessly.
Common GPS Rescue Failures and Fixes
| Symptom | Cause | Fix |
|---|---|---|
| Quad flies wrong direction | Compass not calibrated (INAV), home point set incorrectly, or GPS heading error | Recalibrate compass away from metal, verify home arrow on OSD before takeoff |
| Rescue doesn’t engage on failsafe | Failsafe stage 2 not set to GPS Rescue | Check Failsafe tab in Betaflight Configurator |
| Quad climbs uncontrollably | Barometer not working, GPS altitude drift, or throttle max too high | Verify barometer in Sensors tab, reduce Throttle Max to 1750 |
| Quad descends into ground | Descent Distance too short, barometer error, or landing logic buggy | Increase Descent Distance to 100m+, test barometer accuracy |
| “RESCUE N/A” or “NO GPS” in OSD | Insufficient satellites, no 3D fix, or GPS not properly configured | Wait for 8+ satellites and 3D fix. Check GPS tab for valid coordinates |
| Quad oscillates wildly during rescue | PIDs too aggressive, angle too high, or excessive ground speed | Reduce Angle to 30°, lower Ground Speed to 12 m/s, soften PIDs |
Real-World Reliability Tips
Even a perfectly configured GPS Rescue can fail in the real world. Here’s what experienced long-range pilots do to stack the odds:
- Set the initial climb altitude generous: A 30m climb might clear trees at your flying site, but what about that cell tower half a kilometer away? Set minimum 50m, and 100m+ for mountainous terrain.
- Check satellite count before every flight: At least 10 satellites with HDOP under 1.0. The GPS tab in your OSD should be part of your pre-arm checklist.
- Verify the home arrow: Before taking off, the home arrow on your OSD should point directly at you. If it’s off by 180°, your compass is miscalibrated and rescue will fly away from you.
- Land and reset home point if you move: If you walk 50m from your takeoff location to a better vantage point, the quad’s “home” is still the original coordinates. Land, power cycle, and re-arm.
- Use a self-powered buzzer as a backup: If the quad crashes during rescue (ejected battery), a VIFLY Finder or similar self-powered buzzer will beep for hours, making recovery possible even without GPS coordinates.
- Log your flights: Blackbox logs of rescue events are invaluable for debugging. If rescue behaves oddly, the log will show you GPS coordinates, altitude, heading, and motor outputs throughout the event.
The Psychology of Trusting Rescue
Here’s a truth most guides won’t tell you: even with a perfectly configured GPS Rescue, turning off your radio at 2km out is terrifying. Your brain screams at you that the quad is flying away forever. The only thing that builds trust is repetition. Test rescue every single flying session — not just once when you set it up, but regularly. Flip the switch, watch it work, take back control. After 20 successful rescues, the panic subsides and you can actually enjoy your long range flights knowing you have a genuine safety net.
GPS Rescue isn’t a gimmick — it’s a mature, reliable feature that has saved thousands of quads. But like any safety system, it’s only as good as its configuration and testing. Put in the time. Your future self, staring at a black screen 3 kilometers from home, will thank you.