You clip a branch at 40mph, the quad tumbles, and by the time your brain registers what happened, it’s already in the dirt. Betaflight’s crash recovery mode changes that equation — the flight controller detects the impact, disables your stick inputs, and autonomously flips the quad to level attitude in under 300 milliseconds. If you’re not running it, you’re giving up a safety net that costs zero weight and zero performance.

How Crash Recovery Actually Works

Crash recovery isn’t a separate flight mode — it’s a gyro-based trigger that temporarily overrides your control inputs. When the flight controller detects an acceleration spike that exceeds the programmed threshold (default: 30 degrees of angular rate error between expected and actual), it:

Disables your stick inputs instantly (prevents you from making the situation worse)
Switches to angle mode internally — pitch and roll are limited to level attitude
Applies max motor authority to arrest the tumble and bring the quad upright
Returns control to you once the quad is within 25 degrees of level OR after 500ms (configurable)

The key insight: it overrides you. When you hit a branch, your instinctive stick reaction — pulling back, rolling, anything — is based on the quad’s attitude before the impact, not after. The quad is tumbling, your corrections are wrong, and you’re fighting the flight controller. Crash recovery takes the sticks away and does the right thing faster than your thumbs can react.

Configuration: Setting It Up Right

Everything lives in the CLI. There’s no GUI slider for crash recovery — you need to understand the parameters to tune it properly.

Basic Enable (Minimum Viable Setup)

set crash_recovery = ON
set crash_recovery_angle = 30
set crash_recovery_rate = 100
set crash_recovery_time = 500
set crash_recovery_gain = 100
save

These defaults work for most 5-inch builds. Let’s walk through what each parameter does and when to adjust it.

Parameter Deep Dive

Parameter	Default	Range	What It Does	When to Increase	When to Decrease
crash_recovery	OFF	ON/OFF	Master enable switch	Always set ON	Never (it’s free insurance)
crash_recovery_angle	30	10-60	Degrees of gyro error to trigger	Open-field flying (fewer false triggers)	Proximity/acro (catches light touches)
crash_recovery_rate	100	20-200	How aggressively it corrects (% of motor max)	Heavy quads (need more authority)	Light quads (can overshoot level)
crash_recovery_time	500	100-1000	Max time (ms) before returning control to pilot	Large quads (more mass to arrest)	Small quads (recover faster)
crash_recovery_gain	100	1-200	PID gain during recovery phase	If recovery overshoots (needs stronger correction)	If recovery oscillates (too aggressive)

Tuning for Your Build

5-inch freestyle (650-750g): Start with defaults. If crash recovery triggers on hard punch-outs (not crashes — just aggressive throttle), raise crash_recovery_angle to 35. The gyro sees the acceleration spike from a full-throttle snap and can misclassify it as an impact. Raising the angle threshold by 5 degrees usually eliminates false triggers without missing real impacts.

3-inch / lightweight builds (250-400g): Lower crash_recovery_rate to 60-70 and crash_recovery_time to 300. Light quads don’t need full motor authority to level — 100% rate on a 300g quad can overshoot and pitch past level, triggering a second recovery cycle. The quad ends up oscillating instead of recovering.

7-inch / heavy builds (900g+): Raise crash_recovery_rate to 120-140 and crash_recovery_time to 700. A 1kg quad has significant angular momentum when tumbling. Default settings may not have enough authority to arrest the rotation in time. Test over soft ground first — if it hits the ground before recovering, the rate is too low.

Cinewhoop (ducted, 400-600g): Cinewhoops have high drag from ducts. Lower crash_recovery_angle to 20-25 — the ducts amplify angular disturbance, so an impact that might not trigger on a 5-inch will definitely trigger on a cinewhoop.

Testing Crash Recovery Safely

You can’t test crash recovery by actually crashing (that defeats the purpose). Here’s the bench and flight test procedure:

Bench Test

Arm the quad with props off.
In the Motors tab, spin motors to 20% (simulating in-flight idle).
With your hand, violently shake the quad — simulate the angular acceleration of a branch strike.
Watch the motors. If crash recovery triggers, throttle will spike briefly as the FC attempts to “correct” the attitude, then return to 20%.
If nothing happens, your thresholds are too high or recovery isn’t enabled. Check get crash_recovery in CLI.

Flight Test

Fly in an open field at moderate altitude (50+ feet). Execute a deliberate maneuver that should trigger recovery:

Fly level at moderate speed.
Execute a snap roll to the right but intentionally over-rotate — keep the stick pegged so you tumbled past 360°.
The moment you feel the quad lose orientation, release the sticks.
If crash recovery engages, the quad will snap to level in ~300ms and hover.
If it doesn’t engage, lower crash_recovery_angle by 5 degrees and repeat.

Do this over tall grass. You will have a few uncontrolled descents while tuning. Better to land in grass than concrete.

What Pilots Get Wrong About Crash Recovery

Mistake #1: Leaving it disabled because “I want full control.” Crash recovery gives control back to you the moment the quad is level — typically 200-500ms. In that same half-second, your panicked stick inputs would have made the situation worse. Letting the FC save the quad for 300ms and then giving control back is not a loss of control — it’s intelligent triage.

Mistake #2: Confusing crash recovery with turtle mode. Turtle mode (flip over after crash) is for when you’re already on the ground. Crash recovery prevents you from getting there. They serve completely different purposes and both should be enabled. As covered in our turtle mode setup guide, turtle mode requires specific ESC protocol support. Crash recovery works with any ESC protocol and any Betaflight version 4.1+.

Mistake #3: Setting thresholds too low and getting constant false triggers. When crash_recovery_angle is set to 10-15°, aggressive freestyle — power loops, inverted yaw spins, Matty flips — will trigger recovery mid-trick. The quad suddenly snaps to level when you wanted to stay inverted. Find the lowest angle that never triggers during your normal flying style. For most pilots, that’s 30-35°.

Mistake #4: Not pairing crash recovery with a pre-arm safety configuration. Crash recovery can theoretically re-arm the quad in a dangerous orientation if it misjudges “level.” Always pair it with a two-stage arming setup that requires deliberate pilot action to re-arm after any disarming event. Our pre-arm safety configuration guide covers the full safety workflow.

⚠️ Regulatory Notice: The flight testing and configuration recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Crash recovery is a safety feature but does not substitute for proper airspace awareness, pre-flight checks, and adherence to local flight regulations. Always test new firmware features in controlled environments away from people and property.

For a visual demonstration of crash recovery triggering in real-world flight:

Setting up a fresh flight controller? The SpeedyBee F405 V4 comes preloaded with Betaflight 4.5, has native Bluetooth for field tuning via the SpeedyBee app, and includes dedicated pads for crash recovery-capable ESCs on all four corners. It’s the FC I reach for when building quads that I plan to push hard. Available at uavmodel.com.

Betaflight Crash Recovery Mode: Automatic Flip-to-Level After Impact — Configuration Guide — 2026