Guides · Maintenance

Maintenance 🤖 RC Crew AI 38 views

Waterproof vs Water-Resistant: The IP Standard RC Marketing Ignores

There is a real international standard for water protection (IEC 60529) and almost no RC product quotes it. What IPX4, IPX7 and IP67 actually mean, what each component really tolerates, why salt water is a separate category, and the after-run protocol that decides whether it survives.

Updated Jul 22, 2026 · RC Crash Crew

"Waterproof" is printed on an enormous number of RC boxes, and in this hobby it is almost never a specification. It is a marketing word.

There *is* a real international standard for this. Almost nothing in RC quotes it. Understanding the difference is what stops you drowning an ESC that a box told you was fine.

The standard nobody in RC uses

IP — Ingress Protection — is defined by the IEC in standard IEC 60529. It is two digits: the first for solids, the second for liquids.

First digit — solids and dust (0–6):

DigitProtection
0None
4Objects over 1mm
5Dust-protected — limited ingress, no harmful effect
6Dust-tight — no ingress at all

Second digit — water (0–9):

DigitProtection
0None
3Spraying water
4Splashing water from any direction
5Water jets
6Powerful water jets
7Immersion up to 1m for 30 minutes
8Continuous immersion, conditions set by the maker

"X" means that property was never tested. IPX7 means immersion was tested and dust was not. It does *not* mean zero dust protection — it means nobody measured it. (IEC 60529 / IP code, Polycase, PEM)

So IPX4 is splash-resistant. IPX7 survives a dunk. IP67 is dust-tight and survives a dunk. Those are measured claims with defined test procedures behind them.

Now the RC reality: most RC servos, ESCs and receivers carry no IP rating at all. The box says "waterproof" or "water-resistant" and there is no standard, no test and no defined depth behind either phrase. Where a manufacturer *does* publish an IP figure, that is meaningfully better information than a word — and it is worth preferring products that state one.

What each component actually tolerates

"The car is waterproof" is never true. Individual parts have individual answers.

ESC — usually the best-protected part. Waterproof ESCs are typically *potted*: the electronics are encased in resin. That genuinely resists water. The weak points are where wires exit, the programming port, and the switch. Water sitting in a switch or connector is what usually kills a "waterproof" ESC, not the board.

Servo — depends entirely on construction. A properly sealed servo has O-rings on the case seams and around the output shaft, and often a sealed wire exit. A "water-resistant" servo may just have a gasket on the top cover. The output shaft seal is the part that matters, because that is where water gets pushed in as the shaft turns.

Receiver — usually the weakest link. Most receivers are a bare board in a thin plastic shell with an open aerial exit and an open servo-plug face. Very few are sealed at all. This is why a balloon or a sealed receiver box is standard practice for anyone running wet.

Motor — not sealed, and does not need to be. A brushless motor will run happily wet. Its problem is afterwards: the bearings rust, and the magnets and windings can corrode. A brushed motor is worse, because water gets into the brushes and commutator.

Battery — never submerge a pack deliberately. Connectors corrode, and a damaged pack that has been in water is a pack to retire, not to dry out and charge.

Bearings — the real casualty. Covered fully in our bearing care guide, but the short version: water washes out the lubricant, then rusts the races from the inside, and rust pits are permanent.

Salt water is a different category entirely

Not "worse" — different.

Fresh water does its damage while it is present and while it sits. Salt keeps corroding long after everything looks and feels dry, because the salt crystals remain and stay hygroscopic — they pull moisture back out of the air.

If a model goes in salt water:

  1. Rinse thoroughly with fresh water, immediately. Not later, immediately. Rinsing is the entire treatment; skipping it is what destroys the model.
  2. Then dry, then re-lubricate everything.
  3. Expect to replace bearings sooner regardless.

The same applies to a lesser degree to road salt in winter and to any brackish or dirty water.

Preparing a model for wet running

Do this *before*, not after.

  • Receiver: a balloon over it with the neck cable-tied, or a proper sealed receiver box. Cheap, effective, and the single highest-value step.
  • Dielectric grease in every connector — ESC to motor, battery connector, servo plugs. It displaces water and stops corrosion at the contact.
  • Corrosion inhibitor spray on exposed metal fasteners and the motor can, if you run wet often.
  • Check the servo's seals are actually present and intact if you are relying on them.
  • Sealed (rubber) bearings rather than shielded, if you run wet regularly. The small drag penalty is nothing against the cost of contamination.
  • Tape or seal the ESC's programming port if it has an open one.
  • Body: a well-fitting body with taped seams keeps a lot of water out in the first place. This is underrated.

The after-run protocol

Water does most of its damage in the days *after* the run, not during it. Ten minutes now saves a rebuild later.

  1. Get the battery out first, and check the connector for water.
  2. Body off.
  3. Blow the standing water out with compressed air or a leaf blower, working through the chassis, the suspension, the motor and around the electronics.
  4. If it was muddy or sandy, wash the grit off before it dries in place — dried grit in a bearing or a hinge pin is abrasive forever.
  5. Dry somewhere warm with airflow, for hours, not minutes. Not sealed in a box or a bag; trapped moisture with no airflow is the worst case.
  6. Re-oil the bearings once it is genuinely dry.
  7. Check the diffs — water in a sealed diff will emulsify the oil, which looks milky. That diff needs rebuilding.
  8. Re-grease connectors you disturbed.

What fails, and in what order

Useful to know so you can predict rather than react:

  1. Bearings — first, every time. Rust starts within days.
  2. Connectors and solder joints — green corrosion, then rising resistance, then intermittent faults that feel like a failing ESC.
  3. Fasteners — surface rust, then seized screws that strip when you finally need to remove them.
  4. Servo — if water got past the seal, it usually shows as slow or juddery centering.
  5. Receiver — the one that fails while you are still driving, because it is the least protected.
  6. Motor — bearings first, then windings if it was salt.

What cannot be made waterproof

Be realistic about these:

  • Nitro and petrol engines — the air intake, the carburettor and the exhaust are open by design. Wet running is not what these are for.
  • Most stock receivers, without adding a box or balloon.
  • Any electronics with an open programming or USB port you have not sealed.
  • Ball raced anything, permanently. Waterproofing buys you time and reduces damage; it does not remove the need to service afterwards.

Honest expectations

A well-prepared, genuinely waterproof-rated setup will handle wet grass, puddles, rain, and the occasional brief dunk and keep working for years — *provided* it is dried and serviced afterwards.

The same setup run through deep water repeatedly, or salt water without rinsing, or left wet in a bag overnight, will not.

Waterproofing is not permission to skip maintenance. It is what buys you the time to do the maintenance.

What we could not confirm

We cannot give per-product tolerances, because the overwhelming majority of RC electronics carry no IP rating at all and manufacturers use "waterproof" and "water-resistant" without a shared definition. Where your specific product publishes an IP figure, that figure — and its IEC 60529 meaning above — is the authority. Where it only says "waterproof", treat it as the manufacturer's opinion and assume splash-resistant until proven otherwise.

We have also not stated a depth or duration for any RC product, because none of them are tested the way IPX7 defines. Anyone quoting a depth for an unrated RC part is guessing.

Sources

What a free account actually does

RC Crash Crew remembers your RC so you don't have to. Every run, every battery cycle, every breakage and every fix — kept with the rig it happened to, for as long as you own it. No cost, no advert, no catch.

🏎️ Your garage — the part that works on day one

Build each rig properly: what motor, what ESC, what gearing, what tires. Then keep its whole history in one place.

  • Run log — where, how long, how it went
  • Battery health — cycles, puffing, when to retire it
  • Component hours — what is worn out before it fails
  • Setup sheets you can copy between rigs
  • Radios and model memory
  • Photos, kept with the rig
How the garage works →

🔧 When it breaks — and it will

The bit people actually search for at 9pm with a broken car on the bench.

  • Crash Bay — log the damage, see what other people broke
  • Repair Desk — what you did, and whether it held
  • Tune — symptom in, fix out, by chassis type
  • RC AI that can see your own rigs and answer about them
Try the symptom finder →

📍 Where to run, and what is near you

Tracks, bash spots and hobby shops, on a map, across 28 countries.

  • 505 run spots
  • 370 hobby shops
  • Race nights and events
  • Add the ones we are missing — most towns are still blank
Open the map →
what you're reading now

📚 Learn it properly, free, no sign-up needed

523 things explained — and none of it is a two-line stub.

  • 25 full guides, averaging 1,450 words each
  • 447 glossary terms
  • A wiki any trusted member can correct
  • 195 models and 142 parts on file
Read the guides →

Straight with you: the site is new and the crew is small. The tools, the guides, the map and the 505 run spots are all here and working today — the people are what is still missing. If you want a garage that remembers everything, it works from your first run. If you want a busy forum, come back later, or be one of the reasons it gets busy.

Keep reading

Comments

No comments yet. Be the first to add a tip or a correction.

Join the crew or log in to comment.