Utah Admin. Code R315-265-226 - Surface Impoundments - Monitoring and Inspection
(a) The owner or operator shall inspect:
(1) The freeboard level at least once each
operating day to ensure compliance with Section R315-265-222, and
(2) The surface impoundment, including dikes
and vegetation surrounding the dike, at least once a week to detect any leaks,
deterioration, or failures in the impoundment.
(b)
(1) An
owner or operator required to have a leak detection system under Subsection
R315-265-221(a) shall record the amount of liquids removed from each leak
detection system sump at least once each week during the active life and
closure period.
(2) After the final
cover is installed, the amount of liquids removed from each leak detection
system sump shall be recorded at least monthly. If the liquid level in the sump
stays below the pump operating level for two consecutive months, the amount of
liquids in the sumps shall be recorded at least quarterly. If the liquid level
in the sump stays below the pump operating level for two consecutive quarters,
the amount of liquids in the sumps shall be recorded at least semi-annually. If
at any time during the post-closure care period the pump operating level is
exceeded at units on quarterly or semi-annual recording schedules, the owner or
operator shall return to monthly recording of amounts of liquids removed from
each sump until the liquid level again stays below the pump operating level for
two consecutive months.
(3) "Pump
operating level" is a liquid level proposed by the owner or operator and
approved by the Director based on pump activation level, sump dimensions, and
level that avoids backup into the drainage layer and minimizes head in the
sump. The timing for submission and approval of the proposed "pump operating
level" will be in accordance with Subsection R315-265-222(a).
Comment: As required by Subsection R315-265-15(c), the owner or operator shall remedy any deterioration or malfunction he finds.
Notes
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.