A quad at 400 feet losing radio link drops for 3.2 seconds before failsafe activates — that’s 85 meters of freefall if you left Stage 1 at default. Most pilots never touch failsafe settings until they watch their quad tumble into a tree line after a single RSSI dropout. Here’s exactly how to configure Stage 1, Stage 2, and GPS rescue so your quad comes back instead of falling.
Understanding Betaflight Failsafe Stages
When your receiver stops sending valid control frames (signal loss, out of range, antenna shadowed), Betaflight doesn’t cut motors immediately. It runs a two-stage sequence:
Stage 1: Signal Loss Grace Period
Stage 1 is a configurable delay during which Betaflight holds the last known control positions. The quad keeps flying exactly as it was — same throttle, same attitude. If the signal returns during Stage 1, control resumes seamlessly. You won’t even notice the dropout.
The default Stage 1 duration (failsafe_delay) is 0.4 seconds. For a quad moving at 30 m/s (67 mph — typical 5-inch freestyle speed), that’s 12 meters traveled before Stage 2 kicks in. If you were pulling out of a dive, holding the “pull out” stick position for 0.4s is fine. If you were mid-roll, holding roll input for 0.4s rotates the quad 288 degrees at 720°/s — you’re inverted when Stage 2 takes over.
Set Stage 1 to 0.5–1.0 seconds for most pilots. Racing pilots flying close to obstacles need shorter (0.3s) — you want the quad to drop rather than fly into a gate on stale inputs. Long-range pilots need longer (1.0–1.5s) because momentary RSSI dips at range are common and you want every chance at recovery before GPS rescue engages.
CLI command: set failsafe_delay = 10 (units of 0.1 seconds, so 10 = 1.0 second)
Stage 2: Failsafe Action
After Stage 1 expires, Betaflight executes the Stage 2 action. You have two options in the Configuration tab under “Failsafe”:
- Drop — Immediate motor disarm. The quad freefalls. This is the safest option for populated areas or racing — you lose the quad but avoid flyaways. For quads with GPS, Drop is never the right choice.
- GPS Rescue — Activates the GPS Rescue procedure: climb to a set altitude, fly toward the home point, descend near home, and disarm. Requires a working GPS lock, magnetometer (or GPS heading), and enough battery to complete the return.
Both are selected in the Failsafe pane of the Configuration tab, not in the Modes tab. The Modes tab “GPS Rescue” switch is for manual activation — different from the failsafe GPS Rescue action.
Verification: After configuring, test on the bench: arm the quad (props off), turn off your radio. Wait for Stage 1 to expire. The motors should spin up to GPS Rescue throttle (if configured) or stop entirely (if Drop). Do not test GPS Rescue in flight without verifying bench behavior first.
RSSI Thresholds and Channel Configuration
Failsafe triggers when your receiver stops sending valid frames. For ExpressLRS, this happens when the link drops below the configured packet rate threshold — typically 50Hz in 50Hz mode, 150Hz in 150Hz mode. But Betaflight doesn’t use RSSI percentage directly for failsafe — it uses a flag called “RX Loss” set by the receiver protocol.
Configuring RSSI for Diagnostics (Not Failsafe)
Even though RSSI doesn’t control failsafe directly, you need it on your OSD to know when you’re approaching link loss. As we covered in our ExpressLRS WiFi flashing guide, set your RSSI channel on the Receiver tab to AUX11 for ExpressLRS, then calibrate:
- In the Receiver tab, verify AUX11 shows a moving value when your radio is on
- Set RSSI channel to AUX11
- “RSSI is in %” should be checked for ExpressLRS (it sends dBm-scaled percentage by default)
For Crossfire, set RSSI channel to AUX8 and leave “RSSI is in %” unchecked — Crossfire sends raw dBm, and Betaflight applies its own scaling.
RSSI Alarm Threshold
Set osd_rssi_alarm to 35 for ExpressLRS — the link is still solid at 35%, and this gives you 15-20 percentage points of warning before actual failsafe (which happens around 15-20% depending on packet rate and environment). CLI: set osd_rssi_alarm = 35
GPS Rescue Configuration (The Failsafe Safety Net)
GPS Rescue requires these elements to be configured BEFORE it can act as a failsafe fallback:
Minimum Satellite Count
set gps_rescue_min_sats = 8 — The quad won’t arm with GPS Rescue enabled if it has fewer than 8 satellites. In urban canyons, this might prevent arming for 60-90 seconds after power-up. Accept the delay — 6 satellites gives a position fix, but accuracy is ±10 meters, and “home” being 10 meters off in a rescue means you land on a roof instead of your launch pad.
Return Altitude
set gps_rescue_altitude = 40 (meters) — 40 meters clears most trees, buildings, and power lines. Set this based on the tallest obstacle at your flying site, plus 10 meters margin. If you fly in mountainous terrain with 50-meter pine trees, set it to 60.
Climb and Descent Rates
set gps_rescue_groundspeed = 1200 — Groundspeed in cm/s, so 1200 = 12 m/s (27 mph). Fast enough to get home before the battery dies, slow enough to maintain GPS accuracy during the return leg.
Sanity Checks
set gps_rescue_allow_arming_without_fix = OFF— Never arm without GPS lock if you’re relying on rescueset gps_rescue_sanity_checks = RESCUE_SANITY_ON— The quad aborts rescue and drops if GPS heading diverges from the home vector by more than 45° for 2+ seconds (indicates compass failure or GPS spoofing)
As discussed in our Betaflight GPS Rescue setup walkthrough, test rescue in an open field at 30 meters before trusting it over water or rough terrain. Flip the GPS Rescue switch mid-flight, verify the quad climbs and turns toward home, then cancel before it lands.
Parameter Comparison: Failsafe Configurations by Flying Style
| Setting | Racing | Freestyle | Long Range | Cinewhoop |
|---|---|---|---|---|
| Stage 1 Delay | 0.3s | 0.5s | 1.0–1.5s | 0.5s |
| Stage 2 Action | Drop | Drop or GPS Rescue | GPS Rescue | Drop |
| RSSI Alarm | 30 | 35 | 40 | 35 |
| Min Sats (if GPS) | 8 | 8 | 10 | 8 |
| Return Altitude | — | 40m | 60m | 30m |
| Throttle on Rescue | — | 1700 | 1650 | 1600 |
Common Mistakes & What Most Pilots Get Wrong
Mistake 1: Leaving Stage 1 at the default 0.4s with GPS Rescue enabled. Here’s what happens: signal drops for 0.3 seconds, Stage 1 doesn’t expire, quad holds last inputs — which were full roll and moderate throttle from a freestyle maneuver. By 0.4s, you’re inverted. Stage 2 kicks in, GPS Rescue activates, and the quad tries to climb while inverted, driving itself into the ground. Fix: increase Stage 1 to 0.5-1.0s so momentary drops don’t cascade into a rescue attempt mid-maneuver.
Mistake 2: GPS Rescue with fewer than 8 satellites. A 6-satellite position fix has a horizontal error of ±8-12 meters. Your “home point” recorded at arm could be 10 meters from where you actually took off. The quad returns to that GPS coordinate and descends — into a lake, onto a road, or into a tree. Always wait for 8+ satellites before arming when rescue is your failsafe action.
Mistake 3: Confusing the Modes tab GPS Rescue switch with failsafe GPS Rescue. The Modes tab switch is for testing and manual activation. Failsafe GPS Rescue is configured in the Configuration tab’s Failsafe pane. If you only configure the Modes tab switch and set failsafe action to Drop, flipping the manual switch works — but a real signal loss drops the quad. Configure both.
Mistake 4: Setting return altitude too low. A 20-meter return altitude clears most obstacles at your flying field — but the quad climbs to that altitude above the ARM point, not above the current position. If you flew down a hill and lost signal 30 meters below your launch point, “20m return altitude” means the quad climbs to -10 meters relative to the terrain in front of it. Set altitude based on the most challenging terrain in your flight area, not the launch pad.
⚠️ 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. Some jurisdictions require that failsafe actions include automatic landing rather than uncontrolled descent — verify your configuration complies.
Recommended Hardware
The Matek M10Q-5883 GPS/Compass module delivers a reliable 10+ satellite lock in under 30 seconds with its M10 chipset — noticeably faster than the older M8N modules, and the built-in compass provides heading data that makes GPS Rescue dramatically more accurate. Available at uavmodel.com.