FPV Failsafe Settings: How to Configure Betaflight Failsafe to Prevent Flyaways

Failsafe is one of the most critical safety features in an FPV drone. It ensures that when the radio control link is lost, the drone will execute a predefined sequence of actions—rather than flying away uncontrollably. A properly configured failsafe can mean the difference between recovering your drone and losing it forever.

In this guide, we’ll walk through exactly how to set up Betaflight failsafe, explain each stage and parameter, show you how to test it safely, and highlight common mistakes that could leave you unprotected.

What Is Failsafe?

Failsafe is the drone’s automatic response to a lost radio signal. Without a signal, the flight controller no longer receives pilot commands; failsafe tells it what to do instead. Betaflight implements a two‑stage failsafe:

• Stage 1: Triggered after a short delay (typically 0.5–1 second) of signal loss. The drone can be set to drop, land, hover, or enter Stage 2.
• Stage 2: Activated if signal loss persists. Usually commands the drone to land or drop (kill motors).

Betaflight Failsafe Stages & Parameters

| Parameter | Default | Recommended | Description |
|———–|———|————-|————-|
| `failsafe_stage1_delay` | 0.5 sec | 1.0 sec | Time before Stage 1 activates after signal loss. |
| `failsafe_stage1_procedure` | DROP | LAND | Stage 1 action: DROP (kill motors), LAND (descend gently), HOVER (hold position), or STAGE2 (skip to Stage 2). |
| `failsafe_stage2_delay` | 5.0 sec | 8.0 sec | Time after Stage 1 before Stage 2 activates. |
| `failsafe_stage2_procedure` | KILL | LAND | Stage 2 action: KILL (stop motors), LAND (continue landing), or DROP. |
| `failsafe_switch_mode` | OFF | ON (if using a switch) | Enables a dedicated failsafe switch on your transmitter. |
| `failsafe_throttle_low_delay` | 0.0 sec | 0.5 sec | Delay before triggering failsafe when throttle is low (anti‑false‑trigger). |
| `failsafe_throttle` | 1000 µs | 1000 µs | Throttle pulse width used during failsafe landing. |

Important: The exact parameter names may differ slightly between Betaflight versions (e.g., `failsafe_delay` vs `failsafe_stage1_delay`). Always check your version’s CLI `dump` for the current names.

Step‑by‑Step Configuration in Betaflight Configurator

1. Connect your flight controller to Betaflight Configurator (10.8.1 or newer).

2. Go to the Failsafe tab (under the Configuration section). 3. Set Stage 1:

2. Delay: `1.0` seconds
3. Procedure: LAND (recommended for most builds)

4. Set Stage 2:

4. Delay: `8.0` seconds (gives you time to re‑acquire signal)
5. Procedure: LAND (or KILL if flying over water/unrecoverable terrain)

5. Enable “Use failsafe switch” if you want a physical switch to trigger failsafe manually (useful for testing). 6. Click “Save & Reboot”.

Testing Your Failsafe Safely

Never test failsafe with a fully armed drone near people or property. Follow this safe test routine:

1. Remove props from the motors.

2. Arm the drone (motors will spin slowly). 3. Turn off your transmitter (or walk out of range) to simulate signal loss. 4. Observe the motors: After the Stage‑1 delay, they should either stop (DROP) or ramp down (LAND). After the Stage‑2 delay, they should stop completely. 5. Check the OSD: The Betaflight OSD will show “FAILSAFE” when triggered.

Common Mistakes That Leave You Unprotected

• Setting Stage‑1 procedure to DROP on a GPS‑less drone: The drone will fall out of the sky immediately—only use DROP if you have a parachute or are over water.
• Too short Stage‑2 delay: If you set `failsafe_stage2_delay` to 2 seconds, the drone may land before you can re‑establish signal.
• Forgetting to set `failsafe_throttle`: If you use LAND, the drone uses this throttle value to descend. Too low (e.g., 900 µs) may cause a hard landing.
• Not testing after a firmware update: Failsafe parameters can reset after flashing new firmware.

Recommended Hardware: A Flight Controller with Reliable Failsafe Execution

A robust failsafe depends on a flight controller that processes signals quickly and executes the failsafe sequence without delay. The Mamba F722 APP Flight Controller from uavmodel.com provides:

• Betaflight‑certified failsafe logic with zero lag.
• Dual‑gyro redundancy—if one gyro fails, the other keeps the drone stable during failsafe landing.
• Built‑in 30A BLHeli‑32 ESCs that respond instantly to motor‑stop commands.
• UART‑based RX connections that detect signal loss within milliseconds.

For pilots who fly near people or expensive equipment, investing in a flight controller that handles failsafe flawlessly is a non‑negotiable safety upgrade.

Watch: Betaflight Failsafe Setup Tutorial

See the exact steps in action with this detailed video walkthrough:

Frequently Asked Questions

Q: What’s the difference between “DROP” and “KILL” in Betaflight failsafe?

A: DROP immediately cuts power to the motors (free fall). KILL also stops the motors but is intended for the second stage after a landing attempt has already begun.

Q: Can I use failsafe with a GPS‑rescue mode?

A: Yes, if you have GPS installed and configured, you can set `failsafe_procedure = GPS_RESCUE` (available in Betaflight 4.4+). The drone will climb, return to home, and land automatically.

Q: How do I know if my failsafe is working without removing props?

A: You can enable “failsafe switch” and assign a transmitter switch to trigger failsafe on command. Arm the drone (with props off), flip the switch, and verify the motors behave as expected.

Q: Why does my drone still fly away even with failsafe set?

A: The most common cause is an incorrectly configured receiver. Some PWM receivers output a “hold last command” signal when signal is lost, which the flight controller interprets as valid input. Use a serial‑based receiver (SBUS, CRSF, etc.) that sends a true “signal lost” frame.

Q: Does failsafe work with all radio protocols?

A: It works best with modern digital protocols (Crossfire, Ghost, ELRS, TBS Tracer) that send explicit “link lost” packets. Analog PWM/PPM receivers may not trigger failsafe reliably.