NOx RACT and the St. Louis Metro: Why a New Illinois Rule Is a Missouri Story Too
← Back to Blog Environmental

NOx RACT and the St. Louis Metro: Why a New Illinois Rule Is a Missouri Story Too

EPA proposed new NOx RACT limits for Metro-East St. Louis manufacturers. The area is bi-state, and Missouri's half faces the same test on the same clock.

by iSi Environmental

On August 6, 2026, EPA proposed approving new NOx control requirements for industrial boilers, furnaces, and kilns in two Illinois ozone nonattainment areas. Read past the Illinois dateline and there’s a Missouri story inside it: one of those two areas, Metro-East St. Louis, is not an Illinois area at all. It’s a single bi-state nonattainment area that reaches across the Mississippi River into St. Louis County, St. Louis City, St. Charles County, Jefferson County, and part of Franklin County, Missouri. The Missouri half carries its own Serious-area NOx RACT obligation, on its own August 3, 2027 attainment clock, and Illinois just published the best available preview of what that obligation is going to look like.

That matters more than a routine SIP notice would, because a plant manager’s first reaction to a facility-wide “major source” designation is usually the wrong question. The right question isn’t whether your facility is big enough to be covered. It’s whether any single unit inside it meets a narrower, conjunctive test that most coverage of RACT rules doesn’t explain correctly.

What did EPA propose on August 6, 2026?

EPA proposed approving revisions to three Illinois regulations, 35 Illinois Administrative Code (IAC) parts 217, 218, and 219, into the Illinois State Implementation Plan (91 FR 50746). Parts 218 and 219 satisfy Moderate-area VOC RACT. Part 217, the one that matters here, satisfies both Moderate and Serious-area NOx RACT under Clean Air Act sections 182(b)(2), 182(c), and 182(f). The action covers two nonattainment areas: Chicago and Metro-East St. Louis.

This is a proposed rule, not a final one. Comments are due September 8, 2026, at regulations.gov under dockets EPA-R05-OAR-2024-0617, EPA-R05-OAR-2024-0618, and EPA-R05-OAR-2025-0259. Nothing here is settled yet, and a plant manager reading a summary that treats it as final is reading a summary that overstates the current status.

One more scope note before the substance: Serious-area VOC RACT for these same two areas is explicitly deferred to a separate, future EPA action, stated twice in the notice. A facility that clears this round on NOx should expect a second round on VOC later, not treat this notice as the last word.

Why is an Illinois rule a Missouri compliance question?

Because the nonattainment area it covers isn’t only in Illinois. Per the Federal Register notice, the Metro-East area includes “Madison, St. Clair, Monroe counties in Illinois, and St. Louis, St. Louis City, St. Charles, and Jefferson counties, as well as Boles Township in Franklin County in Missouri.” That’s one nonattainment area straddling a state line, the same way a single airshed doesn’t stop at a river.

The Missouri portion was reclassified from Moderate to Serious effective December 31, 2024. It carries the same Serious classification, and the same August 3, 2027 attainment date, as the Illinois portion. Missouri DNR has been developing the Serious-area attainment plan since at least April 2025. Illinois hasn’t finished its own NOx RACT rule yet either, but its proposed rule text, now public and moving through EPA approval, is the closest thing available to a preview of the control level Missouri regulators and EPA will expect on the Missouri side of the same nonattainment area.

That’s a materially different framing than “an out-of-state rule that doesn’t affect us.” A plant in Sauget or Granite City, Illinois, and a plant in south St. Louis County, Missouri, sit inside the same designated nonattainment area and are working toward the same statutory deadline. The rule that lands first tells you what the second one is likely to look like.

Does my facility’s NOx RACT obligation depend on being a “major source”?

Not by itself, and this is where most coverage of RACT rules oversimplifies the rule. Illinois’s new part 217 test is conjunctive: two separate conditions both have to be true before a unit is captured.

  1. The individual unit is one of eight named equipment categories, and it emits at least 15 tons per year of NOx.
  2. That unit sits at a source located in the nonattainment area with facility-wide potential to emit at least 50 tons per year of NOx.

Fail either condition and the unit isn’t captured, no matter how the other one comes out. A facility with 60 tons per year of facility-wide NOx potential to emit, comfortably over the 50 tpy gate, can still have zero captured units if every individual boiler, heater, or furnace sits under 15 tpy on its own. Run the arithmetic the other way and a single 40-tpy unit at a facility whose total potential to emit is only 45 tpy isn’t captured either, because the facility-wide gate isn’t met. “My facility is a major source” and “my unit is a RACT unit” are two different questions, and treating them as the same one is the single most common way this kind of rule gets misapplied.

Which equipment categories does the new rule name?

Eight, not nine, despite how some early summaries of the rule have described it. The Federal Register text names, verbatim: any industrial boiler, process heater, glass melting furnace, cement kiln, lime kiln, iron and steel reheat, annealing, or galvanizing furnace, aluminum reverberatory or crucible furnace, or fossil fuel-fired stationary boiler (91 FR 50748).

Counted as named categories, that’s eight. Two of them, the iron and steel furnace category and the aluminum furnace category, each bundle multiple furnace subtypes, so counting distinct unit types instead of categories gets to eleven. Either count is defensible depending on how you’re using it; what isn’t defensible is a count of nine, which doesn’t match the rule text under either reading.

Two of the eight categories, industrial boilers and process heaters, aren’t sector-specific. That’s the pair worth flagging for a broader audience than metals, glass, and cement producers: any facility running boilers or process heaters at scale, in food processing, chemicals, pulp and paper, or general manufacturing, needs to run the applicability test rather than assume the rule is limited to heavy industry.

What are the exact boundaries of the Metro-East nonattainment area?

Madison, St. Clair, and Monroe counties in full on the Illinois side. On the Missouri side: St. Louis County, St. Louis City, St. Charles County, and Jefferson County, plus only Boles Township in Franklin County, not the entire county. That township-level limit on Franklin County is the detail most likely to trip up a self-check: a facility in western or southern Franklin County, Missouri, outside Boles Township, sits outside the nonattainment area even though it shares a county name with a covered township.

One live iSi post already covers a related but distinct Missouri boundary question. Our St. Louis petroleum vapor recovery piece describes the broader rule-defined St. Louis metropolitan area used for a different program (VOC vapor recovery), which includes the entirety of Franklin County rather than just Boles Township. Different program, different pollutant, different boundary. Don’t use one boundary definition to answer a question about the other.

Can I average NOx emissions across units instead of meeting each unit’s limit?

Yes, but only voluntarily and only at a cost. Illinois’s Economic Incentive Program lets a source meet its NOx RACT obligation in aggregate across units rather than unit by unit. Using EPA’s 2001 presumptive approach, that flexibility comes with a price: an additional 10 percent emissions reduction beyond what unit-by-unit compliance would require (91 FR 50748 to 50749). A source can also simply meet each captured unit’s individual limit and skip averaging entirely. Model both paths before choosing one; the averaging option isn’t automatically the cheaper route once the 10 percent premium is priced in.

When do the new NOx limits actually take effect?

That’s the honest gap in this notice, and it’s worth stating plainly rather than guessing. The Federal Register notice supplies a comment deadline, September 8, 2026, and two state rule effective dates, April 23, 2025 for part 217 and December 9, 2024 for parts 218 and 219. It does not supply a compliance date for the actual numeric NOx limits, and a state rule effective date is not the same thing as a compliance deadline. The compliance schedule lives in the Illinois Pollution Control Board’s rule text, which this brief did not pull and which any facility relying on a specific date should verify directly before treating it as final.

If EPA says the air is clean, why are new limits coming?

Because those are two different legal questions, and the tension between them is real enough that it deserves a direct answer rather than a dismissal. On February 26, 2026, EPA proposed Clean Data Determinations for both the Missouri and Illinois portions of the St. Louis nonattainment area, a status that on its face suggests the area is currently meeting the ozone standard.

A Clean Data Determination suspends specific planning obligations: attainment demonstrations, reasonable further progress plans, reasonably available control measures, and contingency measures. RACT is not one of those. It’s an emission control program, not a planning document, and a federally approved RACT limit stays enforceable regardless of a Clean Data Determination. The area can be reading clean today and still be legally required to adopt and enforce control-technology limits set for its classification. Both things are true at once, and neither cancels the other out.

Is there an active enforcement trend behind this rule?

No, and stating that plainly matters more than manufacturing urgency that isn’t supported by the record. A search across EPA and Federal Register enforcement records covering 2024 through 2026 found no NOx RACT-specific enforcement action. Every recent RACT-related item in the record is a rulemaking, a state implementation plan approval, not a penalty case.

What the record does show is that Illinois air-permit enforcement generally is active, and that federally approved limits are what actually gets enforced once a state rule is in the SIP. Heidtman Steel in Granite City, Illinois, settled for $75,000 in March 2026 over a Title V permit gap and Boiler NESHAP noncompliance on a natural gas-fired industrial boiler, the closest live analogue to what a NOx RACT enforcement case would look like once these limits are approved and in effect. That’s a permit and standards case, not a NOx RACT case specifically, but it’s the right reference point for what federal enforceability means in practice once a state rule clears SIP approval.

What should a Metro-East or St. Louis-area facility do now?

  1. Pull facility-wide NOx potential to emit from the current Title V or FESOP permit and confirm whether it clears 50 tons per year.
  2. Pull unit-level NOx emissions for every boiler, process heater, kiln, and furnace on site, and check each one against the 15 tpy threshold and the eight named categories, matching the rule’s category language rather than the vernacular name for the equipment.
  3. Confirm the facility’s location against the nonattainment boundary at township resolution if Franklin County, Missouri, or Grundy or Kendall County, Illinois, is involved.
  4. Track the Illinois rule as a preview, not a final answer, for Missouri obligations. Missouri’s own Serious-area plan is still in development; Illinois’s proposed part 217 text is the best current indicator of the control level Missouri sources should expect to be measured against.
  5. Comment by September 8, 2026 if a specific limit, boundary, or the averaging premium affects your facility and is worth contesting or clarifying while the rule is still proposed.

Where iSi fits

Running this applicability test correctly, facility-wide potential to emit against the 50 tpy gate, then each individual unit against the 15 tpy trigger and the eight-category list, at township-level boundary precision, is exactly the kind of cross-referencing that gets skipped when it’s someone’s fourth priority on a Tuesday. iSi supports manufacturers across Missouri and the greater St. Louis area with air permitting applicability determinations, emissions inventories, and SIP-tracking for exactly this kind of two-part test, so a facility knows whether it has a RACT obligation before EPA or Missouri DNR tells them so directly.

If your facility sits in the St. Louis metro and runs boilers, process heaters, kilns, or furnaces at meaningful scale, that applicability question is worth answering now, while the Illinois rule is still in comment and before Missouri’s own Serious-area plan firms up further.

Sources

INTERNAL NOTE, not for publication (content-pipeline-draft, 2026-08-07): This draft is staged to drafts_ready/ only. It must NOT be converted to the Astro mirror or moved toward deploy until the publication blocker documented in the source research brief (feynman_research/nox-ract-requirements-manufacturers_2026-08-06.md, CORRECTIONS ANNEX, CONFLICT 1, HIGH) is resolved: the live post ozone-nonattainment-reclassification-requirements.md still states, as of this run, “Kansas, Missouri, Nebraska, and Oklahoma currently have no reclassified ozone nonattainment areas,” a statement this brief’s own sourcing shows is wrong for Missouri (St. Louis portion reclassified Serious effective 2024-12-31, FR Doc 2024-27382). Publishing this new post while that sentence stands live would put two directly contradictory statements about Missouri on the same site. That correction requires editing a live Astro source file and is out of scope for this scheduled run; it belongs to a live Website Build session per the existing routing note at Strategic Intelligence/pending_web_dev_input/nox_ract_illinois_HELD_routing_2026-08-06.md. Word count approximately 2,150. Category “Environmental” is enum-valid. Image path verified on disk. 0 em/en-dashes, 0 banned-phrase hits (manual check this run).

Tags: