A monitoring system that has stopped working looks identical to one that is working and finding nothing. Both show a quiet console. 40 CFR 280.40(a)(3) closes that gap by requiring a test of proper operation at least annually, and the rule is unusually specific about what gets checked on each piece of equipment.
The five component groups
The rule lists what the annual test must cover, as applicable to the facility. This is the list to hold a contractor's report against.
- Automatic tank gauge and other controllers. Test alarm. Verify system configuration. Test battery backup.
- Probes and sensors. Inspect for residual buildup. Ensure floats move freely. Ensure the shaft is not damaged. Ensure cables are free of kinks and breaks. Test alarm operability and communication with the controller.
- Automatic line leak detector. Test operation against the criteria in 280.44(a) by simulating a leak.
- Vacuum pumps and pressure gauges. Ensure proper communication with sensors and the controller.
- Hand held electronic sampling equipment used with groundwater and vapor monitoring. Ensure proper operation.
Two items on that list deserve a second look. Verify system configuration means somebody confirms the console is set up for the tanks that are actually in the ground, which catches the site where a tank was replaced and the console still holds the old capacity. And simulating a leak on the line leak detector means the test is active rather than observational. A detector that has never been given something to detect has not been tested.
What a pass actually claims
Operability testing establishes that the equipment works. It does not establish that the tank is tight.
Those are separate questions answered by separate activities. The annual test says the float moves, the alarm sounds and the sensor talks to the console. Whether product is leaving the tank is answered by the monitoring method itself, running at its own frequency, month after month. A site can pass its operability test in March and have a release in April, and nothing about the March test was wrong.
Worth stating plainly because the paperwork encourages the opposite reading. A clean annual report filed in the compliance binder looks like proof the tanks are sound. It is proof the instruments are honest.
Who sets the procedure
280.40(a)(3) gives three sources, the same shape used elsewhere in Part 280: the manufacturer's instructions, a code of practice from a nationally recognized association or independent testing laboratory, or requirements determined by your implementing agency to be no less protective. Petroleum Equipment Institute RP1200 is named as a code of practice that may be used.
The same rule also requires the method to be installed and calibrated in accordance with the manufacturer's instructions, and to be able to detect a release from any portion of the tank and the connected underground piping that routinely contains product. Coverage is part of the requirement, so a monitoring method that watches the tank and misses a run of piping does not satisfy 280.40(a)(1) no matter how well the equipment tests.
The date it started
October 13, 2018. The annual operability test arrived with the 2015 UST rule and applies from that date.
Sites that had monitoring equipment installed years before and had never had it operability tested went from compliant to behind on a single day, without anything at the site changing. It is one of the requirements most likely to be missing from an older operator's records for the simple reason that it did not exist when their routine was set.
A note on the language we use for tank readings
Daily and monthly reconciliation of tank readings against deliveries and sales produces data suitable for statistical inventory reconciliation. That is a useful and regulated thing to do, and it is worth being careful about what it is called. Certified leak detection is a claim that rests on the certification of the method, so software that reconciles numbers is producing SIR-ready data rather than performing leak detection. We hold ourselves to that distinction and it is a fair question to ask any vendor.
How FastDragon handles it
The annual operability test sits on the calendar per site, separate from the monitoring it validates and separate from the line leak detector test, because they are three requirements that a single contractor visit often closes at once. Filing one done does not silence the others.
Marking it complete asks for the contractor's report and files it against the requirement, so the question "when was the console last operability tested and what did it cover" is answerable from the site record rather than from a folder. Where a site has no vapor or groundwater monitoring, the hand held equipment line never appears, because the calendar is built from what the site actually has.
Common questions
What exactly gets tested in the annual operability test?
40 CFR 280.40(a)(3) lists five component groups, as applicable to the site. Automatic tank gauges and other controllers: test alarm, verify system configuration, test battery backup. Probes and sensors: inspect for residual buildup, ensure floats move freely, ensure the shaft is undamaged, ensure cables are free of kinks and breaks, test alarm operability and communication with the controller. Automatic line leak detectors: test operation against 280.44(a) by simulating a leak. Vacuum pumps and pressure gauges: ensure proper communication with sensors and controller. Hand held electronic sampling equipment for groundwater and vapor monitoring: ensure proper operation.
Is this the same as the ATG certification my contractor invoices for?
Usually yes, in substance. The rule does not use the word certification, and contractors do. What the rule requires is a test of proper operation performed at least annually, covering the components above, done to the manufacturer's instructions, a nationally recognized code of practice, or your implementing agency's requirements. Petroleum Equipment Institute RP1200 is named as a code that may be used. Ask which one the report is written against.
When did this start?
October 13, 2018. The requirement came in with the 2015 UST rule and 280.40(a)(3) names that date. Sites that installed release detection before then and never had it operability tested were compliant one day and behind the next.
Does a passing test mean my release detection is working?
It means the equipment operates. That is a different claim from the tank being tight. Operability testing confirms the alarm sounds, the float moves, the sensor talks to the console. Whether product is leaving the tank is answered by the monitoring method itself, run at its own frequency.
Does Connecticut ask for anything different?
Its periodic testing table carries a release detection testing column at annual across the tank categories, referencing RCSA 22a-449(d)-111(b), which lines up with the federal annual interval. The state also publishes a list of testing methods it has determined are unacceptable, so check that before booking a contractor.