How often should haul roads be watered to control dust?

There's no single number that works across every pit. A haul road under a 40-tonne artic fleet running six-minute headways doesn't behave like a lightly trafficked route out to a stockpile, and the same road in January heat and July drizzle isn't the same road at all. Watering frequency comes out of four things: traffic volume, surface condition, ambient temperature and wind, and how much water your fleet can physically lay down before the next pass dries and breaks up the surface again.

Most EHS teams start with a rule-of-thumb interval, often somewhere between 20 minutes and two hours depending on season, then adjust it against what they see on the road. That adjustment is where most of the real control happens.

What drives the interval

Surface moisture on a haul road doesn't evaporate at a constant rate. Wind speed, relative humidity and solar load all move the clock, which is why a schedule written for winter shift patterns falls apart the first hot, dry week of summer. Traffic matters just as much as weather. Every pass of a loaded haul truck pumps fines back up into suspension, so a road carrying continuous traffic needs re-wetting far more often than one with gaps between loads. Surface condition compounds both. A freshly graded, well-compacted road holds moisture longer than one that's rutted or loose, which is why grading and watering schedules usually get planned together, not separately.

Add a chemical suppressant or binder to the mix and the calculus changes again. A treated road can go hours between water truck passes where an untreated one needs attention every cycle, but binder performance degrades with traffic volume too, so the interval still isn't fixed, just longer.

Sizing the cycle to your water truck fleet

This is the practical constraint that sets most schedules: how many water trucks you have, their tank capacity, and how long a full loop of the haul network takes. If one water truck takes 40 minutes to cover a loop and the road needs re-wetting every 30 minutes under full summer heat, you're already short a truck or a route needs splitting. Most sites work this backward from complaint history and VEO results rather than forward from a textbook figure: watch where dust is visibly lifting off the road between water truck passes, then tighten the cycle on that segment specifically rather than across the whole network.

A segment-level approach also saves water and truck hours. Not every haul road needs the same frequency. A low-traffic route to an overflow stockpile doesn't need the same cycle as the primary haul route carrying continuous loaded traffic past the pit boundary.

When the schedule isn't the whole answer

A watering schedule tells you what should have happened. It doesn't tell you what a regulator, a neighbor, or your own monthly report needs to know after a dust event: where the plume actually came from, how far it carried, and whether the suppression program on paper matched what was happening on the ground that day. A log entry showing the water truck ran its route at 2pm doesn't answer a complaint logged at 2:45 if the wind had already shifted or a haul truck kicked up a plume between passes.

That's the gap between a watering schedule and evidence of where dust left the site. Fugitive Dust Map segments a visible plume from a single satellite pass over the haul road, crusher or stockpile in question and hands back a marked-up image and plume extent you can put against your watering log, rather than relying on one observer's account of where the dust started.

If you're defending a watering schedule to a regulator, having a plume-level record alongside the log entry is worth building into your next event response.