(a) 
If an event that would otherwise be a violation of a permit is caused solely by an act of God, war, strike, riot, or other catastrophe, and therefore, is beyond user’s control; the event is not a violation of that permit in an action brought in municipal or state court.
(b) 
A user who wishes to establish the affirmative defense of an event beyond the user’s control shall demonstrate the following through properly signed, contemporaneous operating logs, or the relevant evidence:
(1) 
An event of the type described in subsection (a) above occurred;
(2) 
The facility was at the time being operated in a prudent and workman-like manner and in compliance with applicable operation and maintenance procedures; and
(3) 
The user has submitted the following information to the city manager within twenty-four (24) hours of becoming aware of the event. If this information is provided orally, a written submission must be provided within five (5) days:
(A) 
A description of the indirect discharge and cause of noncompliance;
(B) 
The period of noncompliance, including exact dates and times or, if not corrected, the anticipated time the noncompliance is expected to continue; and
(C) 
Steps being taken and/or planned to reduce, eliminate, and prevent recurrence of the noncompliance.
(c) 
In any enforcement proceeding, the user seeking to establish the occurrence of an event beyond the user’s control shall have the burden of proof.
(d) 
Users will have the opportunity for a judicial determination on any claim of an event beyond the user’s control only in an enforcement action brought for noncompliance with categorical pretreatment standards.
(e) 
Users shall control production of all discharges to the extent necessary to maintain compliance with categorical pretreatment standards upon reduction, loss, or failure of its treatment facility until the facility is restored or an alternative method of treatment is provided.
This requirement applies in the situation where, among other things, the primary source of power of the treatment facility is reduced, lost, or fails.
(Ordinance 4845 adopted 1/19/2021)
A user shall have an affirmative defense to an enforcement action brought against it for noncompliance with the general prohibitions in section 13.05.031(a) or the specific prohibitions in section 13.05.031(b)(3) through (b)(7) if it can prove that it did not know, or have reason to know, that its discharge, alone or in conjunction with discharges from other sources, would cause pass through or interference and that either:
(1) 
A local limit exists for each pollutant discharge and the user was in compliance with each limit directly prior to, and during, the pass through or interference; or
(2) 
No local limit exists, but the discharge did not change substantially in nature or constituents from the user’s prior discharge when the city was regularly in compliance with its TPDES permit, and in the case of interference, was in compliance with applicable sludge use or disposal requirements.
(Ordinance 4845 adopted 1/19/2021)
(a) 
For the purposes of this section, the following definitions shall apply:
Bypass.
The intentional diversion of waste streams from any portion of a user’s treatment facility.
Severe property damage.
Substantial physical damage to property, damage to the treatment facilities which causes them to become inoperable, or substantial and permanent loss of natural resources which can reasonably be expected to occur in the absence of a bypass. Severe property damage does not mean economic loss caused by delays in production.
(b) 
Any user may allow any bypass to occur which does not cause pretreatment standards or requirements to be violated, but only if it also is for essential maintenance to assure efficient operation. These bypasses are not subject to the provision of subsections (c) and (d) of this section.
(c) 
Bypass notifications:
(1) 
If a user knows in advance of the need for a bypass, it shall submit prior notice to the city manager, at least ten (10) days before the date of the bypass, if possible.
(2) 
A user shall submit oral notice to the city manager of an unanticipated bypass that exceeds applicable pretreatment standards within twenty-four (24) hours from the time it becomes aware of the bypass. A written submission shall also be provided within five (5) days of the time the user becomes aware of the bypass. The written submission shall contain a description of the bypass and its cause; the duration of the bypass, including exact dates and times, and, if the bypass has not been corrected, the anticipated time it is expected to continue; and steps taken or planned to reduce, eliminate, and prevent reoccurrence of the bypass. The city manager may waive the written report on a case-by-case basis if the oral report has been received within twenty-four (24) hours.
(d) 
Bypass:
(1) 
Bypass is prohibited, and the city manager may take an enforcement action against a user for a bypass, unless:
(A) 
Bypass was unavoidable to prevent loss of life, personal injury, or severe property damage;
(B) 
There were no feasible alternatives to the bypass, such as the use of auxiliary treatment facilities, retention of untreated wastes, or maintenance during normal periods of equipment downtime. This condition is not satisfied if adequate back-up equipment should have been installed in the exercise of reasonable engineering judgment to prevent a bypass which occurred during normal periods of equipment downtime or preventive maintenance; and
(C) 
The user submitted notices as required under subsection (c) of this section.
(2) 
The city manager may approve an anticipated bypass, after considering its adverse effects, if the city manager determines that it will meet the three conditions listed in subsection (d)(1) of this section.
(Ordinance 3064 adopted 9/20/1994; 1995 Code, secs. 51.001–51.004, 51.015–51.019, 51.030–51.033, 51.045–51.051, 51.060–51.067, 51.080–51.092, 51.100–51.103, 51.110(A), 51.110(B)(1), 51.110(B)(2)(a)–(d), 51.115–51.122, 51.130–51.131, 51.140–51.143, 51.150–51.152, 51.999(A), (B); Ordinance 3152 adopted 11/21/1995; Ordinance 3271 adopted 9/2/1997; Ordinance 3525 adopted 6/5/2001; Ordinance 3912 adopted 11/7/2006; Ordinance adopting Code; Ordinance 4845 adopted 1/19/2021)