Back to News
GeneralJul 7, 2026

EPA Reinstates the Title V Emergency Defense. The Protection Is Back, and the Burden of Proof Is Yours.

EPA Reinstates the Title V Emergency Defense. The Protection Is Back, and the Burden of Proof Is Yours.

If you hold a Clean Air Act Title V permit, a protection your predecessors relied on for decades just came back from the dead. On June 1, 2026, the EPA published a direct final rule reinstating the emergency affirmative defense provisions it removed in 2023, after a federal appeals court threw out the removal.

The instinct is to file this under good news and move on. Slower read: the defense has never been a free pass. It is a burden of proof, and the burden sits on your records. A facility with thin documentation holds a defense it cannot use.

Key takeaways

  • The EPA reinstated the Title V emergency affirmative defense by direct final rule on June 1, 2026, restoring the regulatory text that existed before the 2023 removal.

  • The reversal was forced by the D.C. Circuit, which vacated the 2023 rule in September 2025 and held that the EPA’s legal justification for removing the defense was wrong.

  • The defense applies to exceedances of technology-based emission limits caused by qualifying emergencies: sudden, reasonably unforeseeable events beyond the facility’s control.

  • It is an evidence game. You must show proper operation and maintenance before the event, immediate corrective action during it, and timely notice after it, all documented.

  • Nothing about your permit limits, monitoring, or reporting obligations changed. The EPA is explicit that facilities should keep investing in maintenance, prevention, and rapid response.

What happened

Title V of the Clean Air Act requires major sources of air pollution to hold operating permits that pull all applicable air requirements into one document. For decades, the EPA’s Title V regulations included an affirmative defense: a facility that exceeded a technology-based emission limit during a qualifying emergency could assert the defense against penalties, provided it could prove the event met strict conditions.

In 2023, the EPA removed those provisions, reasoning that they intruded on the courts’ role in deciding liability and penalties. Industry groups sued. In September 2025, the U.S. Court of Appeals for the D.C. Circuit vacated the removal in SSM Litigation Group v. EPA, finding the rescission “based entirely on erroneous legal grounds”: the defense is a complete defense to liability rather than a limit on judicial remedies, and it does not make emission standards non-continuous.

The June 2026 direct final rule carries out that mandate and restores the prior regulatory language. In the agency’s words, the action restores “longstanding protections for manufacturers, energy producers, and other facilities that exceed emissions limits due to unavoidable events such as equipment malfunctions or natural disasters.”

What counts as an emergency

The reinstated text defines an emergency as a situation arising from sudden and reasonably unforeseeable events beyond the control of the source, including acts of God, that requires immediate corrective action to restore normal operation and causes the source to exceed a technology-based emission limitation due to unavoidable increases in emissions.

Read the definition like an auditor, because one day someone will. Every clause is a test. Sudden: a failure that crept up on trend data is arguable. Reasonably unforeseeable: a breakdown your maintenance backlog predicted is not. Beyond the control of the source: an operator error or a skipped PM will sink the claim. Immediate corrective action: your response timeline will be reconstructed from records, or it will not be reconstructed at all.

The defense is a records program

Here is the part that deserves budget attention. To assert the defense, a facility has historically needed to demonstrate, through contemporaneous operating logs or comparable evidence, that an emergency occurred and the cause can be identified, that the facility was being properly operated at the time, that all reasonable steps were taken to minimize emissions during the event, and that notice of the emergency reached the permitting authority within two working days.

Notice what that list really is: a documentation program running continuously before, during, and after an event you cannot schedule.

Before: the “properly operated” element is proven by boring, current paperwork. Maintenance procedures that match the equipment as it exists today. PM schedules with completion records. Operator training tied to the current version of each procedure. A three-year-old SOP that no longer matches the machine is not neutral; it is evidence against you.

During: the “immediate corrective action” and “reasonable steps” elements live in timestamps. Who saw the event, what they did, in what order, and when. If your emergency response steps exist as tribal knowledge, the record of following them will be thin exactly when you need it thick.

After: two working days is a short window when an incident is still being stabilized. The notice obligation belongs in your incident workflow as a hard step with an owner, not in someone’s memory.

This is the same closed-loop discipline that drives [audit-ready operations](/blog/audit-ready-safety-operations) generally: procedures that are version-controlled and trained, incidents logged at the point of work with timestamps and evidence, and follow-up actions tracked to verified closure. Facilities running that loop already hold the proof the defense demands. Facilities planning to assemble it after the event will discover the assembly is the hard part.

What this changes for your team, and what it does not

The reinstatement restores a shield you may never need and should never plan to need. Permit limits, monitoring, recordkeeping, and reporting obligations are untouched. The EPA said it plainly: facilities are still encouraged to invest in “maintenance, prevention, and rapid-response systems” to prevent and minimize emissions during unforeseen events.

Legal commentators are giving clients the same caution. The defense is narrow and fact-specific, and the facility carries the burden of proof if it intends to invoke it.

A short list worth acting on this quarter:

  1. Confirm your emergency response and malfunction procedures exist as current, approved documents, and that operators are trained on the versions in force.

  2. Check your PM program’s paper trail: schedules, completions, and deferrals. Deferred maintenance reads badly in an emergency narrative.

  3. Put the two-working-day notice into your incident reporting workflow as an assigned, dated step.

  4. Make incident capture timestamped and mobile, so the during-event record builds itself.

  5. If your state runs its own Title V program, watch how it responds to the reinstatement before assuming the defense’s exact contours at your site.

What comes next

The EPA issued the change as a direct final rule on the view that implementing a court mandate is not controversial. Unless the agency receives adverse comments, it takes effect without further rulemaking. Litigation over emergency provisions in air permitting has run for more than a decade, so treat this as the current chapter rather than the last one, and keep your compliance calendar pointed at both the Federal Register and the courts.

Frequently asked questions

What is the Title V affirmative defense?

It is a regulatory provision letting a Title V permit holder defend against penalties for exceeding a technology-based emission limit when the exceedance was caused by a qualifying emergency. The facility must prove the emergency occurred, that it was properly operating beforehand, that it took all reasonable steps to minimize emissions, and that it notified the permitting authority within two working days.

Why did the EPA reinstate it?

Because a court ordered the result. The D.C. Circuit vacated the EPA’s 2023 removal rule in September 2025, holding the agency’s legal reasoning was inconsistent with the Clean Air Act and precedent. The June 1, 2026 direct final rule restores the provisions to carry out that mandate.

Does the defense excuse noncompliance?

No. The exceedance is still a violation of the permit limit, and the underlying obligations still apply. The defense is a mechanism for avoiding penalties when strict conditions are met and proven. It is asserted after the fact and succeeds or fails on the facility’s evidence.

What counts as a qualifying emergency?

A sudden, reasonably unforeseeable event beyond the source’s control, including acts of God, that requires immediate corrective action and causes an unavoidable exceedance of a technology-based limit. Events traceable to poor maintenance, operator error, or foreseeable wear generally do not qualify.

What records support an affirmative defense claim?

Contemporaneous operating logs or comparable evidence covering the whole arc: maintenance and training records showing proper operation before the event, timestamped incident records showing the response during it, and proof of notice to the permitting authority within two working days after it.

Does this apply automatically in every state?

The reinstatement restores the federal program text and the model language for state programs. States administer their own approved Title V programs and responded differently to the 2023 removal, so confirm the current provision in your state’s rules before relying on it.

Sources

  1. EHS Leaders: EPA Reinstates Title V Affirmative Defense Provisions (July 2, 2026)

  2. Federal Register: Rescission of Title V Emergency Affirmative Defense Rule (June 1, 2026)

  3. EPA news release: EPA Withdraws 2023 Affirmative Defense Rule

  4. D.C. Circuit opinion summary: SSM Litigation Group v. EPA, No. 23-1267 (September 5, 2025)

  5. Federal Register: Removal of Title V Emergency Affirmative Defense Provisions (July 21, 2023)

Your emergency defense is only as strong as your records. Start with ForgeSOP for free and keep procedures, maintenance checklists, incidents, and corrective actions in one audit-ready system.

General
See it in ForgeSOP: SOP and quality managementCAPA softwareAudit & inspection software

Forge better processes

One platform. Always audit-ready.

Bring SOPs, checklists, audits, incidents, and CAPAs into one connected system for safer, clearer, and more consistent operations.

No credit card required · Built for teams that run on process