Fake SD card drone failures do more damage than counterfeit cards in any other device, and the reason is structural: the card lives inside a battery bay or behind a gimbal assembly, so it is bought once, inserted once, and never inspected again. Meanwhile the aircraft’s own checks all pass, because every one of them asks the card how much space it has and the card answers with the number the counterfeiter programmed. The result is a flight where the aircraft reports that everything is fine while it writes the takeoff sequence on top of last week’s shoot.
Two failure types are sold as the same product and behave completely differently. A capacity-expanded card silently destroys older files. A speed-faked card silently stops recording. Neither announces itself, and both leave you with footage that looks like a camera fault.
Why the drone is the worst possible host for a counterfeit card
Three properties of drone use make counterfeits unusually damaging.
The card is out of sight. In a camera, a card is inserted and removed at every shoot, which gives a dishonest card repeated chances to reveal itself — a slow import, a folder that reads oddly, a card that needs repairing. In an aircraft, the card may stay in place for months. Plenty of pilots remove it only when it fills, so the first contact with reality happens after a long period of unnoticed damage.
The card operates at the edge of its specification. A 4K or 5.3K drone recording is one of the most demanding sustained-write workloads in consumer imaging, with a bitrate that many genuine cards handle only comfortably, let alone counterfeits. Cards that behave acceptably in a phone or a webcam fail in the air.
The write is not interruptible. On the ground, a stopped recording costs you a shot. In the air, a card that drops out of the write stream can cost the aircraft’s ability to save anything for the rest of the flight, because the camera subsystem has no way to recover from a card that stops responding mid-clip.
The general mechanics of these cards are covered in the reference on counterfeit memory card warning signs. What follows is the drone-specific version.
Symptom one: capacity that wraps around and eats the oldest footage
A capacity-expanded card is a genuine low-capacity die with a rewritten controller. The card may contain 32 GB of flash while reporting 512 GB, and the controller handles every address beyond its true size by wrapping back to the beginning. Writes “succeed” from every layer’s point of view, and the data that lived at the beginning is overwritten.
On a drone, this produces a signature that is easy to read once you know what to look for. The last flight’s footage is present and plays. The flight before, or the first half of the current flight, has been replaced. In extreme cases the file names run in order and then jump, because the aircraft’s sequential numbering survived while the content behind the earlier numbers did not.
The consequence for an operator is specific: the files that are lost are the ones recorded earliest, which on a job flight are commonly the establishing shots, the wide orbits, and the climb-outs — the footage that is hardest to reproduce and most often needed for the edit. The aircraft does not announce any of this, because the wraparound happens inside the controller and no error is ever returned.
Symptom two: a write speed that cannot sustain the bitrate
The second counterfeit type does not lie about capacity at all. It is a genuine card sold under a speed class it cannot hold, and it fails in a different and less obvious way.
A drone writing 4K at a high bitrate needs a sustained minimum write rate, and the rating that describes this is a minimum, not a peak. A card labeled V30 that sustains only 15 MB/s under sustained load will record the first seconds of a clip and then fall behind. What happens next depends on the aircraft: some stop the recording and report an error, some keep the file open while dropping frames, and some simply stop writing while the app continues to show an active recording indicator. Pilots land believing they have a full set of clips and find a card holding a fraction of the flight.
That last behavior is the one that catches professionals. There is no audio cue, no on-screen warning, and no notification on the controller. The recording indicator is driven by the camera’s state machine, not by confirmation that bytes reached the card.
| What you observe | What it usually means on a genuine card | What it means on a counterfeit |
|---|---|---|
| Early files missing, later files intact and playable | Accidental delete or a format you forgot | Capacity wraparound has already overwritten them |
| File numbering jumps with no gaps in flight time | Cards swapped between flights | Wraparound cycling behind the surviving numbers |
| Recording stops a few seconds into high-bitrate clips | Card below the required write rating, or thermal limit | Speed-faked card that cannot sustain the rated rate |
| App showed recording but the card holds no clip | Rare; usually a crash or power loss | Controller stopped acknowledging writes and reported success anyway |
| Card reports full but the file list is short | Genuine free-space issue | Fabricated capacity plus missing index entries |
| Card works fine in a phone, fails in the aircraft | Different workload, not a fault | The aircraft is the only device stressing sustained write |
What a dropped write costs in the air
The cost of a card failure is not proportional to the card’s price, and this is where the arithmetic of buying cheap becomes clear.
A single client flight may involve a short weather window, a location fee, and a subject that cannot be reassembled. If the card stops writing at minute four of a twelve-minute flight, the remaining eight minutes are gone along with everyone’s time. Aerial survey work is worse, because the flight pattern is a grid whose value depends on completeness: a gap in the coverage means the dataset may be unusable rather than merely incomplete.
There is also an operational cost that has nothing to do with the footage. A card that reports 512 GB and behaves unpredictably mid-flight is a card that can trigger undiagnosed recording stops, error messages, and gimbal or camera resets — a set of symptoms that pilots spend money diagnosing as a firmware or hardware fault. If an aircraft has produced recording stops that firmware updates did not fix, the card deserves a full-surface test before any repair invoice is paid. The identical symptom pattern from a firmware cause rather than a card cause is set out in the notes on recording that stops after a firmware update.
Two-step verification that a drone card has to pass
Neither test can be satisfied by a dishonest controller, and neither takes more than an evening.
Step one: a destructive full-surface test. Fill the card with numbered files, then read every file back and compare. H2testw on Windows and F3 or Validrive elsewhere do exactly this and report the point at which the read-back fails, which is the true capacity. Expect roughly 20 to 30 minutes for a 32 GB card, 60 to 90 minutes for 128 GB, and several hours for 512 GB. The test erases the card, so run it on a new card before it enters service, never on a card holding footage.
Step two: inspect the hardware. Compare the card against the manufacturer’s reference images: print quality, the placement of the capacity and speed markings, the serial number, the notch and contact geometry, and whether the back label carries a manufacturer identifier at all. A card bought from a marketplace seller at a fraction of street price, arriving without retail packaging, has already failed this step.
Two checks that do not work are worth listing because they are the ones pilots rely on. The aircraft’s own pre-flight indication that the card is fine proves nothing, because it is the card’s own claim being echoed back. And formatting the card in the aircraft proves nothing either, because a consistent file system on a lying controller passes every consistency check. More on what a drone actually needs from its storage medium, including the capacity, endurance, and temperature requirements, is collected in the overview of drone storage media, and the models worth buying are compared in the guide to verified microSD cards for drones.
What is left to recover after a card has already wrapped
The honest answer depends on one question: did the card ever fill past its real capacity?
If it did, the wraparound has already overwritten the oldest data, and only the newest generation of files remains — the last real-capacity’s worth of footage, which for a 32 GB die inside a 512 GB label is a small set. Those files are genuinely recoverable and usually intact, because nothing has overwritten them.
If it did not, nothing has been overwritten yet, and the situation is no different from an ordinary card with a damaged index. Recovery prospects are good, including for files that no longer appear in the folder listing. Data that has been overwritten cannot be restored by any tool, and that limit comes from the medium rather than from the software; the boundary is described in the notes on when data is unrecoverable.
Because a counterfeit card’s controller is also a failing component, image the card before scanning it. A controller that can be fooled into reporting false capacity is not a component to trust with repeated full-surface reads.
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. On a wrapped card, expect the most recent files only, and treat the rest as written off. The pattern that results — a card that reports plenty of free space while files keep disappearing — also appears on genuine cards with worn flash, which is why the symptom list for photos disappearing from a card is worth checking before you blame the seller.
Frequently Asked Questions
How do I know if the microSD card in my drone is fake?
Run a full-surface write-and-verify test with H2testw, F3, or Validrive, and compare the card against the manufacturer’s reference images. Nothing the aircraft reports about the card can be trusted, because the aircraft is echoing the card’s own claim.
My drone recorded a whole flight, but the early clips are missing. Is that a fake card?
It is the classic signature. A capacity-expanded card wraps past its real size and overwrites the earliest files, which is why the start of a flight disappears while the end survives. Verify capacity with a full-surface test before flying with that card again.
Can footage be recovered from a card that already wrapped?
Only the most recent generation of files. Everything older than the real capacity has been physically overwritten and no tool can restore it. If the card never filled past its true capacity, nothing was overwritten and recovery proceeds normally.
Why did the app show recording when no file exists on the card?
On a speed-faked or failing card the controller can stop acknowledging writes while still reporting success, so the camera’s recording indicator keeps running. The aircraft’s state reflects its own camera subsystem, not confirmation that data reached the card.