Passage Data · Check a report · Use it from your AI

Plants facing new discharge limits — by state and pollutant

In Oklahoma: 8 plants hold a permit with a new or tighter discharge limit already written into it, taking effect between Nov 1, 2026 and Apr 1, 2030 (29 limits); 2 of them reported a median above that limit between Oct 1, 2025 and Sep 30, 2026. EPA's file of Oct 16, 2026.

By state: all · IA 204 · PA 172 · LA 165 · OH 134 · MS 68 · AR 58 · TX 57 · MI 53 · GA 52 · VA 52 · MD 48 · NJ 35 · IN 31 · SC 23 · KS 21 · MN 21 · NY 21 · MO 20 · WV 17 · OR 16 · IL 14 · FL 10 · NE 9 · OK 8 · TN 8 · CO 7 · UT 7 · NM 6 · CA 5 · SD 5 · CT 3 · ID 3 · ME 2 · WI 2 · AL 1 · DC 1 · KY 1 · MT 1 · NH 1 · PR 1 · VT 1 · WA 1

By pollutant: Copper, total [as Cu] 5 · Selenium, total [as Se] 2 · Cadmium, total [as Cd] 1 · Cyanide, total [as CN] 1 · Lead, total [as Pb] 1

Each limit is one EPA's ICIS-NPDES file holds on the permit's current version with a begin date after today, enforceable and numeric, either on a parameter the outfall was never limited on (new) or lower than the limit in force (tighter). Today's median is the plant's own reported values for the same outfall, statistic and unit between Oct 1, 2025 and Sep 30, 2026, with how many; none is shown where most were below a detection limit. Read the permit before relying on a value.

Sell to these plants? The list for your states every week, with every plant over a limit on your pollutant, as a spreadsheet, by API and by email when a new one appears: ask for the plant list, or write to info@passage-data.com. What a seller gets.

For programs and AI agents: a state's permits with these limits as JSON at /api/v1/permits?state=OK&upcoming=true, narrowed with &facility_type=potw or &min_flow_mgd=1; the whole list at /dmr/data/upcoming.json; or add https://passage-data.com/mcp as a remote MCP server (tool list_permits). Free, no key. llms.txt

From EPA's ECHO data, not the permit document itself: your permit is the final word. All states