Drone water damage is the one failure class where the type of water matters more than the amount of time. Salt water begins corroding contacts in minutes and keeps corroding after it dries. Fresh water is far slower and far more forgiving, which is exactly why it produces the more common disaster: a freshwater-soaked card often still works for one session, and that one session powers the corrosion that finishes it.
This page covers the mechanism rather than the handling sequence: why a drone card behaves as it does after a splashdown is a question about chemistry and packaging.
Why the card usually outlives the aircraft
A consumer drone is a poor candidate for surviving immersion. The gimbal camera module is not rated for it, the SD slot door on most models is a friction-fit cover rather than a gasketed seal, and the airframe has openings for motors, vents, and a battery bay. Water enters a gimbal housing within seconds, and once inside it reaches the card slot, the ribbon connectors, and the mainboard.
The card in that slot is a different object. An SD or microSD card is a monolithic package: memory dies and a controller, bonded to a small board and encapsulated in epoxy and plastic, with no openings, no vents, and no moving parts. Water does not get inside the package. It gets around it, onto the gold fingers and into the seams at the edges.
That difference is why the aircraft is usually a repair question and the card is usually a data question. If the aircraft itself is the concern, the handling procedure for a submerged camera covers the same battery-first, card-second order that applies to a drone body.
Salt water and fresh water corrode on different clocks
The two water types differ in conductivity, and conductivity is what drives the damage.
Salt water is an electrolyte. Its dissolved chloride ions make it conductive enough to carry meaningful current between adjacent contacts, and chlorides are aggressive toward the nickel and copper layers under a card’s gold plating. The plating itself is nearly inert, which is why a card can look pristine while the metal underneath has already corroded. Salt also attracts moisture from humid air, so a card dried after saltwater exposure re-wets itself in a humid room.
Fresh water is a poor conductor by comparison, but it is not inert. It carries dissolved oxygen and minerals, and lake or river water usually carries more fine sediment than seawater. Sediment is the specific problem: particles lodge in the contact recesses and the write-protect switch and hold moisture against the metal.
| Water type | Conductivity | Visible corrosion begins | Continues after drying? | Realistic outlook for the card |
|---|---|---|---|---|
| Ocean or saltwater | High | Minutes | Yes, slowly | Urgent; hours matter |
| Brackish or estuary | Moderate to high | Tens of minutes | Yes | Treat as salt water |
| Fresh lake or river | Low | Hours to days | Weakly | Good if never powered wet |
| Cold freshwater (under 10 °C) | Low | Days | Weakly | Better than warm freshwater |
| Muddy or silty water | Low | Hours | Yes, sediment holds moisture | Moderate; cleaning matters |
| Chlorinated pool | Moderate | Tens of minutes | Yes | Treat as mildly saline |
Two entries there run against intuition. Cold water is better than warm water. A drone recovered from a cold alpine lake after three days has a better chance than one recovered from a warm shallow pond after six hours, because corrosion reactions are temperature-dependent and cold suppresses the biological activity that produces organic acids. And freshwater immersion that seems to have done nothing is the more dangerous event, because a card that still reads tempts its owner into using it, and using it is what causes the real damage.
The two paths water takes into a card
Water reaches the data through one of two routes, and the route determines whether software has any role at all.
Path one: the contacts. Water bridges the gold fingers and wicks along the seam between shell and board. The memory die stays dry and the data stays intact. What fails is the interface: oxide and corrosion products build up on the contact surfaces, and the card stops responding or responds intermittently. This path is recoverable because the failure is at the surface. Cleaning the contacts, letting the card dry completely, and reading it once in a known-good reader can work.
Path two: the controller. If the shell is cracked, if the card was crushed in the impact that led to the splashdown, or if water sat against the package long enough, moisture can reach the controller’s solder joints and bond wires. A drone that hits water at speed typically does both: the gimbal takes the impact and the card takes the immersion. Controller-level water damage is not a cleaning problem, and it leads to the same terminus as a burnt controller: a laboratory, board-level work, and the cost profile described in the assessment of software versus a recovery laboratory.
The quick separator between the paths is the camera. If the slot shows water marks but the card looks clean and unbent, suspect path one. If the shell is cracked, if the aircraft came out of the water in pieces, or if the card was hot when it went in, suspect path two and stop experimenting.
The counterintuitive part: power does more damage than water
Water alone, with no electrical current, is slow. Water plus voltage is electrolytic corrosion, and the rate increase is not incremental; it is orders of magnitude. This is why the single worst thing you can do to a wet card is put it in a reader to see whether it works.
The corrosion cell needs three things: an electrolyte, two metals at different potentials, and a current path. A wet card has the first two by default. The moment the card is powered, you supply the third, and the reaction eats the fine traces and solder joints connecting the controller to the memory die. Soaking a card in salt water without power for an hour is survivable. Powering it for thirty seconds while wet can be permanent.
The same logic applies to the drone. Leaving the battery in a flooded airframe keeps current flowing through wet boards for as long as the pack holds charge, and a lithium pack exposed to salt water can also swell or vent. Removing the battery is a fire-safety step that happens to help the card as well.
A second, quieter version of the same mistake is heat. Warm air, a hair dryer, or a warm car interior accelerates both chemical corrosion and the migration of dissolved salts into narrow recesses. Air at room temperature, desiccant in a sealed container, and patience are what the chemistry calls for.
Rice is not a drying method. Rice dust is finer than the gaps it needs to stay out of, it packs into contact recesses and the write-protect switch, and it removes water from a sealed plastic package no faster than open air. The emergency handling guide for a water damaged card covers the drying setup that works.
How long the window actually is
The window is defined by exposure, not by a stopwatch. What matters is which path the water took, whether the card was ever powered wet, and how fast it can be dried or handed to a professional.
| Situation | Reasonable action window | Best move |
|---|---|---|
| Freshwater splash, never powered, contacts clean | 24–72 hours of drying is fine | Dry fully, read once, copy everything |
| Freshwater, card powered while wet | Immediate | Stop; treat as an electrical fault |
| Salt water, card never powered | Hours, fewer in warm conditions | Keep as found, do not rinse, hand over promptly |
| Salt water, card powered while wet | Immediate | Laboratory |
| Any water, shell cracked or card crushed | No window; handling is the risk | Do not insert; laboratory |
| Recovered from cold freshwater after days | Days, and surprisingly good | Dry slowly, read once |
Rinsing a saltwater-soaked card with fresh water is not the right first move, even though it sounds like one: it redistributes chlorides into recesses that air cannot reach well enough to dry them afterward. Keep the card damp and as-found.
What the drone’s own shutdown does to the last file
A separate failure usually accompanies the water damage, and it is routinely mistaken for total loss. Drones detect water contact or sudden attitude change and cut the motors, and depending on the model they may also stop recording, power down, or both.
That shutdown creates the classic interrupted-recording file: the video data is complete on the card, but the trailing index atom that tells a player where the frames are and how long the clip runs was never written. The result is a file that reports a duration of zero seconds, or that a player refuses to open at all. Nothing is missing; the map is.
This is repairable, and worth doing before concluding that the last — usually most valuable — clip of the flight is gone. The repair procedure for a missing index atom applies directly, and the same failure appears in drone crashes that never touch water, which is why the cause analysis for crash-related card damage shares a common branch with this page.
Reading the card once, correctly
When the card is dry and the decision is to try it, the goal is one clean read with no writing.
- Use a known-good reader on a rear-panel port, not the drone and not a hub. Reading through the aircraft gives a damaged board another chance to write.
- Lock the write-protect switch if the card has one.
- If the card mounts and the files are there, copy them off and verify the copies. Do not delete or reorganize anything on the card.
- If the card mounts and files are missing or truncated, stop and make an image first, since a second read of a corroding card may not behave like the first.
- If the card does not mount, decline any repair prompt. A repair utility writes a new file system and can destroy the directory entries a recovery scan needs; the recovery mistakes that make damage permanent covers that list.
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. Data that has not been overwritten can be recovered in full, a recovered file that will not open can often be repaired or re-encoded, and data that has been overwritten is gone. Recovery software cannot clean corroded contacts or replace a drowned controller, and those cases belong to a laboratory.
A card that has been submerged and then works should not go back into service, because corrosion does not stop when the card starts working. Copy the footage to two drives, verify it opens, and retire the card. The long-term wear and lifespan picture explains why a card that has been through an electrical event is a poor candidate for a shoot that matters.
Frequently Asked Questions
Should I rinse a saltwater-soaked memory card with fresh water?
No. Rinsing moves chlorides into recesses that air cannot dry afterward, and it does not stop the corrosion already underway. Keep the card damp and exactly as found, do not power it, and hand it to someone equipped to clean and dry it.
How long can a drone card stay underwater and still be recoverable?
It depends on the water rather than the clock. Cold freshwater is the best case, and a card recovered after several days from a cold lake is often still fully readable. Warm salt water is the worst case, where contacts corrode within minutes and the practical advice is to hand the card over the same day.
The drone cut recording when it hit the water. Is that last clip lost?
Usually not. The video data is typically complete on the card; what is missing is the trailing index atom, because the drone powered down before writing it. A file that reports zero duration or refuses to open is the standard signature, and the repair is well established.
Can I dry a wet card in the oven or with a hair dryer?
No, and it is one of the more damaging things you could do. Heat accelerates corrosion and drives dissolved salts deeper into the card’s seams and contact recesses. Room-temperature air with desiccant is slower and far better.