← All articles

the 30-day walkthrough: the cheapest requirement to fail an inspection on

Since October 2018, 40 CFR 280.36 has required a walkthrough inspection of the site every 30 days, plus a longer one once a year. It needs no contractor, no equipment and no appointment. It takes about fifteen minutes. It is also, on the numbers most state programs publish, among the things inspectors write up most often, because a requirement that costs nothing is a requirement people assume is optional.

What the monthly walk checks

The rule lists two pieces of equipment for the 30-day check and is specific about what happens to each.

Spill prevention equipment, meaning the spill bucket or catchment basin under the fill cap. Visually check it for damage. Remove liquid or debris sitting in it. Check for and remove obstructions in the fill pipe. Check that the fill cap is securely on the fill pipe. If the bucket is double walled with interstitial monitoring, check the interstitial area for a leak.

Release detection equipment. Check that it is operating with no alarms or unusual operating conditions present, and make sure the records of release detection testing are reviewed and current.

Read the second one twice. It contains a records check inside an equipment check. Walking past a console with no red light showing satisfies half of it. The other half is confirming the release detection paperwork is up to date, which means the monthly walk is also the thing that catches a missed test somewhere else on the calendar.

What the annual walk adds

Once a year, two more items under 280.36(a)(1)(ii).

  • Containment sumps. Visually check for damage, leaks to the containment area, or releases to the environment. Remove liquid in contained sumps, or debris. For double walled sumps with interstitial monitoring, check the interstitial area for a leak.
  • Hand held release detection equipment. Tank gauge sticks and groundwater bailers get checked for operability and serviceability.

The annual sump check is a visual, and it is worth being clear that it is a different obligation from the three year liquid tightness test on sumps under 280.35. Looking in the sump once a year does not close out the test, and testing it every three years does not close out the annual look.

The delivery exception

One allowance is written into the 30-day requirement. Spill prevention equipment at UST systems receiving deliveries at intervals greater than every 30 days may be checked prior to each delivery instead.

That matters for a low-volume site, a seasonal marina, or a fleet yard that takes a load every six or seven weeks. The catch is evidentiary: 280.36(b) says the records must include delivery records where spill prevention equipment is checked less frequently than every 30 days due to infrequent deliveries. Using the allowance means keeping the BOLs to prove you were entitled to it. The release detection equipment check stays on the 30-day clock regardless.

You can use somebody else's checklist

280.36(a) gives three ways to satisfy it. Do the inspection the rule describes, follow a standard code of practice from a nationally recognized association or independent testing laboratory that checks comparable equipment, or use a walkthrough developed by your implementing agency.

The rule names Petroleum Equipment Institute RP 900 as a code of practice that may be used. Several states publish their own forms: Connecticut has a fillable monthly inspection checklist and a separate annual one, and a separate monthly checklist again for systems that are temporarily out of service. Using the state's own form has an obvious advantage when the state's inspector arrives.

One year, and that is the trap

280.36(b) requires walkthrough records to be kept for one year. The tests sitting beside them in the same binder are kept for three, under 280.35(c). Two retention periods, one folder, and the shorter one belongs to the record generated most often.

Each record has to list every area checked, whether each area was acceptable or needed action, a description of the actions taken to correct anything that needed it, and the delivery records where the longer spill bucket interval is being used.

That last requirement is the one that turns a walkthrough into a real document. A checklist of twelve ticks proves a walk happened. A checklist with one item marked "sump 2, water present, pumped out and disposed of, 14 May" proves somebody looked and did something. The second one is what closes an inspection question.

Why it gets skipped

Nothing breaks when a monthly walk is missed. No alarm sounds, no supplier calls, no dispenser stops. The gap only surfaces when an inspector asks for twelve records and gets nine, and by then the missing three cannot be recreated honestly.

It also lands on a person rather than a contractor. Every other date on a compliance calendar has somebody outside the business who turns up, does the work, and sends an invoice, and an invoice is hard to forget. The walkthrough has none of that. It is the only recurring requirement with no external party attached to it, which is exactly why it is the one that quietly stops happening.

How FastDragon handles it

The walkthrough sits on the calendar as a monthly item per site, with the annual one on its own cycle, so the two do not get confused with each other. It is done on a phone at the site: the checklist is the one you set up, a failed point takes a photograph where it was taken, and the note goes on the record rather than in somebody's memory.

Because the record is filed against the site and dated when the walk happened, twelve months of them is a query rather than a search through a binder. Where the delivery exception applies, the site is set to that interval and the calendar stops asking for a monthly check it does not owe.

Common questions

How long do walkthrough records have to be kept?

One year, under 40 CFR 280.36(b). That is shorter than most UST records and it catches people out, because the spill bucket and sump test records next to them in the same binder are kept three years under 280.35(c). Each record has to list every area checked, whether it was acceptable or needed action, and a description of what was done about anything that was not.

My site only takes a delivery every six weeks. Do I still walk it every 30 days?

The spill prevention equipment part can move. 280.36(a)(1)(i) allows spill prevention equipment at sites receiving deliveries at intervals greater than every 30 days to be checked before each delivery instead. If you use that allowance you have to keep the delivery records alongside the inspection records to show why the interval is longer. The release detection equipment check stays on 30 days.

Can I use a checklist from somewhere else?

Yes. 280.36(a)(2) allows a standard code of practice from a nationally recognized association or independent testing laboratory that checks comparable equipment, and the rule names Petroleum Equipment Institute RP 900 as one that qualifies. 280.36(a)(3) allows a walkthrough developed by your implementing agency. Connecticut publishes its own monthly and annual inspection checklists as fillable forms.

Who is allowed to do the walkthrough?

The federal rule does not name a job title for it, which is part of why it gets treated as optional. In practice it lands on whoever is at the site, and states that run operator training programs generally expect a Class B operator to own the monthly inspection. Check what your own state requires before you decide a cashier can sign it.

What does the annual part cover that the monthly does not?

Two things, under 280.36(a)(1)(ii). Containment sumps get a visual check for damage, leaks, or releases, liquid and debris get removed, and double walled sumps with interstitial monitoring get an interstitial check. Hand held release detection equipment, meaning tank gauge sticks and groundwater bailers, gets checked for operability and serviceability.

See the compliance calendar →

See your own sites on this calendar.

Bring one difficult site. We set it up on the call, tanks, piping and state, and show you what it owes.