Determine the current, post-litigation status of the RICE NESHAP's operating-hour limits for emergency stationary engines, including the 50-hour non-emergency/demand-response allowance
domain: ecfr.gov · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm 40 CFR Part 63 Subpart ZZZZ (RICE NESHAP) generally allows emergency stationary RICE up to 100 hours/year for maintenance and readiness testing, with up to 50 of those hours usable for non-emergency situations under specific conditions
Confirm the 50 non-emergency hours may not be used for peak shaving or non-emergency demand response, and may not be used to generate income for a facility supplying power to the grid or under a financial arrangement with another entity (per current eCFR text)
Note the history: a 2015 court decision vacated provisions that had allowed emergency engines to run during grid voltage/frequency deviations or emergency demand response; EPA's final rule reflecting that vacatur took effect August 10, 2022 (Federal Register, Aug 10, 2022)
Pull the live eCFR text for Subpart ZZZZ rather than pre-2022 summaries, since older vendor content may still describe the vacated pre-2015/pre-2022-rule provisions
Known gotchas
A lot of vendor/dealer content online still describes the pre-2015-vacatur rules (e.g., allowing emergency demand-response participation) — always check the effective date of any source against the August 10, 2022 final rule
Genuine 'emergency' operation itself is not hour-limited; only the maintenance/testing (100 hr) and non-emergency (50 hr, carved from the 100) allowances are capped — don't conflate emergency runtime with the capped categories
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?