NPDES ID: ALG110502
D — SNC: Discharge monitoring report not received
The facility didn't submit its required discharge monitoring report.
Mentions
Lake Purdy's inlet is still listed with no cleanup plan
Karst valleys move water fast. Rain falls onto limestone and dolomite bedrock and travels through dissolved channels into springs and streams with almost no natural filtering along the way. That structural vulnerability shows up plainly in the official impairment record for the Southern Limestone/Dolomite Valleys and Low Rolling Hills. Shades Creek and Patton Creek are both listed as impaired under the Clean Water Act with a completed cleanup plan — a TMDL, which sets an enforceable ceiling on how much pollution the waterway can carry. Fivemile Creek is listed as impaired but with other controls expected to address the problem instead of a TMDL. The Little Cahaba River sits in a different spot on that same list. Its Lake Purdy segment (AL03150202-0103-102) is documented as impaired and 303(d)-listed as requiring a TMDL, with no cleanup plan completed. The adjoining upstream segment of the same river is assessed as fully supporting all its designated uses — so the problem is specific to the reservoir end, not the whole stream. That distinction isn't a technicality: until a plan is finalized, there's no binding limit on the pollutant loads reaching that segment and no timeline for improvement. Lake Purdy is also understood to supply drinking water to part of the Birmingham area, which makes the unresolved status at its inlet worth watching rather than filing away. It's tempting to attach a named discharger to that gap, and worth saying plainly that the record doesn't support one. The facility EPA currently lists in significant non-compliance nearest this write-up, FIREROCK PRODUCTS, LLC, sits at 33.4986, -86.9111 — west of Birmingham, in the Village Creek drainage that flows to the Locust Fork and the Black Warrior, a different river basin from the Cahaba. Its violation is also administrative rather than chemical: a required discharge monitoring report was never submitted, with no pollutant exceedance on file. That's a real compliance failure, but nothing in the record connects it to water reaching Lake Purdy, and it shouldn't be read as a source there. What the geology does support is a general caution. Fast-draining bedrock means whatever loads do enter this system reach surface water and springs quickly and with little dilution, so the absence of an enforceable limit matters more in a karst valley than it would where deeper soils and slower runoff buffer the inputs. Identifying what is actually loading the Lake Purdy segment would take the TMDL that hasn't been written yet — which is the point. Until then, the drinking water inlet is the one impaired water here without a ceiling on it, and without a documented cause on the public record either.
Keep readingViolations
December 31, 2025
Solids, total suspended
0% over limit
Discharged 0 mg/L against a permitted limit of 0 mg/L (DAILY MX)
DMR, Monitor Only - Overdue
Rainfall
0% over limit
Discharged 0 m against a permitted limit of 0 m (DAILY MX)
DMR, Monitor Only - Overdue
pH
0% over limit
Discharged 0 SU against a permitted limit of 0 SU (DAILY MN)
DMR, Monitor Only - Overdue
Annual Certification Statement
0% over limit
Discharged 0 pass=0;fail=1 against a permitted limit of 0 pass=0;fail=1 (ANNL TOT)
DMR, Monitor Only - Overdue
pH
0% over limit
Discharged 0 SU against a permitted limit of 0 SU (DAILY MX)
DMR, Monitor Only - Overdue
First flagged
April 14, 2026 (5 months ago)
Last confirmed
September 15, 2026 (6 days ago)