How to respond to a fugitive dust complaint from a neighbor

A dust complaint from a neighbor rarely comes in through official channels first. It's a phone call to the front office, a message to a county supervisor, or a photo posted to a community page with the mine's name in the caption. By the time it reaches EHS, the moment that mattered (wind direction, which haul segment was active, whether the water truck had made its pass) is already gone unless someone wrote it down.

What to capture before you write anything back

Start the clock the minute the complaint lands. Note the time of the call, the wind speed and direction from your nearest met station, and which operations were running: crusher on or off, which stockpile face was active, haul truck counts on the segment nearest the complainant. Pull your water truck or suppressant application log for that shift. If the complainant mentions a specific time, a shift change, right after a blast, match your production records to that window before you draft a response.

This is also where most responses go soft. A complaint says dust was blowing off the property toward a house, and the file ends up holding a log entry that repeats the same claim back with a date stamp attached. A regulator reading that file later will ask the obvious question: how do you know it came from the mine and not the county road, a neighboring ag field, or a construction site a half mile upwind.

Dust complaint response procedure, step by step

A workable procedure runs something like this:

1. Log the complaint with time, date, wind data, and the complainant's description of the plume, color, direction, how long it lasted.
2. Pull operational records for the window described: equipment running, suppression applied, haul road watering schedule.
3. Walk or drive the named source area while conditions are still close to the event, or as near the event time as practical.
4. Document what you find: ground photos, any plume still visible, the condition of the haul road surface or stockpile face.
5. Identify a corrective action if the walk turns up an obvious cause, a dry haul segment, a stockpile face that missed a watering pass, a gap in the crusher enclosure.
6. Close the loop with the complainant, and with the regulator in writing if one is involved.

Steps 3 and 4 are where a ground-based response usually falls short. A dust event moves fast. Wind shifts, trucks keep running, and by the time someone walks the site the plume that triggered the call has already dispersed. What's left is one observer's account, usually your own staff, standing at the source looking for a dust condition after it has already passed.

That gap is the real argument for pulling an image from the satellite pass closest to the complaint window. If a fugitive dust file rests on a worker's written recollection of what they saw an hour after the call, a regulator, or a neighbor with a lawyer, can reasonably ask why that's the best evidence on hand. Fugitive Dust Map hands back a marked-up image and a shapefile of plume extent from the imagery itself, something that reads as independent evidence rather than a staff recollection written up after the fact.

What to send a regulator after a dust complaint

When a regulator follows up, the file that holds up is the one built on a timeline, not a narrative. At minimum, it should include:

• The original complaint log entry with wind data for that window
• Operational records covering the same period: equipment status, water truck application log
• Site documentation from the follow-up walk, with photos and timestamps
• The corrective action taken, with a date it went into effect
• Any imagery or independent evidence tying the plume to a specific source, or ruling the site out

Skip the paragraph explaining why the mine probably wasn't the source. Regulators read a lot of those, and they read as defensive even when the facts back them up. A timeline with records attached does the explaining on its own.

Not every complaint has a clean answer. Sometimes the wind was wrong for the site to be the source and the met data shows it plainly. Sometimes a stockpile face really was dry and the fix is obvious. Either way, a response built on logged records holds up better the second time around than one built on a single person's account of what they saw from the road.

If dust complaints keep landing on your desk, it's worth having an image of the day in question on file before the next one does.