Betaflight Crash Recovery Mode: Flip Over After Crash Detection and Auto-Stabilization — 2026 Guide

You clip a ghost branch at 40mph. The quad tumbles, the video feed spins, and you instinctively disarm. Then you realize it landed right-side-up in a field 200 meters away. If you’d waited half a second, Crash Recovery could have saved it. This feature — introduced in Betaflight 4.3 and refined in 4.5 — detects impacts and autonomously levels the quad. It’s saved my quads from walks of shame at least 30 times. Here’s how to configure it properly.

How Crash Recovery Works

Crash Recovery monitors the gyro for a sudden, extreme angular rate change that exceeds normal flight dynamics. When it detects a crash signature — accelerations above 1800 deg/s sustained for multiple consecutive samples — it temporarily switches from the pilot’s flight mode to ANGLE mode with aggressive leveling gains, commanding the quad upright regardless of stick position.

The critical distinction from turtle mode: Crash Recovery activates while the quad is still airborne or immediately upon impact, using remaining prop momentum to right itself. Turtle mode requires you to be on the ground, disarmed, with props stopped, and then re-armed in a specific stick position to flip. Crash Recovery happens in milliseconds, automatically.

Step-by-Step Configuration

Step 1 — Enable and Set Sensitivity

set crash_recovery = ON
set crash_dthreshold = 40        # Degrees/second deviation threshold
set crash_gthreshold = 450       # Gyro rate threshold (deg/s)
set crash_setpoint_threshold = 350  # Setpoint deviation threshold
set crash_time = 500             # Recovery time in ms
set crash_delay = 0              # Delay before recovery (ms, 0 = instant)
set crash_recovery_angle = 10    # Max angle for recovery to consider successful
set crash_recovery_rate = 100    # Recovery rate (deg/s, higher = faster flip)
set crash_limit_yaw = 200        # Max yaw rate before crash detection disabled

The key parameters are crash_gthreshold, crash_dthreshold, and crash_time. crash_gthreshold defines how fast the gyro must be spinning before recovery triggers — 450 deg/s is a good universal starting point. crash_dthreshold checks the rate of change of gyro — a crash produces a near-instantaneous acceleration spike that is distinct from aggressive pilot inputs. crash_time is how long the ANGLE-leveling runs: 500ms (half a second) is enough to right most 5-inch quads.

Step 2 — Tune for Your Build

Lighter quads need higher sensitivity. Heavier quads need lower sensitivity:

Step 3 — Test Without Props

Remove props. Arm the quad with the transmitter. Hold the quad in your hand, throttle at zero, then simulate a crash by suddenly rotating the frame sharply — like whipping it 90 degrees in pitch or roll. The motors should briefly spin up in a leveling response and then stop. If they don’t trigger, lower crash_gthreshold by 50 and test again. If they trigger during normal bench handling (picking up the quad, tilting it), increase crash_gthreshold by 50.

Step 4 — Set Crash Recovery Angle and Rate

crash_recovery_angle (default 10) determines the maximum tilt angle that counts as “leveled” for recovery to succeed. At 10 degrees, the quad only needs to get close to level for the recovery to be considered complete. If your quad tends to end up at a 45-degree tilt after recovery, increase this to 25 — recovery won’t fight for perfect level and will end sooner, saving battery and preventing ground contact.

crash_recovery_rate (default 100) controls how aggressively the quad tries to level. Higher values produce snappier recovery but can overshoot and oscillate. For 5-inch builds, 100–150 works. For whoops, 200 produces a clean flip. For heavy 7-inch quads, stay at 80–100 — excessive rate on a heavy quad causes bounce-back.

Crash Recovery vs Turtle Mode: When to Use Each

The two features complement each other. Enable both. Crash Recovery catches the ones you can save mid-air; Turtle Mode handles the ones that settled.

Common Mistakes & What Most Pilots Get Wrong

Mistake 1: Disarming instantly on every crash. This is the hardest habit to break after years of flying. The instinct to “disarm to save the ESC” is correct for a quad pinned against an obstacle at full throttle, but for a mid-air clip where the quad is tumbling freely, waiting 0.5 seconds for Crash Recovery to attempt a save costs nothing and wins you a fly-away instead of a walk. Train yourself: count “one-one-thousand” after impact before disarming.

Mistake 2: Setting crash_recovery_rate too high. I set this to 200 on a 5-inch and watched the quad overshoot level, oscillate, and drive itself into the ground with more energy than the original crash. Match the rate to the frame’s rotational inertia. Bigger, heavier quads need slower recovery rates. 100 is the safe starting point for everything.

Mistake 3: Leaving crash_limit_yaw at default without testing. The default limits crash detection when yaw rate exceeds 200 deg/s — this prevents false triggers during fast yaw spins. But if you fly freestyle at 600+ deg/s yaw rates, Crash Recovery is essentially disabled during aggressive yaw maneuvers because your normal flight exceeds the limit. You clip a branch mid-yaw-spin and recovery doesn’t fire. Set crash_limit_yaw above your maximum intentional yaw rate (or set it to 0 to disable the yaw limit entirely).

Mistake 4: Assuming Crash Recovery works after the quad has settled. Once the quad is stationary on the ground, Crash Recovery cannot activate — it requires the crash impact signature (rapid gyro acceleration) to trigger. If you disarmed, the quad dropped, and is now sitting still upside down, Crash Recovery will not fire. This is turtle mode territory.

⚠️ Regulatory Notice: Crash Recovery and turtle mode both involve spinning motors after an impact, which can create fire hazards in dry vegetation and safety risks if the quad is near people or property. In 2026, multiple jurisdictions including EASA (EU) and CAA (UK) classify autonomous recovery maneuvers as part of the aircraft’s operational safety system, requiring them to be tested and documented. Pilots flying under FAA recreational exemption should note that autonomous flight behaviors like Crash Recovery, while safety-enhancing, constitute an onboard automated system — ensure your aircraft’s Remote ID status remains compliant after any Betaflight CLI modifications.

See Also

Crash Recovery is one tool in the broader reliability picture. For what comes after a crash, our post-crash rebuilding guide walks through damage assessment and repair order. If you’re landing upside down frequently, our turtle mode setup guide covers DShot beacon configuration. And for preventing crashes in the first place, the pre-flight checklist catches mechanical issues before they become airborne problems.

Crash Recovery works best on a flight controller with a clean gyro signal — noise and vibration can cause false triggers or missed detections. The SpeedyBee F405 V4 flight controller has an ICM-42688-P gyro with a dedicated vibration-isolated mounting scheme that delivers the cleanest gyro trace I’ve seen at this price point. All four of my 5-inch builds run this board.