AFFIRMATIVE DEFENSES

Salt Lake City Code tit. 17, div. II, ch. 17.69

in effect

Salt Lake City Code § 17.69.010 UPSET

17.69.010: UPSET: A. For the purposes of this section, "upset" means an exceptional incident in which there is unintentional and temporary noncompliance with categorical pretreatment standards because of factors beyond the reasonable control of the user. An upset does not include noncompliance to the extent caused by operational error, improperly designed treatment facilities, inadequate treatment facilities, lack of preventive maintenance, or careless or improper operation. B. An upset shall constitute an affirmative defense to an action brought for noncompliance with categorical pretreatment standards if the requirements of subsection C of this section are met. C. A user who wishes to establish the affirmative defense of upset shall demonstrate, through properly signed, contemporaneous operating logs, or other relevant evidence that: 1. An upset occurred and the user can identify the cause(s) of the upset; 2. The facility was at the time being operated in a prudent and workmanlike manner and in compliance with applicable operation and maintenance procedures; 3. The user has submitted the following information to the director and treatment plant operator within twenty four (24) hours of becoming aware of the upset (if this information is provided orally, a written submission must be provided within 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. D. In any enforcement proceeding, the user seeking to establish the occurrence of an upset shall have the burden of proof. E. Users shall have the opportunity for a judicial determination on any claim of upset only in an enforcement action brought for noncompliance with categorical pretreatment standards. F. The user 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 has failed. (Ord. 68-11, 2011)

Salt Lake City Code § 17.69.020 PROHIBITED DISCHARGE STANDARDS

17.69.020: PROHIBITED DISCHARGE STANDARDS: A user shall have an affirmative defense to an enforcement action brought against it for noncompliance with the general and specific prohibitions in section 17.36.060 of this title, with the exception(s) of the fire or explosion hazards or low or high pH, or any trucked or hauled wastes listed in subsections 17.36.060B2, B4, B5, and B15 of this title, 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: A. A local limit exists for each pollutant discharged and the user was in compliance with each limit directly prior to, and during, the pass-through or interference, or B. No local limit exists, but the discharge did not change substantially in nature or constituents from the user's prior discharge when the POTW was regularly in compliance with its UPDES permit, and in the case of interference, was in compliance with applicable sludge use or disposal requirements. (Ord. 73- 21, 2021: Ord. 68-11, 2011)

Salt Lake City Code § 17.69.030 BYPASS

17.69.030: BYPASS: A. Definitions: For the purposes of this section: 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. Conditions To Allow Bypass: A 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 Notification: 1. If a user knows in advance of the need for a bypass, it shall submit prior notice to the director, at least ten (10) days before the date of the bypass if possible. 2. A user shall submit oral notice of an unanticipated bypass that exceeds applicable pretreatment standards to the director 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. The user shall also set forth in writing the steps taken or planned to reduce, eliminate, and prevent reoccurrence of the bypass. The director 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 Prohibition; Exception: 1. Bypass is prohibited, and the director may take 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 backup 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 director may approve an anticipated bypass, after considering its adverse effects, if the director determines that it will meet the three (3) conditions listed in subsection D1 of this section. (Ord. 68-11, 2011)

Source: Salt Lake City, Utah, City Code (American Legal Publishing, codelibrary.amlegal.com)URL: https://codelibrary.amlegal.com/codes/saltlakecityut/latest/saltlakecity_ut/0-0-0-59431Fetched: 11/1/2026