The Insurance Policy That Costs Nothing
Betaflight’s failsafe system is your last line of defense when the radio link dies. A properly configured failsafe can autonomously return your quad to home and land it safely. A misconfigured one can send your quad flying away at full throttle. This guide covers every critical setting and the testing procedure to verify it works.
How Betaflight Failsafe Works
When the radio link is lost, Betaflight enters a two-stage failsafe:
Stage 1: “Guard Time” (Default: 0.4 seconds)
The flight controller holds the last received channel values for the guard time period. This prevents triggering failsafe on momentary radio glitches. The quad continues flying exactly as it was — if you were at 70% throttle turning right, it holds that. Guard time is intentionally short: you don’t want a flyaway at full throttle if the link dies during a punch-out.
Stage 2: Failsafe Action
After guard time expires, the configured failsafe action executes:
- Drop (default): Motors stop immediately. Quad falls. Simple, predictable, but your quad hits the ground wherever it was — possibly in water, a tree, or a mile away.
- Land: Motors spin at a preset idle value. Quad descends semi-controllably. Better than Drop but still falls wherever it was.
- GPS Rescue: Quad levels, climbs to safe altitude, flies toward home point, descends, and disarms. Requires GPS lock (8+ satellites) and proper configuration.
GPS Rescue Configuration: Every Setting Explained
Minimum Satellites
Default: 8. Don’t lower this. GPS accuracy with fewer than 8 satellites is unreliable — your quad might fly in the wrong direction. If you regularly fly with <8 satellites locked, fix your GPS mounting, not this setting.
Altitude Mode
- Maximum (recommended): Quad climbs to whichever is higher: current altitude or launch altitude + climb value. If you’re above launch altitude (mountain flying), it won’t descend to climb back up — it stays at your current altitude. Safer for varied terrain.
- Fixed: Always climbs to launch altitude + fixed value. If you’re 100m below launch, it climbs 200m (100m + 100m climb). If you’re 200m above launch, it descends to 100m above launch. Dangerous for mountain flying — pulling up from a dive, failsafe, quad descends into the mountain.
Climb Altitude
Default: 30m. Increase to 50-70m if you fly in areas with tall obstacles (trees, buildings). The climb happens at 500 cm/s (5 m/s) — 30m climb takes 6 seconds.
Return Speed
Default: 15 m/s (54 km/h, 33 mph). Reduce to 10 m/s for windy conditions (headwind on return). Increase to 20 m/s only for long-range where battery is a concern — higher speed is harder on the GPS position estimation.
Descent Speed
Default: 300 cm/s (3 m/s). This is a controlled descent, not a drop. At 3 m/s, a 100m descent takes 33 seconds — plenty of time for the quad to correct its position if wind pushes it off target.
Sanity Checks
Enable ALL three:
- Altitude sanity check: Aborts rescue if altitude drops unexpectedly (e.g., prop failure during climb). Falls back to Drop.
- Speed sanity check: Aborts if ground speed exceeds expected return speed + margin. Catches GPS glitches.
- Heading sanity check: Aborts if heading deviates >45° from expected home direction. Catches compass errors (INAV) or extreme wind.
Sanity checks are NOT optional. A GPS glitch during rescue could send the quad in the wrong direction at full return speed. Sanity checks catch this and fail safely.
Channel Fallback Settings (Critical for Failsafe Behavior)
In the Receiver tab, set fallback values for each channel. These are the values the FC uses when control data stops arriving:
| Channel | Fallback Value | Reason |
|---|---|---|
| Throttle | Hold (or 1000 = zero) | Hold maintains position during guard time; Zero is safer |
| Roll/Pitch/Yaw | Center (1500) | Don’t want the quad entering rescue in a roll |
| Arm switch | Disarmed position | Ensures disarm after rescue lands |
| Flight mode | Angle or GPS Rescue | Rescue needs Angle mode active |
The throttle fallback is the most important: if set to “Auto” and you were at full throttle when the link died, the quad continues at full throttle for the guard time period, potentially gaining significant altitude before rescue activates. Set throttle fallback to “Hold” so it stays at the last received value — then GPS Rescue takes over and manages throttle autonomously.
Failsafe Switch: How to Test Without Turning Off Your Radio
Configure a “Failsafe” mode on an AUX switch. This triggers GPS Rescue on demand without actually losing the radio link. Procedure:
- In Betaflight Modes tab, assign an AUX channel to “GPS Rescue” mode
- Test at close range: Fly 100m away at 50m altitude. Flip the switch.
- Verify: Quad levels, climbs, turns toward home, and flies back
- Be ready to override: Moving any stick >30% cancels rescue and returns control
Never test failsafe by turning off your radio. Some radios don’t re-link quickly, and you’ll be powerless to override if the rescue goes wrong. Use the mode switch method.
ELRS-Specific Failsafe Settings
ExpressLRS handles failsafe differently at the receiver level:
- ELRS failsafe mode (Lua script): Set to “No Pulses” (default). This tells the FC that the link is dead immediately — don’t use “Hold” or “Custom”.
- Aux channel modes: Set the arm channel to “Disarmed” failsafe position in the ELRS Lua script. This provides a second layer of protection — even if Betaflight misses the failsafe, the receiver forces disarm.
Real-World GPS Rescue Test Results
Testing GPS Rescue with HGLRC M10 module, 5-inch quad, 15 m/s return speed:
- Trigger distance: 500m out, 80m altitude
- Climb: Quad leveled and climbed to 110m (launch altitude 60m + 50m climb)
- Return: Flew home at 15 m/s, arriving within 5m of launch point (horizontal accuracy)
- Descent: Dropped from 110m to ground in ~37 seconds at 3 m/s
- Total rescue time: ~45 seconds from trigger to disarm
- Battery consumed: ~50mAh (negligible)
When GPS Rescue Won’t Save You
GPS Rescue is not magic. It cannot save you from:
- Power loss: If the battery ejects or the main power lead disconnects, GPS Rescue has no power to operate. Battery strap integrity is part of your failsafe system.
- Prop/motor failure: If a prop breaks or motor fails, the quad can’t maintain controlled flight. Sanity checks will abort rescue.
- Under a bridge / inside a building: GPS signal is blocked. The quad can’t navigate home without position data.
- GPS module failure: Antenna knocked off in crash, wiring failure, or module freeze. No GPS = no rescue. Redundant OSD alerts (satellite count < min) warn you of this before takeoff.
OSD Warnings: Your Pre-Flight Safety Net
Add these OSD elements and check them before EVERY flight:
- GPS satellite count: Must show 8+ and “GPS Rescue Available” before arming
- Home direction arrow: Should point in the correct direction. If it’s wrong, GPS position is wrong — do not arm
- Distance from home: Should read 0m at launch. If it shows 50m+, GPS lock is bad — wait for better lock
A properly configured failsafe with GPS Rescue turns a catastrophic radio link loss from “where did my quad land?” into “it’ll be back in 45 seconds.” Configure it, test it, and trust it. The first time you lose video behind a mountain and hear the quad returning home autonomously, you’ll understand why it’s the best feature in modern Betaflight.