GPS Rescue is Betaflight’s answer to “I lost video at 2km.” When it works, your quad climbs, turns toward home, flies back, and descends to a safe altitude. When it fails, your quad flies the wrong direction at full throttle or drops into the ocean because minimum satellites wasn’t met. The gap between those two outcomes is about 20 minutes of correct configuration and 30 minutes of field testing. Most pilots skip the testing part. Here’s how to do it right.
Step-by-Step: Betaflight GPS Rescue Configuration
1. Hardware That Actually Works
The GPS module is the foundation. Don’t cheap out here.
Required hardware:
– GPS module with compass: BN-880Q or Matek M10Q-5883. The M10 chipset locks 15+ satellites in under 30 seconds — a generation ahead of the older M8 chipsets.
– Mounting: Away from the VTX antenna and carbon fiber. The top of a rear standoff or a TPU mast mount works. Carbon fiber blocks GPS signals.
– Wiring: 4 wires minimum (VCC, GND, TX, RX) to a free UART. SCL/SDA for compass is optional but recommended.
What happens if you get it wrong: An M8 GPS under a carbon top plate gets 6-8 satellites and takes 2+ minutes for a 3D fix. GPS Rescue activates with inadequate satellite count, your home point drifts, and the quad flies toward a position 50 meters from where you actually are.
In our GPS module selection guide, we covered the hardware side in depth. The M10 chipset is the current standard for 2026.
2. Betaflight Configuration Tab Settings
Navigate to the GPS tab and configure:
Protocol: UBLOX
Auto Config: ON
Auto Baud: ON
Ground Assistance Type: AUTO
These three settings handle 90% of compatibility issues. The M10 defaults to 115200 baud and 5Hz update rate — Betaflight auto-negotiates these correctly with Auto Config enabled.
In the Ports tab, set the UART’s Sensor Input to GPS at the baud rate your module uses (usually 115200 for M10, 9600 for older BN-220).
Verification: After powering up with a battery (USB alone may not power the GPS), check the GPS tab. You should see a 3D fix within 30-60 seconds outdoors. If it stays at “NO FIX” for 2+ minutes, check your wiring — the most common failure is swapped TX/RX.
3. Failsafe Tab — GPS Rescue Settings
This is where most pilots get it wrong. Navigate to Failsafe → Stage 2.
Stage 2 Settings:
- Stage 2 Failsafe Procedure: GPS Rescue
- Sanity Checks: ON (ALL THREE — this is critical)
- GPS Rescue Sanity Checks — Rescues Require: MIN_SATS — number of satellites
- Allow Arming Without Fix: OFF
- GPS rescue will not be activated if altitude (home altitude + GPS) is below sanity check maximum altitude
The sanity checks prevent GPS Rescue from activating when the GPS data is unreliable. A quad that arms without a GPS fix will trigger GPS Rescue without a valid home position — the quad has no idea where “home” is.
Throttle settings (critical):
- Throttle: 1500-1600 range (adjust per build)
- Climb throttle: 80% of your hover value + 200-300us buffer
- Climb time (seconds): The number of seconds the quad should climb before starting the return flight
- Maximum Rescue Throttle: Start at 1800 and work down
How to set climb throttle: Hover your quad in angle mode. Note the throttle percentage. Multiply by 10 to get the approximate µs value. Add 200-300µs. A 5-inch quad hovering at 27% throttle: (27 × 10) + 250 = 520µs climb throttle above hover. This ensures the quad climbs — not descends — on rescue activation.
What happens if you get it wrong: Climb throttle too low and your quad drops during the climb phase. Too high and the quad rockets upward, potentially violating altitude limits. No sanity checks and your quad activates rescue without a valid home position — it flies in a random direction until the battery dies.
4. Altitude and Distance Settings
- Initial Climb: 20 meters (minimum — more if you fly behind obstacles)
- Max Rescue Altitude: 100 meters
- Ground assistance: ON (auto-disarms 1 second after landing)
- Descent distance: 100 meters (quad begins descending when within this distance of home)
The initial climb of 20 meters clears most tree lines. If you fly in mountainous terrain or behind buildings, set this higher.
Field test procedure: Arm the quad, lift off to 2 meters, switch to GPS Rescue via a transmitter switch. The quad should climb to the set altitude, then either hover (if already at home) or begin flying toward home. Land and verify the quad returns to within 5 meters of the takeoff point.
5. Advanced: GPS Rescue on a Switch
Set up a dedicated “OH SHIT” switch on your transmitter:
1. In the Modes tab, assign an AUX channel (I use AUX4 on a momentary switch) to GPS RESCUE.
2. Set the active range to cover the switch’s activated position.
3. The switch overrides the failsafe trigger — useful for testing and emergencies when you still have control link but lost video.
GPS Rescue Parameter Quick Reference
| Setting | Recommended Value | Too Low | Too High |
|---|---|---|---|
| Climb Throttle | Hover+250µs (~1525 for 5″) | Quad descends during climb, hits ground | Quad rockets up, wastes battery |
| Initial Climb | 20m | Can’t clear trees | Wastes battery on climb |
| Max Rescue Altitude | 100m | May fly into obstacles | Violates 120m ceiling in some regions |
| Descent Distance | 100m | Quad descends too late, overshoots home | Descends too early, may land in trees |
| Min Satellites | 8 | Inaccurate home position | Rescue never activates |
| Ground Assistance | ON | Quad stays armed after landing, props spin in grass | N/A — always ON |
Common Mistakes & How to Avoid Them
Mistake 1: Testing GPS Rescue Without Altitude
What people do: Test GPS Rescue on the bench by pulling the arm switch.
Consequence: The quad has no altitude reference or satellite lock indoors. GPS Rescue either doesn’t activate (correct behavior with sanity checks) or activates with garbage data. Neither outcome tells you anything about real-world performance.
Fix: Test outdoors with a real GPS lock and at least 2 meters of altitude. A dedicated GPS Rescue switch (separate from the arm switch) lets you test without actually triggering failsafe.
Mistake 2: Disabling Sanity Checks for “Reliability”
What people do: GPS Rescue fails to activate once, so they turn off sanity checks to “make it work.”
Consequence: The quad activates GPS Rescue with 4 satellites and no valid home position. It flies full-throttle in a random direction — possibly toward a road, water, or people.
Fix: Never disable sanity checks. If GPS Rescue isn’t triggering, fix the underlying issue (better GPS placement, wait for more satellites) rather than removing the safety net.
Mistake 3: Wrong Climb Throttle for the Build
What people do: Copy climb throttle settings from a YouTube video for a different quad weight/power combo.
Consequence: A 700g 7-inch quad with 1300KV motors needs much less throttle to climb than a 250g 5-inch racer with 2700KV. Static settings cause aggressive climbs on some builds and descents on others.
Fix: Measure your quad’s hover throttle in stable angle-mode flight. Set climb throttle as hover + 250-300µs. Test and adjust.
Mistake 4: Trusting GPS Rescue Without Range Testing
What people do: Set it up, test it once at 20 meters, then fly 2km out assuming it works.
Consequence: At range, VTX interference on the GPS band reduces satellite count. Magnetic interference from high-current draws shifts compass heading. The rescue that worked at close range degrades at distance.
Fix: After successful close-range testing, fly 500m out, trigger GPS Rescue via switch, and monitor the return. Gradually extend your trust radius. Verify RSSI during the return — if your control link is marginal at 500m, GPS Rescue is your only lifeline at 2km.
⚠️ Regulatory Notice: GPS Rescue is not a substitute for maintaining visual line of sight or complying with altitude restrictions. The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities. Always verify local laws regarding autonomous flight modes, altitude limits, and no-fly zones.
Internal Links
Our GPS module selection guide covers hardware specs and wiring in detail — pair it with this article for a complete setup. For the emergency scenario where GPS Rescue fails, our failsafe setup guide explains Stage 1 and Stage 2 behavior in depth. Long-range pilots should also read our long-range FPV build guide for redundancy planning.
YouTube Resource
Oscar Liang’s GPS Rescue setup walkthrough covers the configuration tab by tab with real flight footage:
uavmodel Product Recommendation
The Matek M10Q-5883 GPS/Compass module (available at uavmodel.com) locks 20+ satellites in under 30 seconds with the M10 chipset and includes a built-in compass for accurate heading — essential for reliable GPS Rescue performance.