A commercial pilot in Singapore was flying a resort promotional shoot when a gust of wind sent his drone into a palm tree. The drone survived with a cracked propeller. The footage did not — at first.
The problem
The last flight’s file — a 12-minute 4K/60p MP4 from a DJI aircraft — showed a healthy file size (about 6.5 GB) but refused to play beyond the first two seconds. Scrubbing jumped erratically. Classic truncated-index corruption: the drone was still writing when it hit the tree, and the MP4’s moov atom (the index that tells players where every frame lives) never got written.
What we did
- Received the file within the half of an hour via Google Drive link.
- Scanned the raw stream and located every video keyframe across all 6.5 GB.
- Rebuilt the moov atom with correct frame offsets, durations.
- Sent back a playable preview the same evening — about 2 hours after first contact.
✓Result
All 12 minutes recovered — full 4K/60p quality, H.265 stream untouched (remuxed, not re-encoded), audio in perfect sync. The client delivered the resort video on schedule.
Why drone footage corrupts so easily
Drones are flying computers that write video while vibrating, flying and balancing power between motors and CPU. The three most common corruption causes we see:
- Crash or hard landing — the write is interrupted mid-stream, index never finalized (this case).
- Battery death — the drone prioritizes staying airborne over finishing the file correctly.
- Full SD card during flight — recording continues into a card with no space left, producing truncated files.
The good news: because drones write sequentially with frequent keyframes, MP4 recovery rates are very high even in these cases.
Takeaways
- If a crash happens, power the drone off and pull the card — don’t try to replay the clip on the controller first, and don’t format.
- Always fly with a card that has plenty of free space.
- Land with battery to spare; the last 10% of a drone battery is where files go to die.