Drone crash data recovery starts with one fact that is easy to lose sight of in the moment: your footage is not on the aircraft. It was written to the card before the impact, and the card is a self-contained device that does not need the drone to be read. A drone that will not power on after a crash says nothing about whether the video survives. It says the airframe is damaged.
That also means the wrong first move is the one most pilots make. Powering the aircraft back on to “see if it still works” is the single most dangerous action available, because a booting drone mounts the card and its firmware may attempt to repair a file system that currently holds every recoverable block exactly where it needs to be.
What Actually Happens at the Moment of Impact
Impact affects storage along three distinct paths, and the correct handling differs for each. Identifying which one you have takes about two minutes and decides everything that follows.
| Path | What happened | Card readable in a computer? | Where the data stands |
|---|---|---|---|
| One: card dislodged | Card popped out of the slot by shock, or seated but momentarily disconnected | Usually yes, once reseated properly in a reader | Data intact; the final clip may lack its index |
| Two: card physically damaged | PCB cracked, shell bent, contacts torn, or the card is split along a layer | No | Laboratory work; software cannot reach it |
| Three: card intact, aircraft destroyed | Airframe and main controller dead, card unharmed in its slot | Yes, once removed | Data intact; the aircraft is irrelevant to access |
| Four: card submerged in water or mud | Liquid entered the airframe or the card’s shell | Not before drying | Depends on water type and time; treat as urgent |
The table has a fourth row because a crash rarely involves impact alone. Drones crash into water, wet grass, sand, and snow, and the liquid often does more damage than the impact. The tell is whether the aircraft was recovered wet; if it was, the handling rules change entirely, and the specifics are covered in our page on water-damaged drone cards.
Path One: The Card Was Knocked Loose
The card slot holds a microSD card with spring tension and friction, and it takes surprisingly little shock to interrupt that contact. When the connection breaks mid-write, the recording stops without closing.
The card itself is almost always fine, and it will read normally in a card reader. What you will find is that the last clip exists at the correct file size and will not play, because a video file needs an index that is written when recording stops cleanly. No clean stop, no index. The frames are in the file; only the directory at the front of it is missing.
Two situations produce a variation on this. If the card popped fully out of the slot and landed inside the airframe or in the grass, it may have collected grit on its contacts, which reads as an intermittent connection or a card error rather than as a data problem. Inspect the contacts before inserting it into anything, and clean them with isopropyl alcohol and a lint-free swab if they look contaminated. If the card is still seated when you recover the aircraft, do not pull it out with the battery installed and the drone powered on.
An apparently intact card that produces a card error or an unreadable file system is worth a check against the card-not-detected decision tree, which separates a card problem from a reader or driver problem before you spend time on a scan.
Path Two: The Card Was Crushed or Cracked
Drones put the card in one of the more exposed locations on the airframe — usually beside the battery bay, and on some models inside the gimbal camera housing. A hard impact can bend the card’s plastic shell, crack the printed circuit board inside it, tear a contact pad, or, in the worst case, split the card along one of its internal layers.
Physical damage is where software stops being relevant. The card is a package containing a controller and one or more NAND dies bonded to a substrate. If that substrate is cracked, the electrical traces between the controller and the dies are broken, and no amount of scanning from a host computer can bridge them. The data is very likely still stored in the NAND cells — charge does not disappear because the package broke — but reading it requires removing the dies and reading them directly, which is laboratory work with a clean bench and specialized hardware.
| Damage seen | Software recovery possible | Realistic route |
|---|---|---|
| Scratched contacts, no shell damage | Yes | Clean contacts and read normally |
| Bent or lifted contact pad | No | Laboratory re-soldering to a donor shell |
| Cracked PCB or split shell | No | Chip-off NAND reading |
| Card snapped in half | No | Chip-off, with the caveat that a fracture through the die itself is unrecoverable |
| Card intact, exposed to salt water | No, until professionally dried and cleaned | Laboratory decontamination first |
The distinction that matters for a decision is whether the card is electrically continuous. If a computer sees the card at all — if it appears in a device list, even as an unknown device or an unformatted volume — then the controller is alive and there is a path forward. If the card produces nothing on multiple known-good readers, the damage is between the contacts and the controller, and our guide to physically broken card emergencies sets out how to package and ship it.
Path Three: The Card Is Fine and the Aircraft Is Not
This is the most common outcome of a bad crash, and the most misunderstood. The drone takes damage to a motor, arm, or gimbal, the main controller or flight electronics are destroyed, and the aircraft will never fly again. The card, sitting in its slot, is untouched.
In this case the aircraft has no bearing on your data at all. Remove the card, put it in a reader, and it behaves exactly as it would after a normal flight. The footage that was written before the crash is fully recoverable, and the only clip at risk is the one being recorded when the impact occurred.
There is one variant that changes the picture: drones that store footage on internal memory rather than, or in addition to, a removable card. Compact models in several DJI lines and some competitors record to soldered storage when no card is present. If your drone crashed with footage only on internal storage and the aircraft no longer powers on, that footage cannot be reached without repairing the aircraft or desoldering the memory, and it belongs to a repair or recovery specialist rather than to a card-level tool.
It is also worth knowing what else survives. DJI aircraft write flight logs to the app and to the aircraft itself, recording position, altitude, battery state, and the moment of failure. Those logs are not video, but for insurance claims and incident reports they carry the same evidential weight, and our page on DJI flight log recovery covers where they live and how to extract them.
The Order of Operations After Impact
Sequence matters more than tooling. Working in the wrong order can turn a fully recoverable card into an unrecoverable one.
- Do not power the aircraft on. A booting flight controller mounts the card, may run a file-system check, and can rewrite the very structures recovery depends on. It is also a genuine fire risk if the battery was deformed by the impact.
- Photograph the scene and the aircraft as found. For insurance and incident reporting, the state of the airframe and the card’s position are evidence.
- Remove the battery before removing the card. On most airframes the card slot is close enough to the battery bay that pulling the card with power applied risks a short across the contacts.
- Take the card out, inspect it, and read it through a USB card reader rather than through the aircraft. Even a functioning drone should not be the reader after a crash; its USB path routes data through the same damaged electronics.
- Copy what is readable before scanning for what is not. Preserve the intact files first, then run a scan for deleted and formatted data.
- Treat the final clip separately. It is a repair case, not a recovery case, and it should be handled after the intact files are safely copied elsewhere.
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. For a card that does not enumerate, or one that was physically broken or submerged in salt water, no software applies, and our comparison of software recovery versus a data recovery lab explains how to judge which one you need.
Frequently Asked Questions
My drone crashed and will not turn on. Is the footage gone?
Almost certainly not. Video is written to the card during flight, and the card can be read in any card reader without the aircraft. If the crash destroyed the airframe but left the card intact, the recorded footage is fully accessible. Only internal-memory footage depends on the aircraft powering up.
Why is the last clip after a crash unplayable when the earlier ones are fine?
The final clip was open when the impact cut power or interrupted the card connection, so it never received the index that a player needs to navigate it. The video frames are still in the file. It needs repair rather than recovery, and repaired clips often lose only the last second or two.
Should I turn the drone on to check whether the card still works?
No. Booting the aircraft mounts the card, and the firmware may attempt a file-system repair that rewrites the structures holding your recoverable data. Use a card reader instead, and only after removing the battery and inspecting the card.
Does the crash damage the video files that were already closed?
Not if the card itself survived. Closed files live in stable blocks that the impact does not disturb. Damage after a crash comes from the card being dislodged or broken, from water, or from the aircraft being powered on afterward — not from the impact shaking existing data loose.