Weekend Sewer Overflow: Reporting, the Unreported Spill, and Root Cause
At 06:40 on a Saturday, a collection crew responding to a call finds an 8-in gravity sewer running full and overflowing from a manhole into a storm ditch. Grease and roots are visible. They estimate about 4,500 gal escaped before the line was cleared at 08:10; a sheen and a grey plume are visible for about 200 ft down the ditch, which discharges to a creek about 0.25 mi away. The crew vacuumed and limed the area and set up warning signs. The on-call superintendent is notified at 07:05. The state requires oral notification within 2 hours of discovery and a written report within 5 days for any overflow that reaches waters of the state. Reviewing the log, you also find a 300-gal overflow at the same manhole four weeks ago that was cleaned up and never reported "because it was contained."
1. What has to happen in the next two hours, and what has to happen over the next five days?
Read the worked answer
The clock started at discovery (06:40), not at cleanup (08:10). That places the oral notification deadline at about 08:40 today. Do not wait for a final volume - call with the preliminary estimate and update it later. If that deadline has already passed, call immediately, report the actual time of discovery, and do not backdate anything.
Within two hours:
- Oral notification to the state, and to the local health department if the program requires it. Give location, time discovered, estimated volume, receiving water and the path to it, actions taken, and a call-back contact.
- Notify any downstream drinking water intake or public beach program the permit names.
- Photograph the ditch, the plume, and the flow path; start a written incident timeline with names and times.
- Sample upstream and downstream if the monitoring program allows, with chain of custody.
Within five days:
- Written report with the final volume estimate, cause, corrective actions, and a schedule.
- Do not decide unilaterally that the spill was "contained." A ditch discharging to a creek a quarter mile away is a pathway to waters of the state; document it and let the regulator classify it. Many states require reporting of all overflows regardless of reach.
- Complete the cleanup documentation: disposed volume, lime and vacuuming, signage removal.
2. How would you handle the unreported 300-gal overflow from four weeks ago?
Read the worked answer
Treat it as a compliance failure and disclose it; do not bury it.
If the rule requires reporting of overflows that reach waters of the state - and most do - the fact that the spill was cleaned up does not remove the obligation. Cleaning up is remediation, not reporting. The past practice is also a pattern indicator: if one overflow was quietly handled, others probably were too.
Steps:
- Reconstruct the event from crew notes, work orders, dispatch records, and witness statements. Write down what is known and what is not; do not fill gaps with assumptions.
- Self-disclose in writing to the regulator, describing the event, the missed notification, and the corrective action. Self-disclosure before an inspection is treated far more favorably than discovery during one.
- Audit 12 months of crew logs, work orders, and complaints for similar events at other locations.
- Fix the system, not just the person: change the field form to force an explicit "did it leave the right-of-way / reach waters?" answer and a required call-in, add a 24-hour reporting number to the crew's dispatch instructions, and train every crew member on the threshold.
Personal and professional exposure: concealing or falsifying records can be a criminal matter, can jeopardize the plant's permit, and can cost individual operators their certifications. The superintendent's duty is to correct the practice openly and to protect the crew member who raised it.
3. What root cause and preventive measures would you commit to in the written report, and how would you prove they worked?
Read the worked answer
Root cause (state it as a finding, supported by evidence): a grease and root blockage in a line that was not on an adequate cleaning frequency and had no level monitoring. The response itself also contributed to the volume: the crew arrived at 06:40 and cleared at 08:10, so 90 minutes of overflow occurred after discovery.
Corrective actions to commit to:
- CCTV the reach, cut roots, and repair any structural defects found.
- Place the manhole on a high-risk list with a defined cleaning frequency and a level logger; install a level alarm with telemetry if the consequence of failure is high.
- Establish or strengthen a FOG program: ordinance authority, inspections of upstream food service establishments, grease interceptor maintenance records, and a public awareness mailing.
- Review dispatch: pre-position a combination unit and a portable pump so a known repeat location can be contained faster.
- Capacity check on the reach using the logged flows.
How you prove it worked:
- Track SSOs per 100 miles of sewer per year, repeat stoppages at this location, and mean time from call to arrival and to containment.
- Review level-logger data through the next wet season.
- Report these metrics monthly to management and include them in the annual report.
- Hold a post-incident review within 10 days and record the changes made.