FPV crash video recovery begins with an inventory rather than a rescue, because a quad in flight usually writes to three devices at once and they do not fail together. The onboard action camera, the DVR in your goggles, and the flight controller’s blackbox log all record different things, and the one that is most likely to survive a hard impact is not the one you would guess.
So the first question after a crash is not “is the card still readable” but “which recordings exist at all”. A pilot who answers that question before touching anything recovers more footage than one who pulls the onboard camera’s card immediately and starts scanning.
Three Places a Flight Gets Recorded
Every FPV flight generates up to three parallel records, and each has a different failure profile after impact.
| Source | What it records | Quality | Survives a hard impact? | Typical card |
|---|---|---|---|---|
| Onboard action camera | Full-resolution stabilized video, 2.7K to 5.3K | Highest | Depends: often ejected, sometimes crushed | microSD in the camera |
| Goggles DVR | Exactly what the pilot saw, including signal breakup | Lowest | Very likely: it is on the pilot’s face | microSD in the goggles |
| Air unit internal storage | The transmitted feed, when a card is absent or full | Low to moderate | Only if the air unit is undamaged | Soldered eMMC or onboard card |
| Flight controller blackbox | Gyro, RC input, battery, GPS, timing | No video | Usually, if stored on flash | Onboard flash or a card on the FC |
The onboard camera is the only source of publication-grade footage, which is why it gets all the attention. It is also the most exposed: it is strapped to the top of the frame or, on a “naked” conversion, mounted with minimal protection to save weight. A hard impact can eject it, shear its mount, crack its lens, or crush its housing. When it leaves the airframe, it lands somewhere else, and the search area for a camera is larger than the search area for the quad.
The DVR is the opposite case in every dimension. Its resolution is low, sometimes barely above analog noise, and it captures exactly the feed the pilot received, including every dropout. But it lives in the goggles, physically separated from the aircraft, and it keeps recording until the goggles lose signal or the pilot stops it. When a quad goes into water, into a tree canopy, or over a ridge and is never recovered, the DVR footage on the pilot’s face is the only surviving record of the flight. Our page on recovering FPV DVR footage covers the file layouts and the practical limits of that source.
Why the Card Comes Out Last, Not First
The instinct after a crash is to get to the card. The correct sequence puts that step at the end of a short list.
Do not power the quad on. This instruction matters more in FPV than in any other drone category. A crashed freestyle quad has a deformed LiPo pack, and a damaged lithium cell that reconnects to a load can vent or ignite. Beyond the fire risk, a booting flight controller mounts its storage, and a camera left mounted on the frame may also be powered and may run a file-system repair on its card. That repair rewrites the structures holding your deleted or unclosed data.
Disconnect and remove the battery before touching anything else. On most builds the battery strap and the XT30 or XT60 connector are the two things you can access without tools, and both should be handled with the quad sitting on the ground, not held in a hand.
Photograph the wreck before disassembling it. For a race incident report or an insurance claim, the position of the camera, the state of the arms, and whether the card was still in its slot are all worth documenting.
Only then remove cards, starting with the one that is easiest to reach and hardest to damage. The goggle card first, because it is in your hand and completely undamaged. The camera’s card second, after the camera has been found and inspected.
The reason for that order is that a card pulled from a deformed camera with grit or a bent housing can be damaged during removal, and there is no benefit to rushing it. The DVR copy is already safe.
The Rescue Order After Impact
Once every device is powered down and the cards are out, the copy order determines how much you end up with.
| Priority | Source | Why it comes here | Watch for |
|---|---|---|---|
| 1 | Goggles DVR card | Undamaged by the crash, so it is your guaranteed fallback | Low bitrate; a full copy takes minutes |
| 2 | Onboard camera card | Highest quality, only copy of the good footage | Last clip missing its index; camera may have been ejected |
| 3 | Air unit internal storage | Only exists on some radio systems, and only if no card was recording | Requires the air unit to still enumerate over USB |
| 4 | Flight controller blackbox | No video, but proves what happened and when | Onboard flash needs its own extraction tool |
Start with the DVR because it is cheap insurance. Copy the whole card, including the low-resolution files you do not intend to publish, and keep that copy untouched. If the onboard camera’s card turns out to be unreadable, the DVR copy is what tells you what the flight looked like and where the quad came down.
Then handle the camera’s card, which is almost always a two-part job. The clips written before the crash copy normally. The clip that was open when the impact occurred is written at full file size and will not play, because the camera never wrote the index that closes a video file. That clip is usually the crash itself, which makes it the single most valuable file on the card and the one most likely to need repair rather than recovery. A hard impact that dislodges the card produces the same outcome as a power cut, and the mechanics are the same as any power loss during recording.
The blackbox log belongs last, and it is a different kind of artifact. A Betaflight blackbox file records gyro samples, motor outputs, RC commands, and battery voltage at up to several kilohertz, which lets you reconstruct the failure with more precision than video can: whether a motor desynced, whether a prop failed, whether the battery sagged into a brownout. If the log lives on onboard flash rather than on a card, extraction needs the flight controller to be alive and connected, and the general procedure is the same one described in our guide to extracting drone flight logs.
What a Crash Does to a Card That Stays Inside
If the card stayed in the camera through the impact, three things can be true and they are often confused with each other.
The card is fine and the last clip is unclosed. By far the most common outcome. Every earlier clip plays; the final one needs its index rebuilt from the elementary stream.
The camera lost power mid-write and left a truncated frame. Less common, and it shows as a file that plays until the end and then either freezes or ends a few frames early. The data that was written is valid.
The card itself was damaged. Rare in a camera-mounted setup, common in naked conversions where the card’s shell bears the load of the impact. A cracked or bent card is a laboratory case, and the diagnosis path is the same one described in our guide to crash damage to a drone’s storage.
One FPV-specific detail is worth internalizing. An action camera that has been stripped to a naked board has had its heatsink and its thermal mass removed, so the card runs hotter than it would in a stock housing. Overheating does not corrupt existing files, but it does cause recording to stop early, and a pilot who blames the crash for a short clip sometimes finds the camera had already stopped recording during the run.
If several clips need to be joined back into one continuous file — common when a long freestyle session was chaptered onto the card — do that after recovery, not before. The procedure is in our guide to reassembling chaptered video. If the camera is not a GoPro, the file layout differences between brands are covered in our overview of action camera brands and their recovery quirks.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive. A card recovered from salt water or one that no longer enumerates is outside the reach of any software.
Frequently Asked Questions
My quad went down in water and was never recovered. Is the flight footage gone?
Not entirely. The goggle DVR recorded the same feed the pilot watched, and those goggles were never near the water. The footage is low resolution and shows every dropout, but it covers the flight end to end and is often the only surviving record.
Why is the last clip from a crash unplayable when earlier clips are fine?
The final clip was still open when the impact cut power or dislodged the card, so the camera never wrote its closing index. The frames are in the file. It needs repair, not recovery, and a repaired clip typically loses only the last second or two.
Should I power the quad on after a crash to see what still works?
No. A deformed battery can vent or catch fire when reconnected, and a booting flight controller mounts its storage and may run a file-system repair over your recoverable data. Remove the battery first, and read cards in a standalone reader.
Is the camera’s card or the goggles card more important?
The camera’s card holds the publishable footage and should be recovered first if both are readable. The goggles card matters more as insurance: it is undamaged by the crash and it is the only copy when the aircraft is never recovered, so copy it before you start experimenting with anything else.