Compliance · US EPA

EPA Petroleum Refinery Sector Rule: fenceline benzene (40 CFR 63.658)

Ambient air: petroleum refinery fenceline (USA)

The EPA's Petroleum Refinery Sector Rule, finalized in 2015 as amendments to 40 CFR Part 63 Subpart CC, requires every petroleum refinery to monitor benzene at its fenceline under §63.658. Passive samplers around the property boundary collect benzene over contiguous 14-day periods, and for each period the facility calculates Δc, the highest minus the lowest fenceline concentration. When the annual average Δc, over the 26 most recent periods, exceeds 9 µg/m³, the refinery must carry out a root cause analysis and corrective action.

Schedule a callConfigure Refinery Sector Rule Monitoring

The standard

What the Refinery Sector Rule Requires

The rule is a transparency and correction mechanism rather than an ambient limit: it targets the refinery's own contribution, measured as the difference across its fenceline, and it has made refinery fenceline data public, reported to the EPA quarterly since 2019.

Limit values

Refinery Sector Rule Limit Values

Every value US EPA publishes for the parameter below, with its averaging period, as the standard states it.

BTEX / speciated VOC Gases & VOCs
9 µg/m³ Annual average Δc, fencelinebenzene; Δc is the highest minus the lowest 14-day fenceline sample, averaged over 26 periods; above it, root cause analysis and corrective action

Who it applies to

Who It Applies to

Petroleum refineries subject to 40 CFR Part 63 Subpart CC across the United States. The number of samplers and their spacing follow EPA Method 325A, and the samples are analyzed under Method 325B. A refinery may use an approved alternative method, such as open-path monitoring, if it gives equal or better spatial coverage, and may use a site-specific monitoring plan to correct for near-field sources that are not its own.

Monitoring

How Monitoring Demonstrates Compliance

Compliance rests on the passive sampler record: the 14-day samples, laboratory results, Δc for each period, and the rolling annual average against 9 µg/m³. Continuous monitoring does not replace that record, but it answers the questions the record raises: when concentrations rose, from which direction, and during which operations. That is the information a root cause analysis needs. Wind data belongs with every reading.

Recommended

best match
1 of 1 covered · 1 gateway · 1 instrument
  1. Thiamis connects 1 instrument

    A gateway that connects the third-party instruments you choose to the Aethair Platform.

Customize this configuration

Who measures each parameter

Parameter Aethair PRO Aethair IAQ External
BTEX / speciated VOC——1 instrument via Thiamis

Devices

Devices That Cover Refinery Sector Rule

How much of this standard one Aethair monitor covers, followed by the third-party instruments in the sensor catalog that measure its parameters. Each connects to Environet through a Thiamis gateway, which adds whatever the monitor leaves out.

Covers it on its own

Solutions

Solutions Judged Against Refinery Sector Rule

All solutions

Article Library

Articles on Refinery Sector Rule

All articles

Questions

Refinery Sector Rule FAQ

What is the refinery fenceline benzene action level?

9 µg/m³, compared against the annual average of Δc (the highest minus the lowest fenceline sample in each 14-day period) over the 26 most recent periods. Above it, the refinery must investigate the root cause and take corrective action.

How is refinery fenceline benzene sampled?

With passive diffusive sorbent tubes deployed around the property boundary under EPA Method 325A, exposed for 14 days and analyzed in a laboratory under Method 325B.

Can continuous monitors be used under the refinery rule?

An approved alternative method, such as open-path monitoring, can replace samplers if it gives equal or better spatial coverage. Otherwise continuous monitoring supports the program (showing when and from where concentrations rose) rather than replacing the passive samplers.

Monitor Against Refinery Sector Rule

Schedule a callBuild a Configuration All standards

A 30-minute call: you tell us about your application, then we demo the solution for it.