The default Betaflight failsafe is “drop.” Your quad cuts power and falls from the sky the instant signal is lost. If you haven’t changed this, every flight is a gamble. Here’s how to configure failsafe so your quad does something intelligent when the link drops — and more importantly, how to test it so you trust it.
Understanding Betaflight Failsafe Stages
Betaflight uses a two-stage failsafe system. Stage 1 is your “warning period” — the radio link is degraded but not gone. Stage 2 is the actual failsafe — the link is dead and autonomous action begins.
Stage 1: Link Degradation (Guard Time)
When the receiver stops receiving valid frames, Betaflight enters Stage 1. This lasts for the “Guard Time” you set (default is 1.0 seconds). During this period:
– The quad holds the last valid stick positions
– If signal returns within guard time, control resumes immediately with no interruption
– If guard time expires, Stage 2 activates
Recommended Guard Time: 0.4 seconds for racing (minimal recovery delay), 1.0 seconds for freestyle (balance), 1.5-2.0 seconds for long-range (max patience before declaring emergency).
What if it’s wrong? Too short and brief interference triggers a full failsafe unnecessarily. Too long and the quad flies blind on stale stick inputs for up to 2 seconds — at 70mph, that’s 60 meters of uncontrolled flight.
Stage 2: Failsafe Action
This is where you choose what the quad does. The options:
-
Drop — Motors stop instantly. Quad falls. Default setting. Never use this unless you fly exclusively over soft grass.
-
Land — Quad reduces throttle to a controlled descent. Motors remain active. Works at any altitude but drifts with wind. Better than drop, worse than GPS rescue.
-
GPS Rescue — Quad climbs to a set altitude, flies back to home point, and descends. Requires working GPS with 8+ satellites and a valid home point. This is what you want for anything beyond park flying.
Configuring GPS Rescue (Betaflight 4.4+)
Navigate to Failsafe tab in Betaflight Configurator:
- Set “Stage 2 Failsafe Procedure” to GPS Rescue.
- Initial Climb Time: 3-5 seconds. The quad climbs at the “Initial Climb Throttle” setting. For a 5-inch, 1600-1700 throttle is enough. For a 7-inch, 1550-1600.
- Return Altitude: Set this HIGHER than the tallest obstacle in your flying area. If there’s a 50-meter tree line, set it to 70m. The quad climbs to this altitude (or maintains it if already higher) before starting the return.
- Return Speed: 14-18 m/s for most quads. Too fast and the quad overshoots home point. Too slow and it drains battery on the return.
- Descent Speed: 3-5 m/s. The quad descends vertically above home point. At 5 m/s from 70m, that’s a 14-second descent — plenty of time to regain signal.
- Sanity Checks: Enable all of them. Max rescue altitude, minimum satellites (set to 8), and maximum distance. If sanity checks fail, the quad falls back to Land instead of flying away into the sunset.
Testing GPS Rescue: Arm with props off, wait for GPS lock (8+ satellites confirmed in OSD), then trigger failsafe manually via your radio’s failsafe setting or by powering off the radio. Watch the OSD and motors — the motors should spin up to climb power, indicating the rescue logic is running. Do NOT test with props on unless you have a wide open field and are prepared for the quad to climb autonomously.
Channel Fallback Settings
Below the Stage 2 dropdown, you’ll find channel fallback values. These define what each channel does during failsafe:
| Channel | Setting | Why |
|---|---|---|
| Roll/Pitch/Yaw | Auto (centered) | Keeps quad level during rescue |
| Throttle | Auto (mid) | Determined by rescue logic, not this setting |
| Arm | Hold last | Prevents unintended disarm during Stage 1 |
| Beeper | Set to ON | Quad beeps during failsafe for acoustic location |
| Angle/Horizon Mode | Set to ON | Forces angle mode during rescue for stability |
Verify: After configuring, go to Receiver tab, turn off radio, and confirm all channel bars snap to their fallback values.
What Most Pilots Get Wrong About Failsafe
Mistake 1: Leaving Stage 2 on “Drop”
I cannot count how many quads I’ve seen lost because the pilot never changed failsafe from default. A quad falling from 100 meters hits the ground at terminal velocity. A quad doing GPS rescue from 100 meters lands gently. This is a 5-minute configuration change that determines whether you walk home with a quad or a bag of carbon splinters.
Mistake 2: Testing GPS Rescue for the First Time at the Field
GPS rescue has dozens of interacting parameters. Test it on the bench first (props off, confirm motor response). Then test in a wide open field at low altitude (15-20m). Do not wait until you actually need it at 2km range.
Mistake 3: Setting Return Altitude Too Low
Pilots set return altitude to 30m because they fly in a park. Then they fly behind a 40m building and the quad tries to return THROUGH it. GPS rescue has no obstacle avoidance. Set altitude for the worst-case obstacle in your entire flying radius.
Mistake 4: Forgetting That GPS Rescue Needs a Valid Home Point
GPS rescue requires the home point to be set at arm time. If you arm before GPS has 3D fix (8+ satellites), your home point is either wrong or nonexistent, and rescue won’t work. Add a GPS satellite count element to your OSD and never arm until you see 8+.
Mistake 5: Not Configuring Failsafe on the Radio Side
Even with perfect Betaflight failsafe, your radio needs to be configured to stop sending on signal loss. In ExpressLRS and Crossfire, the receiver will generally detect loss regardless, but on some protocols the radio keeps transmitting a frozen last position, which prevents Betaflight from ever entering failsafe. Set your radio’s failsafe to “No Pulses” or “Cut” — not “Hold.”
Internal Links
If you’re setting up GPS rescue, you’ll want our guide on Betaflight GPS Rescue Sanity Checks. For the receiver side, see our ExpressLRS binding guide to make sure your link is solid before you ever need failsafe.
⚠️ 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 regions also require failsafe systems to meet specific redundancy standards for BVLOS operations.
Recommended Product
GPS rescue only works with a reliable GPS module. The Matek M10Q-5883 GPS/Compass module is my standard recommendation — available at uavmodel.com, it locks 12+ satellites in under 30 seconds cold start and weighs only 6 grams.