Following EPA enforcement: using ECHO data to track environmental violations and penalties

The Environmental Protection Agency regulates more than 800,000 facilities under four major environmental statutes—the Clean Air Act, the Clean Water Act, the Resource Conservation and Recovery Act, and the Toxic Substances Control Act—and publishes a comprehensive record of every enforcement action it takes against them. That record, housed in the Enforcement and Compliance History Online database known as ECHO, contains facility violations, formal enforcement actions, penalties assessed, penalties paid, and real-time compliance status. What it reveals about which facilities stay in violation for years without consequence, which industries concentrate the most enforcement activity, and where the geography of non-compliance maps against the demographics of environmental justice communities is the subject of this piece.

This article covers what ECHO's four statutory programs track, the data structure underlying each facility record, the Significant Non-Compliance designation and what it means for enforcement prioritization, how to access the database in bulk and via API, three research use cases that surface patterns invisible from summary statistics, the state and federal enforcement split, cross-references to adjacent EPA datasets, and the structural limitations every analyst needs to account for before drawing conclusions.

What ECHO covers: four statutes, one interface

ECHO integrates compliance and enforcement data from four distinct federal environmental programs, each operating under its own statutory authority, regulatory framework, and enforcement logic. Understanding the scope of each program is prerequisite to interpreting what a facility record means.

The Clean Air Act program covers stationary sources of air pollution—power plants, refineries, chemical manufacturers, cement kilns, smelters, and any industrial facility that emits criteria pollutants or hazardous air pollutants above threshold quantities. Regulated facilities must hold operating permits under Title V of the CAA if they are major sources; smaller sources may be regulated under State Implementation Plans. CAA enforcement in ECHO includes permit violations, excess emissions events, failure to conduct required stack tests, and failure to maintain required monitoring equipment. The Clean Air Act is enforced through both the Stationary Source Compliance Division at EPA headquarters and, for smaller sources, through state air agencies operating under delegated authority.

The Clean Water Act program tracks point-source dischargers holding National Pollutant Discharge Elimination System (NPDES) permits. An NPDES permit authorizes a facility to discharge pollutants into navigable waters up to specified concentration and mass limits, subject to monitoring and reporting requirements. The CWA enforcement universe in ECHO includes municipal wastewater treatment plants, industrial direct dischargers, stormwater permit holders, and concentrated animal feeding operations (CAFOs). CWA violations recorded in ECHO include effluent limit exceedances, failure to report discharge monitoring results, unauthorized discharges, and violations of permit conditions for pretreatment programs.

The Resource Conservation and Recovery Act program covers generators, transporters, and treatment, storage, and disposal facilities that handle hazardous waste. RCRA establishes a cradle-to-grave tracking system: waste generators must characterize their waste, use licensed transporters, and ensure disposal at permitted TSDF facilities. ECHO's RCRA data includes generator classification (large quantity, small quantity, very small quantity generator), compliance evaluation results, and formal enforcement actions for waste storage, labeling, manifest, and disposal violations. RCRA enforcement is particularly relevant for industrial facilities that generate process waste streams classified as listed or characteristic hazardous wastes.

The Toxic Substances Control Act program covers facilities that manufacture, import, process, or use chemical substances subject to TSCA reporting and restriction requirements. TSCA enforcement in ECHO primarily reflects PCB handling and disposal violations, asbestos abatement violations, and compliance with chemical data reporting rules. The TSCA enforcement universe is substantially smaller than the CAA and CWA programs in ECHO's database, but it captures chemical industry compliance with EPA's chemical risk management framework.

Data structure: what each facility record contains

ECHO organizes its data around the facility as the primary unit of analysis. Each facility carries a persistent identifier, FACS_ID, that links across programs and across time. For facilities regulated under multiple statutes—a refinery that holds both a CAA Title V permit and a CWA NPDES permit—ECHO maintains program-specific identifiers that link back to the single FACS_ID record. This multi-program linkage is one of ECHO's most analytically valuable features: a facility's compliance history under one program can be evaluated alongside its compliance history under the others.

Beyond the facility identifier, each record contains industry classification codes—both Standard Industrial Classification codes for older records and NAICS codes for more recent ones. Industry codes are the primary stratification variable for cross-sector enforcement analysis: grouping facilities by NAICS two-digit sector and computing violation rates, formal action rates, and average penalties by sector reveals which industries receive enforcement attention proportionate to their regulatory burden and which are effectively under-enforced relative to the size of the regulated universe.

At the violation level, ECHO records the violation type, the date the violation was identified, and the regulatory standard violated. Violation types vary by program: CAA records distinguish between High Priority Violations and other violations; CWA records distinguish effluent limit exceedances from reporting violations and permit schedule violations; RCRA records the specific RCRA subpart violated. The date of violation onset and the date of return to compliance define the duration of the violation period—a critical field for significant non-compliance analysis, discussed below.

Formal enforcement actions in ECHO are classified by type. The four primary formal action types are: administrative penalty orders, which assess a monetary penalty without requiring judicial involvement; compliance schedules, which establish a timeline for returning to compliance without a monetary penalty; injunctive relief, which requires the facility to take specific corrective actions under court or administrative order; and referrals to the Department of Justice, which initiate civil or criminal judicial proceedings for the most serious violations. The action type is the primary signal of enforcement severity in the database: a compliance schedule is the lightest touch; a DOJ referral is the most consequential.

The penalty fields in ECHO record both the penalty assessed and the penalty paid. The assessed figure is the formal penalty amount specified in the enforcement order or settlement agreement. The paid figure reflects what the facility actually remitted. For settled cases, assessed and paid are typically identical. For cases resolved with supplemental environmental projects (SEPs)—where the facility funds an environmental improvement in lieu of paying part of the cash penalty—the paid figure will be lower than the assessed figure by the SEP credit amount. The gap between assessed and paid is an underappreciated analytical variable: it reveals where enforcement outcomes diverge from their nominal financial weight.

Compliance status in ECHO uses a three-category taxonomy: No Violation (the facility has no current violation findings under the program in question), In Violation (the facility has one or more active violation findings), and Significant Violation, which corresponds to the Significant Non-Compliance designation discussed in the next section. The compliance status field is the ECHO user interface's primary filter for identifying enforcement priorities.

The Significant Non-Compliance metric

EPA uses two related designations to identify facilities that pose elevated enforcement priority: Significant Non-Compliance (SNC) for CWA and RCRA programs, and High Priority Violator (HPV) status for the CAA program. Both designations function as enforcement triage signals, identifying the subset of the regulated universe that requires formal EPA response.

Under the CWA NPDES program, a facility earns SNC status through a set of algorithmic criteria applied to its discharge monitoring reports. The criteria include: effluent limit exceedances that exceed a threshold magnitude (typically 40 percent over the monthly average limit or any exceedance of a daily maximum limit for certain toxic pollutants), chronic permit schedule violations (missing or late reporting for two or more consecutive quarters), and failure to report discharge monitoring results for two or more quarters. A facility that triggers any of these criteria is flagged as SNC in ECHO and is supposed to receive a formal response from EPA or the state agency within one quarter.

Under RCRA, SNC designation applies to facilities that have failed to achieve and maintain compliance with a compliance schedule or who have a pattern of violations across multiple compliance evaluations. The RCRA SNC criteria are more judgment-based than the algorithmic CWA criteria: an RCRA inspector's evaluation report and the regional office's assessment of violation gravity drive the designation, rather than a formula applied to self-reported monitoring data.

The CAA High Priority Violator designation functions analogously to SNC for stationary sources. HPV status is triggered by the magnitude of excess emissions, the duration of the violation, whether the facility has a history of prior violations, and whether the violation involves a hazardous air pollutant or criteria pollutant of particular regulatory concern. HPV-designated facilities are listed on EPA's Enforcement and Compliance Dashboard and are supposed to be resolved within one year of designation through either a formal enforcement action or a return to compliance.

The policy significance of SNC and HPV designations is that they create a documented prioritization obligation: a facility in SNC or HPV status is supposed to trigger a mandatory formal response. ECHO's historical records allow analysts to measure whether that obligation is met—by computing the time between SNC designation and the date of the next formal enforcement action, or the date of return to compliance. Facilities that remain in SNC status for multiple consecutive quarters without a formal response represent a documented enforcement gap.

How to access ECHO data

ECHO provides four access channels suited to different research workflows.

The ECHO facility search at echo.epa.gov is the primary web interface. It supports geographic search by state, county, or map area, filtering by program (CAA, CWA, RCRA, TSCA), compliance status, industry sector, and enforcement action type. The facility search produces tabular results that can be exported as CSV for further analysis. For researchers exploring a specific region or industry, the facility search is the fastest route to a scoped dataset.

The ECHO bulk data downloads at echo.epa.gov/tools/data-downloads provide full-database exports across all four programs. Downloads are organized by data type: facility data, inspection data, violation data, formal enforcement action data, and penalty data are separate tables joined by facility identifier. The bulk downloads are updated quarterly and are the appropriate starting point for national-scale analysis. File sizes are substantial: the CWA NPDES effluent monitoring data alone runs to several gigabytes uncompressed.

The ECHO API at echo.epa.gov/tools/web-services provides RESTful access to the same underlying data with field-level documentation. The API supports filtered queries by facility identifier, NAICS code, compliance status, enforcement action type, date range, and geography. API responses are available in JSON and XML. Authentication is not required for public data endpoints. The API is particularly useful for retrieving targeted facility subsets—all CWA SNC facilities in a given state, or all CAA HPV facilities in a specific NAICS sector— without downloading full bulk files.

The Enforcement and Compliance Dashboard at echo.epa.gov/trends provides aggregated trend data at the national, regional, and state level: quarterly SNC counts, formal action counts by program, penalty totals by fiscal year, and compliance rate trends. The dashboard is better suited to policy monitoring than to facility-level research, but its summary statistics are useful as denominators when computing facility-level metrics.

Three research use cases

Significant Non-Compliance duration: how long before EPA acts

The most direct enforcement accountability question the ECHO database can answer is: once a facility is designated Significant Non-Compliance, how long does it stay there before receiving a formal enforcement response? The answer, across the full CWA NPDES universe, is frequently measured in years rather than the quarters that EPA's own policy envisions.

The analytical approach joins the ECHO violation table to the formal enforcement action table by FACS_ID, filters to CWA NPDES records with an SNC flag, and computes the interval between the quarter of initial SNC designation and either the date of the first formal enforcement action or the date the SNC flag was cleared. Stratifying the resulting duration distribution by state reveals wide variation: some states resolve SNC designations within one to two quarters through active formal action programs; others allow facilities to remain in SNC status for four, six, or eight quarters before any response. The variation is partly a function of state enforcement capacity (delegated states vary enormously in inspector staffing) and partly a function of enforcement culture and political priorities.

A refinement of this analysis stratifies by facility size and industry. Large municipal wastewater treatment plants in financial distress are among the most chronic SNC facilities in the CWA database: they regularly exceed effluent limits due to aging infrastructure and are often given extended compliance schedules rather than penalties, because they lack the rate revenue to fund both compliance capital projects and cash penalties simultaneously. Industrial dischargers in the same SNC duration tier are analytically distinct: a petrochemical facility that remains in SNC for six consecutive quarters without a formal response is a fundamentally different enforcement problem than an underfunded rural sewage treatment plant.

Environmental justice analysis: SNC facilities and EJScreen demographics

EPA's EJScreen tool provides census-tract-level demographic and environmental burden indices, including percent minority population, percent low-income population, percent people of color, and composite environmental justice scores. ECHO provides each facility's latitude and longitude coordinates, enabling a spatial join between facility enforcement history and EJScreen demographic data.

The research question is whether SNC facilities—facilities with documented, ongoing significant violations—are disproportionately located in census tracts with higher percent minority or percent low-income populations relative to the full distribution of regulated facilities. Academic research using ECHO and EJScreen data has consistently found that facilities with active SNC designations are located in higher environmental justice burden communities than the median regulated facility, and that the enforcement response time in those communities is longer. The ECHO bulk data download contains the geographic coordinates necessary to construct this analysis without any additional data collection; EJScreen data is separately downloadable from epa.gov/ejscreen.

A methodological caution applies: the fact that SNC facilities are disproportionately located in high-EJ-burden communities does not by itself establish that enforcement is discriminatory. High-EJ-burden communities are also disproportionately located near industrial land uses, which means the underlying regulated facility density is higher in those communities. The correct comparison is not SNC facility location versus residential demographics, but SNC designation rate conditional on facility type and violation history, compared across census tracts with different EJ burden levels. That comparison—which requires controlling for industry type, violation magnitude, and state program—is the analysis that has the strongest evidentiary weight for enforcement disparity conclusions.

Penalty-to-violation ratio: repeat violators with nominal penalties

The third use case joins the violation history table to the penalty table to identify facilities with a large number of documented violations but nominal cumulative penalties. The resulting penalty-to-violation ratio—total penalties assessed divided by total violation-quarters recorded—is a rough measure of the financial consequence per unit of documented non-compliance.

Facilities at the low end of this ratio—many violations, few or no formal actions, minimal penalties—are candidates for further investigation. They may represent facilities that have been repeatedly cited in compliance evaluations but that always return to compliance before a formal action is issued, facilities in states with weak formal action programs, or facilities with sufficient political or economic significance that enforcement has been deferred. A facility with thirty quarters of CWA SNC designation and a cumulative penalty history of zero is an analytically significant observation that the database can surface directly.

Cross-referencing the lowest-ratio facilities against EPA enforcement press releases and regional enforcement priority lists tests whether the apparent enforcement gap reflects a real gap or a data artifact. EPA frequently resolves violations through informal correspondence and facility responses that do not generate formal enforcement actions or ECHO-recorded penalties. A facility that appears penalty-free in ECHO may have in fact received multiple informal enforcement letters that produced compliance without formal action—a pattern that is entirely appropriate and that the database will characterize as a gap because it records only formal outcomes.

The state and federal enforcement split

The Clean Air Act and Clean Water Act are cooperative federalism statutes: Congress established minimum federal standards and enforcement authority but authorized states to assume primary enforcement responsibility once they demonstrate that their programs are at least as stringent as the federal baseline. The result is that most environmental enforcement in the United States is conducted by state agencies, not EPA directly. States that have received EPA approval to administer their own CAA or CWA programs are described as having “delegated” or “authorized” programs.

States with authorized programs are required to submit their inspection, violation, and enforcement data to EPA's program-specific data systems, which feed ECHO. CWA NPDES data flows into the Integrated Compliance Information System (ICIS-NPDES); CAA data flows into ICIS-Air; RCRA data flows into RCRAInfo. ECHO aggregates these three underlying systems into a single facility view. The completeness of ECHO's state data depends on state reporting quality and timeliness: some states submit data reliably and on schedule; others have chronic reporting lags or data quality issues that create gaps in the ECHO record.

The practical consequence for researchers is that ECHO's apparent enforcement activity levels are partly a function of state reporting behavior, not purely a function of actual enforcement activity. A state that appears to have high SNC counts may simply be reporting its violations more completely to the federal system than a neighboring state with similar or greater enforcement activity. Conversely, a state with low SNC counts in ECHO may have poor reporting discipline rather than a genuinely clean compliance record. State-level comparisons of enforcement intensity derived from ECHO data should be validated against direct contact with state agency enforcement databases where possible, and should account for known reporting quality differences among states.

EPA retains oversight authority over delegated state programs and can conduct its own inspections and enforcement actions in delegated states when EPA concludes that the state has failed to act on a significant violation. These federal overfiling actions are identifiable in ECHO by the enforcing agency field: records showing EPA as the enforcing agency for a facility in a state with a delegated program represent cases where EPA determined state enforcement was inadequate. The frequency of federal overfiling by state is a direct measure of EPA's assessment of state program performance.

Cross-references: TRI, RMP, and press releases

ECHO produces its strongest research results when joined to three adjacent EPA datasets that provide complementary views of the same regulated facility population.

The Toxic Release Inventory (TRI) collects facility-level data on annual releases of listed toxic chemicals to air, water, and land from manufacturing facilities that exceed reporting thresholds. TRI data is self-reported by facilities and covers approximately 22,000 facilities annually. Joining TRI annual release volumes to ECHO enforcement history by facility identifier produces a combined dataset that shows both what a facility discharges (from TRI) and whether that discharge produces enforcement consequences (from ECHO). Facilities with high TRI release volumes and minimal ECHO enforcement history represent a specific population worth investigating: they are emitting at volumes that triggered TRI reporting obligations but may not be facing enforcement proportionate to their release burden.

The Risk Management Plan (RMP) database covers chemical facilities that hold quantities of listed acutely hazardous chemicals above threshold levels under Clean Air Act Section 112(r). RMP facilities must submit plans describing their worst-case release scenarios, alternative release scenarios, and accident prevention programs. The RMP database, available at rmp.epa.gov, identifies the highest-consequence facilities in the chemical regulatory universe—those where a single catastrophic failure could produce mass casualties or major community exposures. Joining RMP facility lists to ECHO enforcement history identifies RMP facilities with active SNC or HPV designations: chemical facilities with documented significant violations that also pose catastrophic accident risk. This is the most acute version of the enforcement gap question the ECHO database can answer.

EPA enforcement press releases, published through EPA's newsroom at epa.gov/newsreleases, provide narrative case detail that the structured ECHO database does not. A formal enforcement action that appears in ECHO as an administrative penalty order for $2.3 million against a refinery's CAA violations will have a corresponding press release that describes the specific excess emissions events, the duration of the violations, the regulatory standards violated, and the corrective actions required. For high-consequence cases, the press release is also the source for penalty component breakdowns—which portion is a cash penalty, which portion is directed to a supplemental environmental project, and whether any portion was suspended contingent on compliance. Cross-referencing the ECHO penalty record against the EPA press release archive for major cases is essential for correct interpretation of what the penalty figures actually represent.

Limitations

ECHO is the most comprehensive public record of federal environmental enforcement in the United States, but analysts need to understand four structural limitations before building conclusions on the data.

ECHO reflects enforcement history, not current emissions. A facility with no current ECHO violations has not been certified clean by any air or water monitoring system; it has simply not received a documented violation finding in its most recent compliance evaluation. Between evaluation cycles, facilities may be emitting in excess of their permit limits without that excess appearing anywhere in ECHO. The Continuous Emissions Monitoring System (CEMS) data that large CAA sources submit to EPA's Clean Air Markets Division provides near-real-time emissions data for power plants and certain industrial sources, but this data is separate from ECHO and is not integrated into ECHO's facility view. A complete picture of facility-level air emissions compliance requires combining ECHO enforcement history with CEMS data, and neither alone is sufficient.

Penalty paid vs. assessed gap varies by resolution type. The assessed penalty in ECHO represents the formal penalty amount. In cases resolved with Supplemental Environmental Projects, a facility funds an environmental project in the affected community and receives a penalty reduction equal to some fraction of the SEP cost. The resulting paid figure understates the actual financial burden on the facility (because the SEP expenditure is real) and overstates the cash deterrent effect (because the SEP does not flow to the government). Analysts using ECHO penalty data to assess deterrence should distinguish cash penalty amounts from SEP-reduced amounts, which requires reading the underlying consent agreement or enforcement order rather than relying on the ECHO penalty field alone.

State data completeness varies substantially. As described in the enforcement split section above, ECHO's completeness is a function of state reporting quality. States that report late, report inconsistently, or have not fully integrated their legacy enforcement databases into the federal reporting systems will appear in ECHO with gaps that do not reflect actual enforcement inactivity. This limitation is most acute for older records and for states with chronic data quality issues; it affects national-scale analyses less than state-level comparisons, because the gaps tend to be distributed unevenly across states rather than uniformly across the dataset.

A “No Violation” designation does not mean clean. It means the facility has no current documented violation in ECHO under the program in question. This is a critically different statement. Facilities that have not been inspected recently, facilities in states with low inspection coverage rates, and facilities in industries with infrequent programmed compliance evaluations may carry No Violation status in ECHO simply because no compliance evaluation has occurred recently enough to detect a current violation. The inspection frequency fields in ECHO—recording when the facility was last inspected under each program—are the appropriate companion to compliance status: a facility with No Violation status and an inspection date five years ago is analytically distinct from a facility with No Violation status and an inspection date six months ago.