You’re 300 meters out, upside down in a field of knee-high grass, and your walk of shame is going to take 15 minutes each way. Turtle mode — also called flip over after crash — gets you airborne again in 5 seconds. Here’s how to set it up and avoid burning out a motor in the process.
What Turtle Mode Actually Does
Turtle mode selectively reverses individual motors to flip the quad back upright. When you activate it and move your pitch/roll stick, Betaflight commands specific ESCs to spin in reverse — the props push against the ground and flip the quad over. It requires bidirectional DShot protocol (DShot300 or higher) because the ESC needs to accept a direction-change command mid-operation.
Without DShot bidirectional, the ESC doesn’t know which direction the motor is spinning — it just sends pulses. Turtle mode needs the ESC to respond to a “reverse direction now” command, which only works with DShot and the bidirectional protocol enabled.
Step 1: Enable Bidirectional DShot
In Betaflight Configurator, go to the Motors tab. Set the ESC/Motor Protocol to DShot300 or DShot600 — any DShot variant works, but DShot300 is the sweet spot for compatibility. Then enable “Bidirectional DShot” in the Configuration tab under “Motor Protocol.”
Without bidirectional DShot, turtle mode will not work. The motors will twitch but won’t reverse. You’ll see the “TURTLE” mode indicator in the OSD, but nothing happens when you move the sticks.
Expected result: After saving and rebooting, you should see the RPM data from each motor in the Motors tab when you spin them manually. If RPM values show as 0 or error, bidirectional DShot isn’t working — check that your ESCs support it (BLHeli_S with JazzMaverick firmware, BLHeli_32, or AM32).
Step 2: Configure Turtle Mode in the Modes Tab
Go to the Modes tab in Betaflight. Add a range for “FLIP OVER AFTER CRASH” and assign it to an aux channel — I use the same momentary switch I use for pre-arm so I can’t accidentally activate it in flight.
Set the active range so the switch position corresponds to the armed+flip state. This should be a momentary switch, not a latching one. If you use a latching switch, you WILL forget it’s on, arm the quad, and watch it flip over instantly on the pad.
Troubleshooting note: If turtle mode activates but only one motor spins, check motor numbering in the Motors tab. Each motor must be mapped to the correct ESC output. Also verify that your Mode range is wide enough — if the slider only covers 50% of the switch range, turtle mode will flicker on and off.
Step 3: Set Turtle Mode Motor Power Limit
This is the setting that prevents motor burnout. In the CLI, set:
set crash_recovery = ON
set crashflip_motor_percent = 55
set crashflip_expo = 35
save
crashflip_motor_percent limits the power sent to motors during turtle mode. Start at 45 for 5-inch builds, 35 for whoops, 60 for 7-inch. If the quad won’t flip over, increase by 5. If the motors scream and the ESCs get hot, decrease by 5.
crashflip_expo adds an expo curve around center stick so you don’t accidentally full-throttle the motors when you just want a gentle nudge. 35 is a good starting point.
What happens if you get this wrong: With motor percent at 100, a stalled motor draws locked-rotor current — easily 30-40A through windings that can handle 20A continuous. The enamel on the windings burns off within 2-3 seconds, creating a phase-to-phase short. That motor is now a paperweight.
Turtle Mode Configuration Quick Reference
| Setting | Whoop (1S-2S) | 3-inch | 5-inch | 7-inch / Heavy |
|---|---|---|---|---|
| ESC Protocol | DShot300 | DShot300 | DShot600 | DShot600 |
| crashflip_motor_percent | 30-35 | 40-45 | 50-55 | 55-65 |
| crashflip_expo | 25 | 30 | 35 | 40 |
| Motor Idle (DShot) | 4.5% | 5.0% | 5.5% | 6.0% |
| Max Flip Attempts | 5 | 5 | 3 (heat) | 2 (heat) |
If the quad won’t flip after the max attempts, walk. A motor replacement costs more than the walk.
What Pilots Get Wrong About Turtle Mode
Mistake 1: Using turtle mode when a prop is physically blocked.
The consequence: If a prop is wedged against a branch, rock, or packed into mud, commanding that motor to spin in turtle mode stalls it instantly. The ESC delivers full locked-rotor current to a winding that can’t move. Smoke in 2 seconds.
The fix: Before attempting turtle mode, disarm and look at the video feed. Are props obstructed by something solid? Disarm, walk 50 feet closer, try again. A partially-obstructed prop will move a little but not flip the quad — if you see the quad shake but not roll after two attempts, walk.
Mistake 2: Holding the stick for too long in one direction.
The consequence: The motors run at crashflip_motor_percent continuously as long as you hold the stick. Even at 55%, that’s enough to heat ESCs and motors past safe temperatures in 5-10 seconds of sustained load on the ground with no cooling airflow.
The fix: Use short pulses — 1-2 seconds, then release. Let the quad settle. If it didn’t flip, try a different stick direction. Flip attempts should be brief nudges, not sustained burnouts.
Mistake 3: Assigning turtle mode to a latching switch.
The consequence: You land, flip the switch, pack up, and forget it’s engaged. Next session, you plug in, arm, and the quad flips itself over on the pad — smashing props, possibly damaging motors, and definitely embarrassing you at the field.
The fix: Use a momentary switch, or add a pre-arm condition. My setup: turtle mode is on the same momentary switch as pre-arm — I must hold the button down to activate turtle mode. The moment I release, it disarms. No accidental activation possible.
Mistake 4: Not verifying bidirectional DShot actually works before relying on turtle mode.
The consequence: You crash upside down, toggle turtle mode, and nothing happens. The OSD says “TURTLE” but the motors won’t reverse. You’re walking 400 meters through a soybean field because you never bench-tested it.
The fix: After setup, test turtle mode on the bench. Arm, switch to turtle mode, and move the sticks (props OFF). You should see the motors spin — some forward, some reverse depending on stick direction. If nothing happens, your ESC protocol or bidirectional DShot config is wrong.
⚠️ 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. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
Beyond Turtle Mode: DShot Beacon for Crash Location
Turtle mode requires DShot, and DShot gives you another tool: the ESC beacon. When the quad is disarmed for a configurable period (default 30 seconds), the ESCs pulse the motors at a specific frequency, producing an audible tone. This helps you find a quad in tall grass or a tree.
As we explained in our self-powered beeper guide, a dedicated beeper with its own battery is more reliable than ESC beacon (which stops if the main battery ejects), but DShot beacon is zero-weight and always available.
Set beacon strength and delay in CLI:
set beeper_dshot_beacon_tone = 3
set beeper_dshot_beacon_volume = 150
The uavmodel BLHeli_32 45A 4-in-1 ESC supports full bidirectional DShot600 with turtle mode, RPM filtering, and DShot beacon — compatible with all Betaflight 4.4+ builds.