# Betaflight Crash Recovery Mode: Setup, Testing, and Race Day Scenarios
Crash Recovery is one of Betaflight’s most underappreciated features. When enabled, it automatically levels the quad and punches the throttle after detecting an impact — turning what would be a walk of shame into a mid-air recovery. This guide covers configuration, testing, and race-day strategy.
## What Is Crash Recovery?
Crash Recovery monitors gyro data for a sudden, extreme rotation that exceeds normal flight dynamics. When it detects a crash, it:
1. Disables the PID loop momentarily
2. Commands full motor output (or a configurable percentage)
3. Holds the quad level using accelerometer data
4. Gradually returns control to the pilot
| Normal Crash | With Crash Recovery |
|————-|——————-|
| Quad tumbles to ground | Gyro spike detected |
| Pilot disarms | Auto-level activates |
| Walk of shame | Quad recovers mid-air |
| Possible damage | Pilot resumes flying |
## Configuration
Enable Crash Recovery in Betaflight Configurator or via CLI:
“`
set crash_recovery = ON
set crash_delay = 0
set crash_recovery_angle = 10
set crash_recovery_rate = 100
set crash_time = 500
set crash_recovery_time = 100
set crash_dthreshold = 50
set crash_gthreshold = 400
set crash_limit_yaw = 200
“`
| Parameter | Function | Recommended Value |
|———–|———-|——————-|
| crash_recovery | Master enable | ON |
| crash_dthreshold | D-term spike threshold | 50 (lower = more sensitive) |
| crash_gthreshold | Gyro rate threshold (deg/s) | 400 |
| crash_recovery_angle | Max tilt during recovery | 10 degrees |
| crash_recovery_rate | Throttle recovery speed | 100 |
| crash_time | ms to hold crash state | 500 |
| crash_recovery_time | ms to return control | 100 |
| crash_limit_yaw | Max yaw rate during crash | 200 |
## Step 1: Sensitivity Tuning
The key to Crash Recovery is finding the right sensitivity. Too sensitive = false triggers during aggressive maneuvers. Not sensitive enough = real crashes go undetected.
### Test Procedure
1. Enable Crash Recovery
2. Perform the following maneuvers:
– Full-rate snap rolls (should NOT trigger)
– Quick flips at high rates (should NOT trigger)
– Light tap on a soft surface (SHOULD trigger)
3. If snap rolls falsely trigger: increase `crash_gthreshold` by 50-100
4. If light taps do not trigger: decrease `crash_gthreshold` by 50
## Step 2: Race Day Best Practices
### Pre-Race Configuration
For racing, reliability is critical. Use conservative settings:
“`
set crash_recovery = ON
set crash_dthreshold = 60
set crash_gthreshold = 500
set crash_recovery_angle = 15
set crash_time = 400
“`
Racers cannot afford false triggers during tight gates. A 15-degree recovery angle gives enough tilt to avoid the ground without feeling like the quad is fighting you.
### Freestyle Configuration
Freestyle pilots can use more aggressive recovery:
“`
set crash_recovery = ON
set crash_dthreshold = 40
set crash_gthreshold = 350
set crash_recovery_angle = 25
set crash_time = 600
“`
Freestyle crashes tend to be more violent and at higher altitude, so a longer recovery window and more aggressive leveling are beneficial.
## Step 3: Advanced Integration
### Crash Recovery + GPS Rescue
For long-range quads, configure Crash Recovery as the first line of defense and GPS Rescue as the backup:
“`
set crash_recovery = ON
set gps_rescue_allow_arming_without_fix = OFF
set gps_rescue_angle = 45
“`
If Crash Recovery fails to save the quad (e.g., it is too low), activate GPS Rescue manually on a switch to climb and return home.
### OSD Warnings
Add **CRASH FLIP** to your OSD. When it shows “CR,” Crash Recovery is actively engaged. This gives you real-time confirmation that the feature is working.
## Testing Without Crashing
The cleanest way to verify Crash Recovery works:
1. Arm the quad and hover at 2 meters
2. Give a sharp stick input that would simulate a collision (rapid roll + throttle cut)
3. The quad should auto-level and add throttle within 200ms
4. If it does not, lower `crash_gthreshold` in 50-unit increments
## Hardware for Reliable Recovery
Crash Recovery requires a fast gyro and responsive ESCs. The **UAVModel F7 Ultimate Stack** features an ICM-42688P gyro running at 8kHz with SPI connection — providing the sub-millisecond data that Crash Recovery needs for instant detection. Pair it with **Bluejay 48kHz ESCs** for the fastest motor response. Available at [uavmodel.com](https://uavmodel.com).