A failsafe at 500 meters with no GPS rescue configured means your quad drops out of the sky. I’ve watched it happen — not to me, but to pilots who thought “arming on a switch is enough.” It’s not. Here’s the exact failsafe stack that saves your quad when signal drops.
Betaflight Failsafe: Two-Stage Configuration
Betaflight’s failsafe system has two stages. Most pilots only know about Stage 1. That’s the problem.
Stage 1 — Signal Loss (Guard Time)
This is what happens immediately when your receiver stops getting valid data. By default, Betaflight waits 0.4 seconds (Guard Time) before acting. This prevents false triggers from a momentary signal blip. You can adjust this in the CLI:
set failsafe_delay = 4
The value is in tenths of a second — 4 means 0.4s. Don’t go below 0.3s (value 3). I’ve seen micro-dropouts trigger a full failsafe at 0.2s, and the resulting disarm mid-roll wasn’t pretty.
During Stage 1, Betaflight holds the last known channel values. If signal returns within the guard time, nothing happens — you’ll feel a tiny hiccup and keep flying.
Stage 2 — Failsafe Procedure
After the guard time expires, Betaflight executes the failsafe procedure. You have three options:
- Drop — immediate disarm. The quad falls. This is the default. It’s also the worst option for anything but a 3-inch whoop flying 20 feet away.
- Land — Betaflight tries to auto-land at the current position. It’s unreliable. Barometer drift means “land” sometimes means “descend into a tree at 45°.”
- GPS Rescue — the only option worth setting. The quad climbs to a safe altitude, flies home, and either hovers or lands.
Set this on the Failsafe tab or via CLI:
set failsafe_procedure = GPS-RESCUE
If you don’t have a GPS module, set it to DROP and accept the risk. Land mode without GPS is GPS rescue without GPS data — pointless.
Channel Fallback Values
For each channel, set a fallback value that triggers when signal drops. Under the Receiver tab, set:
| Channel | Fallback Value | Reason |
|---|---|---|
| Throttle | 1000 (zero) | Quad must not punch out on failsafe |
| Roll/Pitch/Yaw | 1500 (center) | Level attitude for GPS rescue |
| Arm | 1000 (disarmed) | Prevents re-arm in air |
| Mode switches | Last position or 1000 | Avoid mode-change surprises |
The throttle fallback is critical. If you leave it at “Hold” and the quad was at 70% throttle when signal dropped, GPS rescue fights against full throttle — it either overshoots altitude or fails entirely.
GPS Rescue Configuration — The Parameters That Matter
GPS rescue doesn’t work out of the box. You need a GPS lock (minimum 8 satellites) and these settings tuned to your build.
Minimum Satellites
set gps_rescue_min_sats = 8
Below 8, Betaflight won’t attempt rescue. It’ll drop. The default is 8 — don’t lower it. At 5 satellites, position error can be 30-50 meters. Your quad might “fly home” into a building three blocks away.
Altitude Mode
set gps_rescue_alt_mode = MAX_ALT
Options: MAX_ALT (climb to a set altitude above launch), FIXED_ALT (climb to a fixed absolute altitude), CURRENT_ALT (maintain current altitude + offset). MAX_ALT is safest — it climbs above everything, then comes home.
Initial Climb and Return Altitude
set gps_rescue_initial_climb = 50
set gps_rescue_altitude = 70
These are in meters. Initial climb is the immediate ascent after failsafe triggers. Return altitude is the cruise altitude back home. I run 50m initial climb and 70m return altitude where I fly (suburban, cell towers at ~40m). Adjust for your environment — if you’re in mountains, double it.
Ground Speed
set gps_rescue_ground_speed = 1200
In cm/s. 1200 = 12 m/s = ~43 km/h = ~27 mph. Faster gets you home quicker but uses more battery. A 5-inch freestyle quad at 30° tilt cruises at about 15 m/s — set it there.
Sanity Checks — The Settings That Prevent Flyaways
set gps_rescue_sanity_checks = RESCUE_SANITY_ON
set gps_rescue_allow_arming_without_fix = OFF
Sanity checks verify the quad is actually moving toward home during rescue. If it’s flying away (GPS glitch, wrong home point), it disarms. You want this on. The arming check prevents you from arming without a GPS lock — annoying when you’re impatient, lifesaving when you forget.
Testing GPS Rescue Without Risking Your Quad
You don’t test GPS rescue by flying a kilometer out and turning off your radio. Here’s the safe method:
- Hover at 5 meters, 20 meters away
- Enable GPS Rescue via a switch (Modes tab → GPS RESCUE)
- Verify the quad climbs and returns to the home point
- Test again at 10m and 30m
- Disarm if anything goes wrong — you’re close enough to recover
The first test will reveal problems: wrong home point, insufficient climb rate, wrong return direction. Fix them at 20 meters, not 500.
If your quad oscillates during rescue, lower gps_rescue_throttle_p, gps_rescue_throttle_i, and gps_rescue_throttle_d — start at P=80, I=15, D=20. High P causes altitude hunting. High D causes jerky throttle response.
Common Failsafe and GPS Rescue Mistakes
Mistake 1: Setting failsafe to “Hold” on throttle. If the quad loses signal at full punch-out and throttle holds at 2000μs, it rockets to the moon. Always set throttle fallback to 1000. Your quad can survive a drop — it cannot survive a flyaway.
Mistake 2: GPS Rescue without sanity checks. A GPS module that reports 15 satellites but a bad home point will fly your quad 2 kilometers in the wrong direction. Sanity checks catch this. Turn them on.
Mistake 3: Not testing after a firmware upgrade. Betaflight 4.3, 4.4, and 4.5 all changed GPS rescue defaults. Upgrading without re-testing means the settings you trusted last month might not behave the same way today.
Mistake 4: Insufficient climb altitude for the environment. If you set initial climb to 30m and there’s a 35m tree between your quad and home, rescue fails — your quad hits the tree at 12 m/s. Always climb above your tallest obstacle by 20m. Walk your flying site, note the highest structure, add 20.
Mistake 5: Running GPS rescue on a dying battery. GPS rescue at 12 m/s draws more current than cruising. A 1km return at 12 m/s takes about 83 seconds — if you’re already at 3.5V/cell, you might not make it. As we discussed in our LiPo C-rating guide, voltage sag under sustained load is real. Land with 20% reserve.
⚠️ 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 is a tool, not a guarantee. I’ve had it work flawlessly 30 times and fail once because the GPS module rebooted mid-flight. That one failure is why I still set my radio to call out RSSI every 5 seconds when I’m pushing range — as covered in our RSSI and LQ setup guide, knowing your link margin before it hits zero is your first line of defense.
For reliable GPS rescue, the BN-880Q GPS/Compass module with a u-blox M8N chipset delivers consistent 12+ satellite locks, supports Galileo and GLONASS, and includes a built-in compass for accurate home-point heading — available at uavmodel.com.