Upload the blackbox log from your crash and find out why — and how to prevent it. Free.
Log in to analyze your crash — free
One free analysis a month; unlimited with a subscription.
Log in / Sign upAlmost every “out of nowhere” crash leaves its cause in the blackbox. Here are the most common ones, what each looks like in the log, and how to stop it happening again.
Desync is the most common reason a quad suddenly flips and falls. The ESC loses track of where the motor is, so one motor keeps getting a throttle command but stops spinning — its RPM telemetry drops to zero while the others keep going. In the blackbox you see the motor output stay high while its eRPM collapses, and the gyro on that axis spikes as the quad rolls. It is usually triggered by hard throttle changes, worn bearings, or marginal ESC timing. Fixes: update ESC firmware, raise motor_idle slightly, run bidirectional DShot with RPM filtering, and resolder any cold joints.
If every motor stops at once and the quad drops straight down without spinning, it is almost always power loss. The flight controller browned out — the voltage sagged below what it needs and the log simply ends mid-flight with a voltage cliff. Causes are a tired or under-C-rated battery, a cracked XT60 or solder joint, or a missing capacitor letting voltage spikes through. Fixes: test the battery under load, reflow the power connector, add a low-ESR cap on the ESC power pads, and keep current draw within the pack’s rating.
When the radio link drops, Betaflight enters failsafe and (by default) cuts the motors so the quad falls. The blackbox flags this clearly: rxSignalReceived goes false and failsafePhase changes before the motors stop. This is a link problem, not a tune problem — check antenna placement and damage, watch RSSI/LQ on your OSD, raise TX power, and set a sensible failsafe stage.
A prop strike or extreme rotation can push the gyro past its measurement limit (around 2000°/s). When it saturates, the flight controller can no longer tell how fast the quad is rotating and it spins out — the classic uncontrolled yaw spin. The blackbox shows the gyro pinned at its limit. Enable gyro_overflow_detect, soft-mount the FC, and inspect for the prop damage that usually starts it.
Lose a prop or a motor and that corner stops making thrust, so the other three saturate trying to hold the quad level before it tips and falls. In the log, one motor’s RPM drops while the rest peg to maximum. This is purely hardware: check that props are intact and screwed down, inspect motor bearings and bells, and make sure nothing has vibrated loose.
Sometimes the tune itself is the culprit: a growing oscillation builds until the quad shakes itself out of the air. The blackbox shows gyro amplitude climbing in the seconds before the fall. This is the one cause you fix with tuning rather than hardware — lower P/D where it oscillates, tighten filtering, or just upload the log to get safe recommended settings.
Not sure which one? Upload your log above for an answer in seconds. To make the quad more stable and less crash-prone at the root, read the complete FPV tuning guide, or upload a log and tune. For the common propwash and hot-motor issues, see fixing propwash and motor temperature & tuning.
The most common causes are ESC desync, power loss (brownout), radio signal loss / failsafe, gyro overflow, or a mechanical failure like a thrown prop. Your blackbox log usually shows which one — that is what this analyzer reads for you.
The Betaflight blackbox log (.bbl or .bfl) from the flight that crashed — exported from Betaflight Configurator, or pulled off the SD card. Logging must have been on during the crash.
Yes — crash analysis is free. If the cause turns out to be a tuning problem, you can re-tune with FPVTune; for hardware causes we just tell you what to check.