You clip a gate, the quad cartwheels, and suddenly the motors scream at full throttle while the quad spins uncontrollably toward the parking lot. This isn’t a failsafe — it’s a crash recovery failure. The flight controller thinks it’s recovering from a disturbance and applies corrective throttle, but the quad is on the ground with two broken props. Here’s how to configure crash recovery so your quad disarms when it should, and only when it should.
Configuring Betaflight Crash Recovery (Step by Step)
Step 1: Enable crash_recovery in CLI
Go to the Betaflight CLI tab and enter:
set crash_recovery = ON
save
This enables the crash recovery feature, but the default settings are conservative — they work for gentle bumps but not for gate impacts at race speed. We need to tune three parameters for your build.
Step 2: Tune crash_delay — How Long Before Recovery Attempts
After a crash is detected, crash_delay (in milliseconds) is how long the FC waits before trying to level the quad. Default is 0ms — the FC tries to recover immediately.
For a 5-inch freestyle quad, set it to 200ms:
set crash_delay = 200
This 200ms pause lets the quad’s gyro settle after impact. Without it, the FC reads a spinning gyro from the cartwheel and applies corrective motor output in a random direction — producing the classic “spinning flyaway” behavior.
For lightweight whoops (sub-100g), 0ms is fine — there’s not enough inertia to spin the gyro after impact.
Step 3: Tune crash_gthreshold — Gyro Trigger Level
The crash_gthreshold is the gyro rate (deg/s) that triggers crash detection. Default is 2000 deg/s, which is a 5.5-revolution-per-second spin.
Lower it to 1100 deg/s for aggressive flying:
set crash_gthreshold = 1100
At 2000 deg/s, many impacts that should trigger detection don’t — especially glancing gate hits where the quad doesn’t fully spin. At 1100 deg/s, you get consistent detection on gate clips and ghost-branch strikes, but the quad still won’t false-trigger during sharp freestyle moves like snap rolls.
Don’t go below 800 deg/s — power loops and split-S maneuvers can hit 700+ deg/s momentarily, and a false crash detection mid-maneuver disarms your quad at 30 meters.
Step 4: Tune crash_time and crash_recovery_angle
set crash_time = 500
set crash_recovery_angle = 10
crash_time (500ms) is how long the FC stays in recovery mode. During this window, it ignores the pilot’s inputs and tries to level the quad. 500ms is enough for most builds to stabilize.
crash_recovery_angle (10 degrees) is the maximum angle the FC will command during recovery. At 10 degrees, recovery is gentle — the quad doesn’t shoot off in a random direction. Race pilots prefer 15-20 degrees for faster recovery, but freestyle pilots should stick to 10 — you want level and steady, not fast.
Step 5: Verify Runaway Takeoff Prevention
This is separate from crash recovery but works alongside it. The runaway takeoff feature disarms the quad if it detects motors spinning up without corresponding attitude change (props off, quad stuck, or catastrophic mechanical failure).
set runaway_takeoff_prevention = ON
set runaway_takeoff_deactivate_delay = 500
set runaway_takeoff_deactivate_throttle_percent = 25
Verify it works: Arm the quad with no props. Blip the throttle to 30% for 2 seconds. The motors should disarm automatically after ~0.5 seconds with the “RUNAWAY” warning in the OSD. If they don’t disarm, your gyro orientation may be wrong — the FC expects the quad to move when motors spin, and if it doesn’t see movement, it assumes a stuck quad.
Crash Recovery Parameter Reference
| Parameter | Default | Recommended (5-inch Freestyle) | Recommended (Racing) | Effect of Too Low | Effect of Too High |
|---|---|---|---|---|---|
| crash_recovery | OFF | ON | ON | No recovery — crash = flyaway | N/A |
| crash_delay | 0ms | 200ms | 50ms | Gyro noise triggers recovery in random direction | Missed recovery window, quad already on ground |
| crash_gthreshold | 2000 | 1100 | 1000 | Glancing impacts don’t trigger recovery | False triggers during hard freestyle |
| crash_time | 500ms | 500ms | 300ms | Recovery too short to level | Unresponsive to pilot inputs too long |
| crash_recovery_angle | 10 | 10 | 15 | Recovery too slow to save quad | Recovery shoots off in random direction |
| crash_limit_yaw | 200 | 200 | 200 | N/A | Recovery tries to yaw-correct unnecessarily |
What Pilots Get Wrong About Crash Recovery
Mistake 1: Relying on crash recovery instead of a proper failsafe
Crash recovery works when the FC is still powered and processing. If the battery ejects on impact — which happens in about 30% of hard crashes — crash recovery does nothing. The fix: Set up proper Stage 2 failsafe with zero throttle and a disarm timeout. Our failsafe configuration guide covers every scenario.
Mistake 2: Leaving crash_delay at 0ms
Zero delay means the FC reads whatever gyro value is present the instant it detects a crash. During a cartwheel, the gyro is spinning at 2000+ deg/s. The FC interprets this as “the quad is upside down and accelerating” and punches the motors to “recover” — which sends it sideways at full throttle. The fix: Set crash_delay to at least 100ms on any build over 100g. Let the gyro settle.
Mistake 3: Disabling crash recovery to reduce “false positives”
A pilot gets two false crash recoveries during power loops and decides to disable the feature entirely. Next race, they clip a gate and the quad spins under full throttle into the spectator net. The fix: False triggers come from gthreshold being too low, not from the feature being broken. Tune gthreshold, don’t disable crash recovery. A false disarm at 15 meters is a crash; a missed disarm at 1 meter into a metal pole is a fire.
Mistake 4: Not testing crash recovery after every firmware update
Betaflight defaults change between versions. A feature that was ON in 4.4 might be OFF in 4.5 after a full chip erase. The fix: After every firmware flash, run diff all and confirm crash_recovery = ON in the output. Don’t assume your settings survived the upgrade.
Mistake 5: Using crash recovery as a substitute for a physical disarm switch
Some pilots think “crash recovery will handle it” and get lazy about hitting the disarm switch on a crash. Crash recovery is a backup — it exists for the moments when you can’t react fast enough. The fix: Train the disarm reflex. The moment you lose control, disarm. Crash recovery should only ever activate when the disarm reflex fails.
⚠️ Regulatory Notice: Crash recovery configuration affects your drone’s behavior during and after uncommanded maneuvers. Always test crash recovery settings in a controlled environment away from people and property. Follow the latest 2026 drone regulations in your country or region regarding failsafe requirements and proximity to spectators. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
Once your crash recovery settings are dialed, your blackbox logs become much more useful — you can distinguish between tuning problems and crash artifacts. Our blackbox log analysis guide walks through the full diagnostic workflow. For GPS-equipped quads that can autonomously return after a signal loss, pairing crash recovery with our GPS rescue setup gives you a complete safety net.
When a crash recovery fails and you’re replacing a flight controller, the SpeedyBee F405 V4 brings onboard blackbox flash and crash-resistant soldering pads that survive repeated impacts — available at uavmodel.com.