Building a dust control plan that satisfies a notice of violation

A notice of violation for fugitive dust almost always traces back to one thing: an inspector or a neighbor saw a visible plume leaving the haul road, the crusher, or a stockpile, and nobody on site had anything on paper to counter it. Once the notice lands, the agency wants a corrective action plan: specific changes, with a way to verify they're happening. That plan gets read by someone who reviews dozens of these a year and knows which ones are boilerplate.

Most sites already have a dust control plan sitting in a binder somewhere. The problem is rarely that the plan is missing; it's that the plan on file doesn't match what the inspector saw on site, and there's no way to show where the dust originated, how far it traveled, or whether the control measures already in place were even running that day.

What the reviewer is actually checking for

A compliance officer reading a corrective action plan after a fugitive dust complaint is looking for three things, in roughly this order:

A named source. "Unpaved haul roads" is not a source. "The 400 meters of haul road between the pit exit and the crusher, graded at 6%, carrying loaded trucks at roughly 40 trips a shift" is a source. If your plan can't point to the segment, the stockpile face, or the transfer point that produced the plume the inspector cited, the reviewer has no way to confirm your fix addresses the actual event.

Controls sized to the source, with a trigger. Water truck frequency, binder application, speed limits, wind-speed shutdown thresholds, enclosure or skirting on a conveyor. The plan needs to say what triggers each measure (wind speed, moisture reading, visible opacity) and who's responsible for pulling it.

Evidence that the controls worked. This is where most plans fall apart. A log entry that says "water truck dispatched, 14:20" tells the reviewer a truck went out. It doesn't tell them the plume stopped, how far it had traveled, or whether the same source generated another event two days later that nobody wrote down.

The evidence gap a log book can't close

A dust control plan built entirely on operator logs and photos from a single vantage point has a structural weakness: it relies on someone being in the right place, at the right time, with a phone out. Regulators know this, and a corrective action plan that leans on it alone tends to come back with follow-up questions, or a second site visit.

What closes that gap is a record of the plume itself at the time it happened: where it extended to, from which source, on which date. That's the kind of evidence an agency can set alongside a complaint and resolve, rather than taking one party's word over another's.

This is the specific gap Fugitive Dust Map is built around. It pulls a satellite pass over the site around the date of an event, segments the visible plume from the haul road, crusher, or stockpile it came from, and hands back a marked-up image and a shapefile of the plume's extent. Dropped into a corrective action plan, it's the piece that turns "we addressed the complaint" into "here's the plume, here's the source, here's the extent, here's what we changed." If you're assembling a response to a notice right now, see how a single pass over your site turns into that evidence layer.

Writing the plan so it holds up

Once you have a source identified and an extent documented, write the plan to name the source, state the trigger for each control, assign who checks it, and set a review interval (most agencies want 30 or 60 days, read your notice for the actual number). Attach whatever plume evidence you have for the event in question, and keep the format consistent so the next one, if there is a next one, slots in the same way.

Plans that get approved on first submission are specific about source, trigger, and proof, regardless of length. A plan that reads like it was written for any site, anywhere, reads exactly that way to the person approving it.

Fugitive Dust Map exists for the moment right after a complaint or a notice, when you need something more than a log entry to hand back.