NESHAP Subpart ZZZZ: Remote Engine Compliance for Stationary RICE
EPA's broadened definition of 'remote' sites lets qualifying stationary RICE engines comply through management practices instead of emissions testing. Here's who qualifies and what's required.
If your facility operates stationary reciprocating internal combustion engines (RICE) — compressor stations, backup generators, irrigation pumps, landfill gas engines — you’re regulated under NESHAP Subpart ZZZZ (40 CFR Part 63). But not all engines face the same compliance burden. EPA’s broadened definition of “remote” sites, finalized January 30, 2013 (78 FR 6674), creates a materially different compliance pathway for engines in isolated locations: management practices instead of emissions testing.
⚡ TL;DR — Stationary RICE engines at remote sites (≤5 buildings within 0.25 miles, or on qualifying gas pipeline segments) can comply with NESHAP Subpart ZZZZ through documented maintenance practices instead of emissions testing and control equipment. The definition was broadened in 2013 and remains current as of 2026. A 2024 electronic reporting rule now requires CEDRI submission for all RICE engines.
What NESHAP Subpart ZZZZ Regulates
Subpart ZZZZ establishes National Emission Standards for Hazardous Air Pollutants from stationary RICE at both major and area sources. Originally promulgated June 15, 2004 (69 FR 33474), with major amendments for spark-ignition (SI) engines in August 2010 (75 FR 51859) and compression-ignition (CI) engines in March 2010.
The primary HAP regulated is formaldehyde, with carbon monoxide (CO) used as a surrogate in many testing scenarios. Other HAPs addressed include acetaldehyde, acrolein, methanol, and volatile organic compounds.
Engine types covered: CI engines (typically diesel-fired) and SI engines (typically natural gas or gasoline-fired) that are stationary — not mobile or used to propel vehicles.
Industries affected: Oil and gas operations (compressor stations, dehydration units), landfills, mining, agriculture (irrigation pumps, digester gas), backup power generation, and remote renewable energy operations.
⚠️ What Goes Wrong — Facilities that misclassify non-remote engines as remote face audit exposure. EPA regional offices verify remote status during compliance inspections by checking building counts and distances against 40 CFR § 63.6675 criteria. Misclassification means you’ve been operating without required emissions controls — potentially for years — and every day of noncompliance is a separate violation.
The Remote Engine Definition (40 CFR § 63.6675)
EPA broadened the definition of “remote stationary RICE” in January 2013 to recognize that engines in genuinely isolated locations pose minimal public health risk and that compliance costs for emissions testing are disproportionately burdensome for these operations. An engine qualifies as remote if it meets any of these four criteria:
1. Offshore Location
Engines located beyond the line of ordinary low water along the U.S. coast, beyond the seaward limit of inland waters.
2. Gas Pipeline Segment
Engines on gas pipeline segments where all of the following are true:
- 10 or fewer buildings intended for human occupancy within 220 yards (200 meters) on either side of the pipeline centerline, in any continuous 1-mile segment
- The pipeline segment does not lie within 100 yards of any occupied building or public assembly area with 20+ persons present at least 5 days per week for 10 weeks per year
- The engine is within 50 yards of the pipeline centerline
3. Non-Pipeline Remote Location
Engines not on gas pipelines with 5 or fewer buildings intended for human occupancy and no buildings with four or more stories within a 0.25-mile radius of the engine.
4. Remote Areas of Alaska
The 2013 amendments specifically expanded this definition beyond “not on the Federal Aid Highway System” to include engines in areas connected to the Federal Aid Highway System only through the Alaska Marine Highway System (AMHS) or within an isolated grid not connected to the Alaska Railbelt Grid, where at least 10% of generated power serves residential purposes and area source generating capacity is less than 12 megawatts or the engine is exclusively backup for renewable energy.
Need help determining whether your engines qualify as remote? iSi’s environmental compliance team evaluates RICE engine classifications and builds compliance documentation for facilities in 40+ states. Request a compliance review →
Remote vs. Non-Remote: What’s Required
The compliance pathway differs dramatically depending on classification.
Non-Remote Engines (Standard Compliance)
Existing 4-stroke SI engines above 500 HP at area sources must meet emission limits:
- 4-Stroke Rich Burn (4SRB): Reduce formaldehyde by 76% OR limit concentration to 350 ppb
- 4-Stroke Lean Burn (4SLB): Reduce CO by 93% OR limit concentration to 14 ppm
This requires emissions testing (initial and periodic), continuous monitoring where applicable, and operating parameter limits tied to certified control equipment.
Remote Engines (Management Practices)
Remote engines comply through documented maintenance instead of emissions testing:
- Oil and filter changes on manufacturer-recommended schedules
- Spark plug inspection and replacement
- Air cleaner inspection and replacement
- Hose and belt inspection and replacement
- Records of all emission-related repairs and maintenance
Record-keeping: Maintain records for five years — on-site for at least two years, off-site storage acceptable for the remaining three.
2024 update: The oil change frequency requirement was clarified to “within 1 year plus 30 days” of the previous change, replacing the ambiguous “annually” language (89 FR 69428, August 30, 2024).
How Subpart ZZZZ Interacts with NSPS Rules
Three federal rules govern stationary engine emissions:
| Standard | Coverage | Citation |
|---|---|---|
| NESHAP Subpart ZZZZ | HAPs from RICE at major and area sources | 40 CFR Part 63 |
| NSPS Subpart JJJJ | New/modified SI engine emissions (CO, NOx, PM) | 40 CFR Part 60 |
| NSPS Subpart IIII | New/modified CI engine emissions (CO, NOx, PM) | 40 CFR Part 60 |
Key rule: Engines meeting the more stringent NSPS standards (Subpart JJJJ for SI, Subpart IIII for CI) automatically satisfy NESHAP Subpart ZZZZ requirements — no duplicative compliance required.
Recent Regulatory Changes
Electronic Reporting Requirement (2024)
EPA finalized amendments August 30, 2024 (89 FR 69428) requiring electronic submission of records and reports via the Compliance and Emissions Data Reporting Interface (CEDRI). This applies to all three RICE rules — NESHAP ZZZZ, NSPS IIII, and NSPS JJJJ. Paper submission is no longer acceptable.
Compliance deadline: 180 days after the effective date, or 1 year from when the CEDRI template is available, whichever is later.
Affirmative Defense Removed (October 2024)
EPA removed the regulatory affirmative defense provision that previously allowed violators to demonstrate they were unaware of violations under certain circumstances. This applies to oil and gas facility NESHAPs including stationary engine regulations — the compliance bar is now strict liability.
Delaware v. EPA (2015) — Emergency Engine Limits
The D.C. Circuit Court vacated EPA’s provision allowing emergency backup generators to operate up to 100 hours per year for emergency demand response purposes (Delaware v. EPA, 785 F.3d 1). EPA removed the vacated provisions from the CFR via ministerial action on August 10, 2022 (87 FR 48826). Emergency engines are now limited to true emergency and maintenance/testing operation only.
💰 The Cost of Getting It Wrong — Clean Air Act civil penalties run up to $121,373 per day per violation under the current Federal Civil Penalties Inflation Adjustment. A stationary RICE engine operating for years under an incorrect remote classification accumulates violations daily. A single NESHAP violation at a major source can also trigger Title V permit noncompliance — multiplying the enforcement exposure.
Frequently Asked Questions
How do I know if my stationary engine qualifies as remote?
Count buildings intended for human occupancy within a 0.25-mile radius of the engine (non-pipeline locations) or within 220 yards of the pipeline centerline (pipeline locations). “Intended for human occupancy” means the primary use involves human presence — not storage sheds or equipment shelters. If you meet the building-count thresholds in 40 CFR § 63.6675, your engine likely qualifies. iSi can perform a formal classification review with documentation.
What happens if my engine was classified as remote but conditions change?
If new buildings are constructed within the threshold distances, your engine may lose its remote classification. You would then need to comply with full emissions testing and control requirements. EPA expects operators to re-evaluate remote status when surrounding conditions change — this is an active compliance obligation, not a one-time determination.
Do I need to file anything under the new electronic reporting rule?
Yes. The August 2024 final rule (89 FR 69428) requires all RICE engines — remote and non-remote — to submit records and reports via CEDRI. This includes management practice records for remote engines. Paper submission is no longer acceptable after the compliance deadline.
Does Subpart ZZZZ apply to emergency generators?
Yes, but with different requirements. Emergency engines have separate compliance pathways under Subpart ZZZZ. Following the Delaware v. EPA (2015) vacatur, emergency engines cannot be operated for demand response — only for true emergencies and maintenance/testing.
Which states have their own RICE air quality rules?
NESHAP Subpart ZZZZ applies uniformly across all states — no state can narrow the remote definition. However, some states layer additional permitting requirements. Kansas (KDHE), Texas (TCEQ), Oklahoma (ODEQ), and Missouri (MoDNR) each have state-level permitting processes that may apply in addition to federal NESHAP requirements. iSi navigates both federal and state air compliance for RICE engines across 40+ states.
Think your facility satisfies every one of these requirements? Find out in 15 minutes →
We Plug In. You Level Up.