APRIL 10, 2026  ·  DEC signed the SPDES permit. Zero enforceable PFAS limits. Read the permit analysis →
Home  /  The Case  /  The Dilution

DEC's job was to protect the water. Instead it watered down the evidence.

The permit builds a monitoring point that can measure Micron's PFAS on its own — undiluted, straight off Micron's treatment line. Then it checks for PFAS somewhere else: downstream, after the discharge is mixed with municipal sewage flow. The number that lands on the public report reads 2 to 3 times lower than what Micron actually sends out the pipe. Not an oversight. A design choice that produces a smaller number.

The industrial section of this plant has not been designed or built. The design-build contract has not been awarded. Every flow and monitoring point below is fixed by the signed permit that will govern it — SPDES No. NY0030317, effective May 1, 2026. This can still be changed before the contract is signed.

The permit sends the water out three doors

Page 3 of the permit defines three discharge points. Two are internal — measured inside the plant. The third is the pipe that actually reaches the Oneida River.

The municipal stream (Outfall 01A, 13.3 MGD) and Micron's industrial stream (Outfall 01B, 8.25 MGD) merge into the combined outfall (001, 21.55 MGD) to the Oneida River. PFAS is measured at the combined, diluted point, not on Micron's stream.
Micron's stream is a fraction of the flow at the point PFAS is checked. Phase 2 figures shown; the ratio shifts by phase.
Outfall 01A · internal

The municipal train

Treated sanitary and process wastewater. The everyday sewage side of the plant.

Outfall 01B · internal

Micron's industrial train

Micron's treated process water. This is the stream that carries the PFAS. DEC built this point specifically to see Micron's discharge on its own, before it mixes with anything.

Outfall 001 · to river

The combined outfall

Where 01A and 01B merge and flow to the Oneida River. The diluted point.

PFAS is checked at the one place it's already diluted

The permit's full 40-compound PFAS panel — the "Emerging Contaminants" section, pages 28 to 34 — is assigned to Outfall 001, the combined point. Not to 01B, the point built to see Micron's stream clearly.

At 01B, the permit measures flow, pH, oxygen demand, solids, ammonia, phosphorus, fluoride, aluminum and bacteria — plus a single one-time "industrial pollutant scan." By the permit's own footnote, the results of that one scan are not even reported on the monthly discharge monitoring report the public can see.

The one monitoring point built to see Micron's PFAS clearly is the one point where PFAS is never routinely measured. The panel sits downstream, in the diluted flow, where the number comes out smaller.

Same chemicals, more water, smaller number

Concentration is mass divided by volume. Because the PFAS comes from Micron's process water, checking at the combined outfall spreads that mass across the municipal flow too. The understatement is simply the ratio of combined flow to Micron's flow — and the permit sets both, phase by phase.

Permitted flows & the resulting understatement
Operating phaseMunicipal
01A
Micron's
01B
Combined
001
PFAS reads
this much low
Phase 1municipal only13.313.3
Phase 2industrial, 1st portion13.38.2521.552.6×
Phase 3industrial, full14.38.2522.552.7×
Phase 4full buildout14.316.530.81.9×
All figures MGD (million gallons/day), monthly-average flow limits · permit pp. 12–15, 19–21, 25–27

What that looks like: a concentration leaving Micron's train at, say, 260 ng/L would read about 100 ng/L at the point the permit checks it in Phase 2. That example is illustrative — the plant isn't built and no PFAS has been measured — but the multiplier itself is fixed by the permitted flows, not estimated.

Stated plainly: this assumes the PFAS load originates in Micron's process stream. Any PFAS in the municipal flow would be on top of this — it does not undo the dilution of Micron's stream at the combined point.

And the pool it's diluted into is inflated on purpose

There is a second dilution, and it starts before the water reaches the plant — at the fab itself. Micron's Clay fabs are the same size as its newest Boise fab: 600,000 square feet of cleanroom each, both leading-edge DRAM, same company, same chip. But Clay is designed to draw roughly twice the water per fab. More water in means more wastewater out — the same PFAS mass dissolved into a bigger pool, and a lower number at the outfall for reasons that have nothing to do with the chips.

Same fab · twice the water
 Boise ID1
newest Micron fab
Clay, NY
per fab
Cleanroom size600,000 sq ft600,000 sq ft
Chip madeleading-edge DRAMleading-edge DRAM
Water use5.5 MGD~12 MGD
Water use capped in permit?Yes — binding limitNo
On-site reuse rate committed?75% process reclaimNone
Cleanroom size: NIST / U.S. Commerce · Boise water: 2024 NIST EIS · Clay water: Micron DEIS, 48 MGD ÷ 4 fabs

The difference isn't the fab and it isn't the technology — it's recycling. Idaho's water permit legally caps Micron's use, and Micron reclaims 75% of its process water there. New York's permit caps nothing. For Clay, Micron commits to no on-site reuse rate at all — only an aspiration to reach "100% reuse, recycling and restoration," a figure it can satisfy by funding water projects in other states or countries rather than reusing the water here.

Same fab. Half the water in Idaho. Why does New York get no water limit and no reuse commitment — when every extra gallon dilutes the PFAS reading while sending the same mass into Lake Ontario's watershed?

Held honest: Clay's per-fab water runs 7.85 to 12 MGD across filings and phases, versus Boise's 5.5 — so the claim holds even at the low end (still ~1.4×) and is strongest at full buildout. And this is a separate layer from the in-plant dilution above. Three different mechanisms; we never multiply them into one number.

Two things this page does not claim

The argument only helps if it survives an engineer reading the permit. So two boundaries we hold to.

Boundary 01

This is not the river's dilution

Once the water leaves the plant, the Oneida River dilutes it again. That is a separate, additional layer. This page is only about the dilution inside the plant, before the water reaches the river. The two are never stacked into one number without saying which is which.

Boundary 02

The masking is worst early

At full buildout Micron's flow grows to outweigh the municipal flow, so the multiplier falls to 1.9×. The 2.6 to 2.7× figures apply to the plant's first years — exactly the window when a clean starting baseline matters most.

One metal gets a hard limit. Forty forever chemicals get watched.

At the very same combined outfall, mercury and PFAS are treated in opposite ways — which is how you know the choice was deliberate, not a limitation of the science.

Mercury — at Outfall 001
Enforceable compliance level

A hard limit the discharge cannot exceed. The permit lists a calculated water-quality limit of 0.7 ng/L and enforces it.

PFOA / PFOS — at Outfall 001
Action level only

The permit's own definitions (page 4) call an action level a monitoring trigger — not a restriction. The other 38 PFAS compounds are monitor-only.

same outfall · same sampling point · opposite enforcement

Move the PFAS panel to 01B. It already exists.

Nothing has to be built. Outfall 01B is already in the permit. Assign the PFAS panel to it, and the permit measures Micron's discharge before municipal sewage dilutes it. A sampling method — even the TOP Assay and Method 1633A the campaign demands — means little if it's run at the diluted point.

This is one move, not the whole game.

The dilution trick is a single example of a permit written to look regulated while letting PFAS through. The action-levels-instead-of-limits swap, the 38 monitor-only compounds, the aquatic-life yardstick used for PFAS while a human-health yardstick governs mercury — they run on the same logic. See the full record.

Straight from the signed permit

Every figure on this page is drawn from the signed SPDES permit. Nothing here is modeled or inferred beyond the flow arithmetic the permit itself sets.

1
NYSDEC. SPDES Permit No. NY0030317, Oak Orchard Wastewater Treatment Plant. Signed; effective May 1, 2026. Page 3 — three outfalls defined: 01A Municipal Treatment Train, 01B Industrial Treatment Train, 001 combined discharge to the Oneida River.
2
SPDES Permit NY0030317, page 4 — Definitions. "Action level" defined as a monitoring trigger; "compliance level" defined as an effluent limitation.
3
SPDES Permit NY0030317, pages 14–15 — Outfall 01B parameter table: flow, pH, CBOD5, TSS, settleable solids, TDS, ammonia, total phosphorus, fluoride, aluminum, fecal coliform, chlorine, and a one-time Industrial Pollutant Scan (footnote: results not submitted on the DMR). No PFAS panel.
4
SPDES Permit NY0030317, pages 28–34 — "Emerging Contaminants Permit Levels and Monitoring," assigned to Outfall 001. The full 40-compound PFAS array, including PFOA and PFOS.
5
SPDES Permit NY0030317, flow limits by phase — Phase 2 pp. 12–15, Phase 3 pp. 19–21, Phase 4 pp. 25–27. Municipal (01A) and industrial (01B) monthly-average flow limits; combined figure is their sum (Outfall 001 flow is listed as "Monitor," no numeric cap).
6
SPDES Permit NY0030317, Outfall 001 mercury lines — total mercury carries a Compliance Level (an enforceable effluent limitation); the permit states a calculated WQBEL of 0.7 ng/L.
7
U.S. Department of Commerce / NIST CHIPS. Cleanroom size — each Clay fab and each Boise fab has approximately 600,000 sq ft of cleanroom, leading-edge DRAM. nist.gov/chips
8
Water use — Boise ID1: 5.5 MGD (2024 NIST Environmental Assessment for the ID1 expansion). Clay: ~48 MGD at four-fab buildout, ~12 MGD per fab (Micron New York DEIS); Fab 1 quoted at 7.85–11.5 MGD across county and DEIS filings. Idaho evaporative-water cap (under 1.4 MGD) is a binding condition of Micron's Idaho Department of Water Resources permit; Boise process-water reclaim of 75% per Micron. Clay New York commitment is the non-numeric "100% water reuse, recycling and restoration" language repeated across the DEIS, Micron NY fact sheet, and Commerce/NIST filings; no Clay-specific enforceable reuse rate appears in any document of record.