Turtle mode flips you over after a crash. Crash Recovery mode catches the crash before you hit the ground. This is the difference between walking 20 feet to flip your quad and walking 200 yards to pick up pieces. Most pilots enable it, test it once over tall grass, and never tune the settings — then wonder why it doesn’t work when they actually need it.
Betaflight Crash Recovery: Configuration That Actually Works
Step 1: Understanding What Crash Recovery Does (and Doesn’t Do)
Crash Recovery triggers when Betaflight detects an impact exceeding a G-force threshold while disarmed. The flight controller auto-arms, levels the quad using accelerometer data, applies a brief throttle burst, and levels out. It’s not GPS Rescue — it doesn’t know where “up” is relative to the ground. It knows where “up” is relative to the gyro, and that’s enough.
The key constraint: Crash Recovery works only within 2 seconds of disarm. After 2 seconds, the mode times out and won’t trigger. This is intentional — if you’ve been falling for more than 2 seconds, you’re too low for recovery to matter, and the mode shouldn’t auto-arm a quad that’s already on the ground.
Step 2: Enable and Configure in Betaflight Configurator
Navigate to the Modes tab and add a mode range for “CRASH RECOVERY” on the same AUX channel as your arm switch, but inverted. When the arm switch is LOW (disarmed), Crash Recovery is active. When armed, it’s disabled.
In CLI, the critical parameters:
set crash_recovery = ON
set crash_delay = 0 # ms before recovery triggers after impact
set crash_recovery_rate = 100 # deg/s_yaw recovery rate
set crash_gthreshold = 2.5 # G-force threshold to trigger (2.0-3.5)
set crash_time = 500 # ms of stabilized flight after trigger
set crash_recovery_angle = 10 # degrees from horizontal to target
set crash_dthreshold = 10 # degrees/s deviation from expected gyro
What each setting does:
– crash_gthreshold: The G-force required to trigger recovery. At 2.5G, a moderate impact (dropping 3 feet onto grass) triggers it. At 3.5G, only hard impacts activate. Start at 2.5 and increase if false triggers occur during aggressive landings.
– crash_recovery_angle: Target angle in degrees. Lower values (5-10) produce a flatter recovery. Higher values (20-30) are more tolerant but may not level completely.10 is the sweet spot.
– crash_dthreshold: Degrees per second deviation that constitutes a “crash.” At 10, the quad must deviate 10°/s from expected attitude to count. Lower values (5) trigger on minor instability; higher values (20) might miss crashes.
– crash_time: How long the FC maintains stabilized flight after triggering. 500ms is enough to level from any orientation. 200ms works for flat crashes but not inverted ones.
Step 3: Verify Recovery on the Bench (Critical)
Before testing in the air, verify the logic works:
- Plug in USB, connect to Betaflight Configurator.
- Go to Motors tab, enable “I understand the risks.”
- Spin up motors to 20% (no props installed).
- Arm, then disarm.
- While disarmed, manually jerk the flight controller sharply (simulating an impact).
- The motors should briefly spin up if Crash Recovery triggers.
If nothing happens: check that crash_recovery = ON, that your mode range is correctly mapped, and that you’re within the 2-second disarm window. The mode will NOT trigger if you’ve been disarmed for more than 2 seconds.
Step 4: In-Field Testing — Start Low, Start Over Grass
First test: Fly 10 feet above tall grass. Disarm. Let it fall. Recovery should catch it within 0.5 seconds and stabilize at roughly 10 degrees from horizontal. Second test: fly inverted at 20 feet, disarm, watch it right itself. Third test: fly aggressively into a soft crash — the quad should recover before ground contact.
If recovery oscillates: reduce crash_recovery_rate to 50. If it doesn’t level fast enough, increase to 150. If it triggers during intentional aggressive landings, raise crash_gthreshold to 3.0.
Crash Recovery vs Turtle Mode: Parameter Comparison
| Feature | Crash Recovery | Turtle Mode |
|---|---|---|
| Trigger | Automatic (G-force detected) | Manual (AUX switch) |
| Disarm Required | Yes (must be disarmed) | Yes (must be disarmed) |
| Time Window | 2 seconds after disarm | No time limit |
| Motor Action | Auto-arms, levels, brief thrust | Reverse direction on AUX-selected motors |
| Purpose | Mid-air recovery before impact | Flip over after landing upside-down |
| Altitude Required | 5+ feet for effectiveness | 0 feet (on ground) |
| Gyro Dependence | Requires accelerometer | Gyro only |
| Risk of Damage | Low (motors at controlled RPM) | Medium (reversed motors can dig into ground) |
| Configuration Complexity | Low (5 CLI parameters) | Low (enable mode, set motor directions) |
Common Crash Recovery Mistakes
Mistake 1: Expecting Crash Recovery to work from any altitude. This mode is designed for mid-air crashes at 10+ feet. At 3 feet, by the time the FC detects the impact, processes the trigger, arms, levels, and spools motors, you’ve already hit the ground. Recovery from below 5 feet is pure luck — not a configuration failure.
Mistake 2: Setting crash_gthreshold too low. At 1.5G, every aggressive throttle chop or rapid descent triggers the mode. The quad auto-arms mid-flight when you’re still holding the radio. That’s dangerous. Start at 2.5 and tune upward.
Mistake 3: Forgetting that Crash Recovery requires the accelerometer to be enabled. If you’ve set acc_hardware = NONE to save CPU cycles or flash space, Crash Recovery cannot level the quad. It’ll arm and apply throttle but won’t know which way is up, making the situation worse. Enable the accelerometer or don’t use this feature.
Mistake 4: Running Crash Recovery and Turtle Mode on the same AUX channel. Turtle mode requires disarmed state and overlapped motor control. Crash Recovery also requires disarmed state. If both are active on the same channel, the FC can’t distinguish which you want. Put them on separate AUX channels or configure Crash Recovery to trigger from the arm switch exclusively.
Mistake 5: Not setting crash_time high enough for inverted crashes. An inverted quad needs roughly 300ms just to rotate to upright. With crash_time = 200, recovery cuts out mid-rotation and the quad drops sideways. 500ms gives the FC time to rotate, level, and stabilize before the mode times out.
⚠️ 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. Crash Recovery mode is an emergency safety feature — not a replacement for maintaining safe distance from people and property. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
As we covered in our Betaflight GPS Rescue setup guide, Crash Recovery pairs well with GPS Rescue for a layered failsafe strategy. See our turtle mode configuration guide for the companion feature that handles ground recoveries.
For pilots building crash-resistant quads, the uavmodel GEPRC Mark5 frame features 6mm replaceable arms and a CNC aluminum cage — it survives the crashes that Crash Recovery can’t catch, and the arm-swap takes 3 minutes trackside.