Secondary Bypass During a Storm: DMR Reporting and the Affirmative Defense
A 2.0 MGD activated sludge plant has NPDES limits of 30 mg/L BOD and 30 mg/L TSS with 85% removal, reported on a monthly DMR. On a Saturday at 0900, during a 3-inch rain, influent peaked at 6.5 MGD. Secondary clarifier 2's drive tripped and RAS pump 3 seized; mixed liquor rose in clarifier 1 and began spilling over the weir toward the chlorine contact basin, with water within 4 inches of the MCC room door. The chief operator opened the emergency gate that sends primary effluent straight to chlorination - about 1.2 MGD for 6 hours - while a crew pulled the RAS pump. Effluent that day: BOD 58 mg/L, TSS 74 mg/L; coliforms were in compliance. The plant owns an unused 400,000-gallon sludge holding tank, and a rental pump vendor is 90 minutes away. The superintendent wants the DMR filed as a normal month, saying "it was storm flow, not really our discharge."
1. What are the reporting obligations here, and does the storm change them?
Read the worked answer
The bypass is a permit violation and must be reported, not normalized.
- Oral notice to the state (or the number in the permit) typically within 24 hours of becoming aware - here, Saturday. This is the call that is most often botched because it falls on a weekend; the permit's notification numbers must be posted in the control room precisely for this.
- Written notice typically within 5 days, describing the cause, the volume and duration, the steps taken, and the planned corrective action.
- DMR: the measured BOD 58 and TSS 74 are the values of record. They go on the DMR as monitored, with the exceedance flagged. Bypassed flow is not removed from the report and is not replaced by an "estimated" value designed to look better.
- Other triggers: depending on the state, the bypass may also be reportable as a discharge to the collection system or receiving water, and there may be separate requirements for the MCC-flooding near-miss.
The storm is not a defense. Wet weather explains the flow but does not convert a bypass into permitted discharge. Dilution, blending, and "it rained" are not recognized excuses, and deliberately misreporting moves the issue from an exceedance to a falsification.
Correct framing for the DMR: report actual data, attach the bypass notification, and describe the event factually in the comment field.
2. The superintendent wants to claim the bypass affirmative defense. Evaluate it against the conditions such defenses actually require.
Read the worked answer
A bypass affirmative defense generally requires all of the following, not most:
- Unavoidable to prevent loss of life, personal injury, or severe property damage. The water 4 inches from the MCC room door is a strong argument - an energized electrical room flooded on a Saturday is a severe property damage and shock/arc-flash risk.
- No feasible alternatives to the bypass, including proper operation and maintenance, adequate back-up equipment, and alternative disposal.
- Proper notice as described above.
- All reasonable steps taken to minimize the bypass and its impact.
This is where the defense likely fails. The plant owns an unused 400,000-gallon holding tank. At 1.2 MGD that is roughly 8 hours of storage (400,000 ÷ 1,200,000 gal/day × 24 ≈ 8 hours) - more than the 6-hour bypass. Even allowing for filling time, drawdown, and the need to keep the tank available, the existence of an unused tank on site undermines "no feasible alternatives" unless there is a documented reason it could not be used (out of service, structurally compromised, needed for sludge, insufficient time to line up piping, no pumps).
What the operator should do: write down the reasoning at the time - what alternatives were considered, why each was rejected, who was consulted, and the timeline. A defense reconstructed two weeks later during a compliance review is worth very little. Also note the defense protects against penalties for the bypass itself; it does not erase the reported exceedances or the underlying equipment failure.
3. What records and follow-up actions turn this from a repeat offense into a managed event?
Read the worked answer
Documentation (produced contemporaneously)
- Timeline: when the drive tripped, when RAS failed, when the gate opened and closed, when the state was called and to whom.
- Flow totalizer readings for the bypass, plus the upstream and downstream sample results, with chain of custody.
- Photographs of the water level at the MCC door, the tripped drive, and the seized pump.
- Maintenance history for the clarifier drive and RAS pump (was the failure predictable?), and the standby/backup strategy as written.
- Copy of the written notice and the oral-call log entry.
Corrective action plan
- Restore redundancy: repair or replace the RAS pump, add a functioning standby, and set alarms on clarifier drive torque so a trip is visible at the control room, not discovered visually.
- Write a wet-weather SOP that pre-identifies the options in order: equalize in the holding tank, use the rental pumps, throttle influent, then bypass - with trigger levels.
- Put the state notification numbers, the after-hours number, and the decision authority on a single laminated sheet at the control panel.
- Drill the scenario before the next wet season; a bypass that has never been rehearsed is a bypass that gets made up under pressure.
Culture point: the operator who opened the gate to protect the electrical room made a defensible call. The failure is the superintendent's instruction to file the DMR as normal, and that instruction should be declined in writing - the permit makes the certified signer personally responsible for the report's accuracy.