☎ (888) 264-7050
RICE NESHAP and NSPS Requirements for Emergency Generators

RICE NESHAP and NSPS Requirements for Emergency Generators

Three facts decide whether a backup generator answers to 40 CFR 63 Subpart ZZZZ or to the NSPS: source status, construction date, and ignition type. What each path requires, and what changed in 2024 and 2025.

A backup generator behind a manufacturing plant is governed by one of three EPA engine rules, and three facts decide which one. Whether the plant is a major or an area source of hazardous air pollutants. When construction on the engine commenced. Whether the engine is compression ignition or spark ignition. Most facility people can answer the second and third from the nameplate and the purchase file. The first one is what decides whether the RICE NESHAP reaches the generator at all, and it is the one that gets answered wrong most often.

Answer all three and the payoff is in 40 CFR 63.6590(c)(1). A new or reconstructed stationary engine at an area source satisfies the NESHAP by complying with the New Source Performance Standards, and the regulation says in plain words that “No further requirements apply for such engines under this part.” For a plant that is not a major HAP source and bought its generator in the last twenty years, that is the difference between an NSPS paperwork file and a NESHAP compliance program. The two are not the same size.

There is a second thing worth knowing before the decision tree. On August 30, 2024, EPA amended Subpart ZZZZ at 89 FR 70505. The headline was electronic reporting. The quieter change was a 30-day grace period written into a recurring maintenance deadline that most facilities still calendar as annual. A plant running the old calendar is holding itself to a tighter schedule than the rule requires.

This post stays on the engine rules. Fuel storage, chemical inventory and the occupational side of a generator installation are covered in depth elsewhere on this site, and the hand-off links are at the bottom.

Is my engine “new” or “existing” under the RICE NESHAP, and what date decides it?

40 CFR 63.6590(a)(1) prints three dates, and which one governs depends on engine size and source status. Over 500 HP at a major source, existing means construction or reconstruction commenced before December 19, 2002. At 500 HP or less at a major source, or at any horsepower at an area source, the date is June 12, 2006.

A change in ownership never converts an existing engine into a new one. That is stated directly at §63.6590(a)(1)(iv), and it matters for any plant that came into a generator through an acquisition or an asset purchase. The engine keeps the commencement date it had under the prior owner, and the compliance obligation that goes with it.

The practical problem is proving the date. Commencement of construction is a documented fact, and the documentation is usually in the original construction file, the air permit application, the installation contract, or the engine manufacturer’s shipping records. A nameplate build date is evidence of when the engine was manufactured, which is a separate test under the NSPS, and it is not the same thing as when construction commenced at the site.

Get this wrong in the conservative direction and the cost is real. A facility that assumes its 2009 generator is an existing engine will go looking for management practices under Subpart ZZZZ when the engine is actually new, routed to the NSPS, and subject to a different set of obligations around certified engines and manufacturer instructions. Get it wrong in the other direction and an existing engine sits with no hour meter and no maintenance records at all.

If my plant is an area source of HAP, do I follow Subpart ZZZZ or the NSPS?

40 CFR 63.6590(c)(1) routes you to the NSPS. New or reconstructed stationary RICE located at an area source meets Part 63 by complying with 40 CFR Part 60 Subpart IIII or Subpart JJJJ, and the rule adds that “No further requirements apply for such engines under this part.” An area source is any site below 10 tpy of a single HAP and 25 tpy of all HAP combined.

That paragraph is the structural fact that organizes the whole subpart. §63.6590(c) lists seven categories of engine that satisfy Subpart ZZZZ by complying with the NSPS, and area-source new and reconstructed engines are the first of them. Emergency and limited-use engines of 500 HP or less at major sources are routed the same way under §63.6590(c)(6).

What this does not do is relieve the engine of anything outside Part 63. The NSPS obligations are real, state and local air permitting is a separate track, and the engine’s potential to emit still has to be accounted for in the facility’s permit record. If permitting and potential-to-emit are the live question at your site, that ground is covered in backup generator air permit requirements, which works the permitting side in detail.

The population that gets caught by this is rarely the plant with a permitted engine and a compliance file. It is the plant that carries a backup generator as a facilities asset rather than an emission unit, exercises it monthly because the maintenance contract says to, keeps no hour log, and has never opened a CDX account.

What makes a facility a major source of hazardous air pollutants?

40 CFR 63.6585(b) sets it at a plant site that emits or has the potential to emit 10 tons per year or more of any single hazardous air pollutant, or 25 tons per year or more of any combination of HAP. Anything below both thresholds is an area source under §63.6585(c). For oil and gas production, the determination is made for each surface site.

The phrase that does the work is “potential to emit.” The test is not what the plant actually released last year. It is what the plant could release operating at its physical and operational design capacity, subject to any federally enforceable limits in the permit. A facility that has taken synthetic minor limits to stay under the threshold is an area source only for as long as those limits hold and are being tracked.

Most non-chemical manufacturing plants land on the area-source side. Hospitals, data centers, water and wastewater utilities, grain elevators, school districts, telecom sites and commercial buildings almost always do. Coatings operations, chemical manufacturing and some wood products operations are where the single-HAP threshold starts to get close.

The determination is site-wide, which trips up multi-building campuses and facilities with contiguous properties under common control. The generator does not make the plant a major source on its own. It inherits whichever status the plant already has, and that status then decides which half of Subpart ZZZZ the engine falls into. Run the site-wide HAP number first, then come back to the engine.

What is the difference between NSPS Subpart IIII and Subpart JJJJ?

Subpart IIII (71 FR 39172) covers stationary compression ignition engines whose construction commenced after July 11, 2005. Subpart JJJJ (73 FR 3591) covers stationary spark ignition engines whose construction commenced after June 12, 2006. Diesel generators fall under IIII. Natural gas and propane engines fall under JJJJ.

Each subpart adds a manufacture date on top of the construction date. Under §60.4200(a)(2), a stationary CI engine is covered when construction commenced after July 11, 2005 and the engine was manufactured after April 1, 2006, with the date moving to July 1, 2006 for a certified NFPA fire pump engine. On the spark ignition side, the manufacture dates sit at §60.4230(a)(4), where emergency engines above 19 kW are keyed to manufacture on or after January 1, 2009.

For most owners of a 2007-or-later compression ignition engine, compliance is a purchasing decision. 40 CFR 60.4211(c) lets you comply by buying an engine certified to the §60.4204(b) or §60.4205(b) and (c) standards for the same model year and maximum engine power, then installing and configuring it to the manufacturer’s emission-related specifications. §60.4211(a) carries that forward: operate and maintain the engine according to the manufacturer’s written emission-related instructions, change only the emission-related settings the manufacturer permits, and meet 40 CFR Part 1068 where it applies.

Deviating from those instructions has a defined cost, set out at §60.4211(g). Under 100 HP, you keep a maintenance plan and records and run an initial performance test within one year. At 100 to 500 HP, the same obligations apply, with the initial test due within one year of startup or of the deviation. Above 500 HP, add retesting every 8,760 hours of operation or every 3 years, whichever comes first.

Fuel is governed separately. §60.4207 sets diesel fuel requirements for stationary CI engines, referencing the 40 CFR 1090.305 nonroad diesel specification for engines under 30 liters per cylinder from October 1, 2010, and a 1,000 ppm maximum sulfur content for engines at or above 30 liters per cylinder from June 1, 2012. Those two figures reached this post in summarized form and are flagged for verification, so confirm them against the current text of §60.4207 before you write a fuel specification into a purchase contract.

Does my emergency generator need a non-resettable hour meter?

40 CFR 63.6625(f) requires one on existing emergency RICE of 500 brake HP or less at a major source, and on any existing emergency RICE at an area source, if one is not already installed. NSPS §60.4237 requires one on emergency spark ignition engines that do not meet the non-emergency standards, phased by horsepower and build date from July 2008 forward.

The NSPS phase-in runs by size. Engines of 500 HP and up built on or after July 1, 2010 need the meter. Engines from 130 HP to under 500 HP built on or after January 1, 2011 need it. Engines under 130 HP built on or after July 1, 2008 need it. §63.6625(d) adds a separate requirement for emergency 4SLB engines of 250 to 500 HP at major sources, where the meter goes in prior to startup.

The meter is the entire compliance program for an emergency engine, and that is worth sitting with. Every hour-based obligation in the regime rests on it: the 100-hour ceiling for maintenance and readiness testing, the 50-hour non-emergency allowance inside it, the categorical loss of emergency status if either is blown, and the records under §63.6655 that separate emergency operation from everything else. One instrument, required by a paragraph many facilities have never opened, carries the weight of the whole file.

A meter that exists but is never read is the same exposure as no meter. The plants that do this well take a reading on a schedule, write it into the same log that records why the engine ran, and reconcile the total at year end against the 100-hour and 50-hour limits. A monthly exercise program of 30 minutes per month puts an engine at 6 hours a year and nowhere near the ceiling, which is exactly why nobody tracks it. The year the engine runs through a prolonged outage, a load bank test and a utility curtailment request is the year the number matters, and by then the log either exists or it does not.

What happens if a generator exceeds its emergency-operation hour limits?

40 CFR 63.6640(f) attaches no separate penalty to the hours themselves. The consequence is categorical. The engine stops being an emergency engine under Subpart ZZZZ and has to meet all non-emergency requirements, which can mean emission limits, performance testing and continuous compliance demonstrations that the facility never designed for or budgeted.

The hour structure itself is the same in the NESHAP and in the NSPS. §63.6640(f)(1) and §60.4211(f)(1) place no time limit on operation during an actual emergency. §63.6640(f)(2) and §60.4211(f)(2) allow up to 100 hours per calendar year for maintenance checks and readiness testing. §63.6640(f)(3) and (f)(4), with §60.4211(f)(3) on the NSPS side, allow up to 50 hours per calendar year of non-emergency operation, and those 50 hours are counted inside the 100.

What the 50 hours cannot be used for is written into the rule. Peak shaving is out. Non-emergency demand response is out. Generating income is out. Supplying power under a financial arrangement with another entity is out. The only opening is the narrow set of grid-dispatch conditions at §63.6640(f)(4)(ii)(A) through (E), and those conditions are specific enough that a contract should be read against them line by line before anyone signs.

Both clocks reset each calendar year, and the hour-meter record has to show which category each hour belonged to. The headline question of how many hours an emergency engine can run before it loses its status is worked through in detail in backup generator air permit requirements. This section is about what happens on the other side of that line.

Can I use an oil analysis program instead of changing the oil on schedule?

40 CFR 63.6625(i) allows it for compression ignition engines, at the same frequency as the table’s oil change interval. The analysis covers total base number, viscosity and water. The condemning limits: TBN below 30 percent of new, viscosity changed by more than 20 percent from new, or water content by volume above 0.5 percent. Nothing exceeded means no oil change is required.

§63.6625(j) does the same for spark ignition engines, with total acid number in place of total base number. The condemning limit there is a TAN increase of more than 3.0 mg KOH per gram from new, with the same 20 percent viscosity change and the same 0.5 percent water threshold. Under both paragraphs, if any limit is exceeded, the oil and filter get changed within 2 business days of receiving the results.

Now the part that needs saying plainly. The oil change and inspection intervals for existing emergency engines at area sources live in Table 2d of Subpart ZZZZ, and this post does not print them. The intervals move with rule amendments, the table is the controlling text, and a number copied from a secondary source into a maintenance calendar is a number nobody can defend in an inspection. Pull your interval from the current eCFR copy of Table 2d, and run your oil analysis program at that same frequency. The management practices themselves sit at §63.6603, with the operating limitations in Table 2b.

Three other clocks in the subpart are easy to miss. §63.6625(h) caps startup idle at 30 minutes. §63.6640(d) gives new, reconstructed and rebuilt engines a burn-in grace period, where deviations in the first 200 hours from startup are not violations. §63.6640(c) requires a retest within 7 days of restart after an exceedance. None of the three generates paperwork on its own, and all three show up in a file review.

What did EPA’s August 30, 2024 RICE rule change about the annual maintenance deadline?

89 FR 70505 replaced “annually” with “within 1 year + 30 days of the previous change” throughout Tables 2c and 2d, and replaced it with “within 1 year + 30 days of the previous inspection” for spark plug, air cleaner, and hose and belt items. The rule appeared in the Federal Register on August 30, 2024 and was effective the same day.

That is a 30-day grace period inserted into a recurring compliance deadline, and the preamble says so in plain terms. It runs against the direction everyone assumes. A maintenance calendar still carrying a hard annual due date is holding the plant to a standard the rule stopped requiring two years ago, and it converts an ordinary scheduling slip into a self-reported deviation that never needed to be one.

The 2024 rule is worth understanding for what it did not do, too. Section IV.D of the preamble states that “The EPA is not making changes to the emission limits,” and the action is characterized as neither economically significant nor a significant regulatory action under Executive Order 12866. Subpart ZZZZ has had no substantive tightening of its limits since the 2013 amendments. The section-level amendment history since then reads as housekeeping.

For a facility, the practical move is small and concrete. Open the maintenance calendar, find every engine task that reads “annual,” and reset the due-date logic to one year plus 30 days from the date the previous change or inspection actually occurred. The clock runs from the last completed event, so the date has to come out of the maintenance record rather than off a fixed calendar square.

What is CEDRI and when did electronic reporting for stationary engines start?

February 26, 2025, which is 180 days after the 2024 rule’s effective date. 89 FR 70505 requires notifications, performance test results, notifications of compliance status, and annual and semiannual reports to be submitted electronically through EPA’s Compliance and Emissions Data Reporting Interface, reached through the CDX portal.

There is one timing wrinkle. Where electronic reporting is newly required for a semiannual or annual compliance report, the obligation starts one year from the date the report template is made available on CEDRI, whichever is later. That means the applicable date for a given report form depends on when EPA posted the template, so check the template availability date for the specific form your engine triggers.

The part that changes how a plant should think about its records is this: CEDRI submissions are made public, and confidential business information cannot be claimed after submission. An hour log that used to live in a binder in the maintenance office is now feeding a public database. Accuracy in that log stopped being an internal housekeeping question and became a disclosure question.

Setting up the access takes longer than people expect, because CDX registration, role assignment and the CEDRI module all have to be in place before a report is due. A facility that has never filed electronically should get the account built well ahead of the first submission rather than during the week it is due.

Are the 50-hour non-emergency provisions still valid after the court remand?

§63.6640(f)(3) and (f)(4) still carry the 50-hour allowance in the Code of Federal Regulations. EPA’s 2024 preamble states that the agency solicited comment on the appropriate next steps “following remand of the provisions specifying that emergency engines can operate for up to 50 hours per year … by the court,” and that it “is not responding to these comments or taking further action on these provisions at this time.” The allowance stands, unresolved.

Section III.F of the same preamble repeats the position: “The EPA did not propose and is not finalizing, any changes to the 50-hour provisions at this time.”

EPA’s own text goes no further than that. It refers to “the court” and to the “remand,” and it names nothing else. Anything beyond those two words would be a characterization rather than a citation, so this post stops where the agency’s text stops.

The practical risk framing is what matters at a plant. If a facility is building a demand response arrangement, a load management program or a utility dispatch agreement on top of §63.6640(f)(4)(ii), it is building on a provision the agency has publicly declined to either defend or revise. The provision is enforceable today, and it is also the piece of this rule most likely to change without much warning. A multi-year contract that depends on it should say what happens if it moves.

How long must RICE NESHAP records be kept?

Five years following each occurrence, measurement, maintenance activity, corrective action, report or record, kept readily accessible, under §63.6660. The required records at §63.6655 include notifications and reports, malfunction occurrences and durations, performance tests, control equipment maintenance, corrective actions, and hour meter readings that separate emergency operation from non-emergency operation.

That five-year figure came out of a summarized read of §63.6660 rather than the section text itself, and it is flagged for verification. Confirm it against the current eCFR before you set a records destruction schedule, because a retention policy that discards a year too early is the kind of error that only surfaces during an inspection.

The record that carries the most weight is the simplest one. For each run, write down the date, the start and stop times, the hour meter reading at each end, and the reason the engine ran. The reason field is what sorts an hour into the emergency bucket, the maintenance and readiness bucket, or the 50-hour non-emergency bucket, and a log without it leaves the facility unable to prove which limit it was operating under.

Readily accessible has a practical meaning as well. Records held in a contractor’s system, or in a maintenance platform the plant cannot export from, are a problem when an inspector asks for five years of engine runs and the answer takes two weeks. Keep a copy where the environmental file lives.

What is the penalty for a Clean Air Act violation involving a stationary engine?

40 CFR 19.4 Table 1 sets the maximum civil judicial penalty under 42 U.S.C. 7413(b) at $124,426 for penalties assessed on or after January 8, 2025. Administrative penalties under 42 U.S.C. 7413(d)(1) sit at $59,114 with a $472,901 cap. Table 1 carries no 2026 column, so the January 2025 figures are the current ones.

One caveat belongs with those numbers. Table 1 prints bare dollar amounts with no unit text. The familiar “per day of violation” framing comes from 42 U.S.C. 7413 itself rather than from the table, so the figures above are statutory maximums under section 113 and the per-day characterization belongs to the statute.

No named enforcement case is cited here, and that is deliberate. What is verifiable is the exposure in the penalty schedule and where the exposure actually sits for an engine. It sits in the hour log. The 2024 rule moved reporting into a public system, and a facility that under-reports or mis-reports emergency-engine hours is now doing so into a database anyone can read rather than into a file cabinet.

The second exposure is the categorical one described further up. Losing emergency status does not produce a fine by itself. It produces a set of non-emergency obligations the engine was never configured to meet, and a period of operation during which the facility was out of compliance with every one of them.

Which stationary engines are exempt from the RICE NESHAP entirely?

40 CFR 63.6585(f) exempts existing residential, commercial and institutional emergency RICE located at area sources, provided they do not operate for the grid-support purpose at §63.6640(f)(4)(ii). §63.6590(b)(3) exempts existing emergency, limited use, 2SLB and 4SLB engines above 500 HP at major sources from the subpart and from Subpart A, which includes the initial notification.

Two more routes narrow the obligation without removing it. Under §63.6590(b)(1)(i), a new or reconstructed emergency engine above 500 HP at a major source owes an initial notification under §63.6645(f) and nothing further under the subpart. Under §63.6590(c)(6), an emergency or limited-use engine of 500 HP or less at a major source goes the NSPS route.

Read the §63.6585(f) exemption carefully before relying on it, because the grid-support condition is a live trigger. An institutional emergency engine enrolled in a utility program that dispatches it for grid reliability can operate its way out of the exemption without anyone at the facility treating it as a regulatory decision.

Engine location can matter as well. EPA’s treatment of remote stationary engines is worked through in EPA’s broadened definition of remote sites for stationary engines, which covers how the remote designation interacts with Subpart ZZZZ obligations.

Related requirements this post hands off

Subpart ZZZZ, IIII and JJJJ are federal rules that apply nationwide, and the applicability logic at §63.6590 does not change at a state line. State and local permitting is a separate track and it does vary, which is why those questions live in their own posts rather than here.

Where to start on your own engines

Build the list before you build the program. For each stationary engine on site, write down the brake horsepower, the ignition type, the documented construction commencement date, the manufacture date, whether it is designated emergency or limited use, and whether a non-resettable hour meter is installed and being read. Then settle the site-wide HAP number so you know which side of §63.6585(b) the plant sits on. Those entries run the §63.6590 decision for you.

Most plants find one of two things. Either the engines route cleanly to the NSPS and the file is thinner than expected, or there is an existing engine at an area source with no hour meter, no maintenance record tied to the Table 2d interval, and a CEDRI account nobody has opened. The second one takes a few weeks to fix and is much cheaper to fix before an inspector asks.

iSi handles air permitting support, engine applicability determinations and compliance calendars for industrial facilities, including the hour-tracking and CEDRI reporting side of Subpart ZZZZ. If you want a second read on which rule your generators fall under, get in touch and we will respond the same day.

Frequently Asked Questions

Which EPA engine rule covers my emergency generator?

Three facts decide it: whether the site is a major or area source of hazardous air pollutants, when construction on the engine commenced, and whether it is compression or spark ignition. A new or reconstructed engine at an area source satisfies Subpart ZZZZ by complying with NSPS Subpart IIII or JJJJ under 40 CFR 63.6590(c)(1).

When is an engine “existing” under the RICE NESHAP?

At an area source, or at 500 HP or less at a major source, existing means construction or reconstruction commenced before June 12, 2006. Over 500 HP at a major source, the date is December 19, 2002. A change in ownership never converts an existing engine into a new one.

How many hours can an emergency engine run outside an actual emergency?

Up to 100 hours per calendar year for maintenance checks and readiness testing under 40 CFR 63.6640(f)(2) and 60.4211(f)(2). Operation during an actual emergency does not count against that allowance. Log the hours from a non-resettable hour meter, because the hour log is what an auditor reads first.

What did the 2024 RICE NESHAP amendments change?

The August 30, 2024 rule at 89 FR 70505 moved compliance reporting into EPA’s electronic CEDRI system and added a 30-day grace period to a recurring maintenance deadline most facilities still calendar as annual. CEDRI submissions are public, so under-reported engine hours now sit in a database anyone can read.

Sources

We Plug In. You Level Up.