SB 1039 creates two parallel monitoring obligations tied to petroleum refineries: a district‑led “refinery‑related community air monitoring system” sited near sensitive receptor locations, and fence‑line monitoring installed by refinery owners or operators. The bill directs that monitoring follow EPA siting guidance, capture refinery‑relevant compounds, maintain records, and make data publicly accessible "to the extent feasible." Costs fall primarily on refinery owners, with a limited cost‑sharing exception where districts repurpose community monitors for other regulated sources.
Why it matters: the measure shifts how localized refinery emissions are observed and reported, enabling more granular exposure estimates and community‑level surveillance. That creates new compliance, technical, and financial obligations for operators and places implementation responsibilities on local air districts, with unresolved questions about monitoring design, data quality, and cost allocation.
At a Glance
What It Does
The bill requires air districts to design and operate neighborhood monitors near refineries and requires refinery owners to install fence‑line monitors adjacent to their sites, with both systems collecting continuous measurements of refinery‑relevant pollutants. It ties siting to EPA guidance, lets districts specify which compounds to measure, and mandates recordkeeping and prompt public access to real‑time data where feasible.
Who It Affects
Primary actors are California local air districts and the owners/operators of petroleum refineries; secondary actors include community groups at identified sensitive receptor locations, third‑party contractors that districts may hire, and public health researchers who use ambient monitoring data.
Why It Matters
This bill institutionalizes localized monitoring that can detect fugitive releases and neighborhood exposures rather than relying solely on regulatory stacks or regional networks. That creates a new evidentiary stream for exposure assessment, community alerts, enforcement, and planning—and shifts most implementation costs onto refinery operators while imposing operational and data‑management duties on districts.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 1039 defines two types of monitoring around petroleum refineries. A refinery‑related community air monitoring system is intended for ambient measurements near sensitive receptors—places where people live, work, study, or otherwise are exposed.
A fence‑line monitoring system is intended to sit at or next to a refinery’s property boundary to detect fugitive emissions, leaks, and other plant‑adjacent releases. The bill requires both systems to measure pollutants the district identifies as emitted by refinery processes, and it specifically links siting practices to EPA guidance to promote consistent placement near sources and receptors.
Operational responsibility is split: the local air district must design, install, operate, and maintain the community monitoring network (and may contract with third parties to do so), while the refinery owner or operator must develop, install, operate, and maintain fence‑line monitors per district guidance. The text permits districts to decide which specific compounds to track and contains an explicit carve‑out preventing districts from requiring monitoring of substances that the facility cannot generate.Both systems must generate real‑time data and preserve records.
The bill uses the phrase "to the extent feasible" when it comes to making data publicly available as quickly as possible in an accessible format, which gives districts some discretion on publication timelines and formats. Guidance development must consider technological capability and affected‑party input and should be informed by existing refinery monitoring plans referenced elsewhere in statute.
Finally, the bill places implementation costs squarely on refinery owners, except when a district intentionally uses a community system to monitor other regulated sources, in which case the district must arrange a reasonably equitable cost sharing arrangement.Taken together, the measure aims to increase transparency about neighborhood‑level pollutant trends and provide data useful for exposure estimation and regulatory follow‑up. The statute leaves several operational details to district guidance—what exact sensors, QA/QC and calibration regimes, data platforms, and enforcement responses will look like in practice—and creates potential for variability across districts in both technical standards and timelines.
The Five Things You Need to Know
The bill defines two monitor types: a district‑operated refinery‑related community air monitoring system sited near sensitive receptors and an operator‑installed fence‑line monitoring system at or adjacent to refinery property.
It requires monitoring equipment to measure compounds the district determines are emitted by refinery processes and to follow EPA siting guidance applicable to air quality monitors.
Districts must operate and maintain community monitors (they may hire third parties) while refinery owners must develop, install, operate, and maintain fence‑line systems under district guidance.
Both systems must collect continuous, real‑time data and keep records; the law directs that data be provided to the public as quickly as feasible and in a publicly accessible format.
Costs are primarily the responsibility of refinery owners or operators, except where a community monitor is used intentionally by a district to monitor other regulated sources—then costs must be shared reasonably.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions: community and fence‑line monitoring
This subsection sets the statutory definitions that drive who and where monitoring occurs. The community system is defined by location (near sensitive receptors) and purpose (estimating exposures and trends); the fence‑line system is defined by proximity to the facility and its utility for detecting fugitive emissions. These definitions matter because they constrain siting choices and the intended analytical uses for the data—exposure estimation versus emissions detection—which in turn affects sensor selection, placement, and data interpretation.
District responsibility for community monitoring and technical standards
This provision obligates local air districts to design, install, operate, and maintain the neighborhood monitoring networks and requires alignment with federal EPA siting guidance. Practically, that gives districts authority to set pollutant lists, instrument classes, and placement criteria, and allows them to contract implementation to third parties. Because districts control technical specs, expect variation across jurisdictions in sensor types, QA/QC, and reporting cadence unless state guidance standardizes those elements.
Refinery operator responsibility for fence‑line monitoring
Operators must develop and operate fence‑line monitoring per district guidance. The text explicitly prevents districts from requiring monitoring of substances a facility cannot produce, which narrows exposure to plausible compounds but leaves districts discretion to require detection of a broad set of refinery‑relevant constituents. For operators this creates a compliance program requirement—procurement, installation, maintenance, and data transmission systems must be budgeted and managed.
Data collection, recordkeeping, and public access
Both districts and operators must collect continuous, real‑time data and maintain records. The statute instructs that, to the extent feasible, data should be made public quickly in an accessible format. That language grants flexibility but also signals an expectation of near‑real‑time transparency; districts will need data management platforms, publication interfaces, and policies on raw versus validated data, including how to annotate or correct transient spikes to prevent misinterpretation by the public or regulators.
Guidance development and stakeholder input
District guidance must account for technological capabilities and incorporate input from affected parties, and should be informed by monitoring plans referenced elsewhere in statute. This creates a procedural requirement for stakeholder engagement and technical feasibility analysis; however, it does not prescribe specific timelines or minimum consultation standards, leaving the depth and timing of stakeholder engagement to district processes.
Cost allocation and the shared‑use exception
The bill assigns primary financial responsibility to refinery owners and operators for implementing both monitoring regimes. The only exception is when a district intentionally uses a community monitor to surveil other regulated sources—then the district must arrange reasonable cost sharing. The statute’s "reasonably equitable" standard is deliberately vague, so cost negotiations and disputes are likely to arise and may require interagency guidance or litigation to resolve fairness questions.
This bill is one of many.
Codify tracks hundreds of bills on Environment across all five countries.
Explore Environment in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Residents near refineries and other sensitive receptor groups (schools, nursing homes): they gain localized, higher‑resolution air quality data that supports exposure assessment, community alerts, and health investigations.
- Local public health agencies and community health researchers: receive ambient data that can be integrated with health surveillance to identify short‑term exposure events and longer‑term trends.
- Environmental justice and community advocacy groups: increased transparency and access to near‑real‑time data strengthen community monitoring, public communications, and evidence for requests to regulators.
- Air districts (programmatically): gain targeted data to prioritize inspections, identify fugitive emission sources, and calibrate permitting and enforcement strategies—if they secure resources to manage the systems.
- Independent monitoring vendors and environmental consultants: increased market demand for sensor systems, data platforms, QA/QC services, and technical support.
Who Bears the Cost
- Refinery owners and operators: must fund development, installation, operation, and maintenance of fence‑line monitors and likely absorb costs for data systems, calibrations, and reporting.
- Local air districts: responsible for community monitors and guidance development; districts may face unfunded programmatic burdens, especially smaller districts with limited technical staff.
- Compliance, legal, and insurance teams at refiners: will incur costs assessing legal exposure to monitoring data, responding to incidents revealed by public monitors, and updating permits or operational controls.
- Third‑party contractors and vendors: while they gain business, they bear upfront capital and operational costs to supply, install, and service equipment before recouping fees under contracts.
- Potentially ratepayers or municipal budgets: if districts lack full funding, costs may shift to local budgets or require fee adjustments, creating indirect public costs.
Key Issues
The Core Tension
The bill pits two legitimate goals against each other: communities’ need for transparent, timely, neighborhood‑level air quality data to assess exposures versus operators’ and districts’ need for practicable, reliable monitoring systems and predictable cost allocation; achieving both fully requires detailed technical and funding decisions the statute leaves unresolved.
The statute leaves significant implementation details to local districts, which risks a patchwork of technical standards. Sensor selection, calibration protocols, detection limits, QA/QC, data validation, and event flagging are not specified; without state‑level minimums, comparability across refineries and districts will be limited.
That complicates statewide exposure assessments and could make cross‑site enforcement inconsistent.
The language around data publication—"to the extent feasible" and "as quickly as possible"—creates practical ambiguity. Districts must balance speed with data quality: publishing raw, unvalidated measurements can prompt community alarm and litigation, while delaying releases reduces transparency.
The cost allocation clause assigns primary responsibility to refinery owners but offers only a vague "reasonably equitable" approach when a community monitor is used for other sources, leaving room for dispute. Finally, the bill does not detail how to protect proprietary business information or confidential monitoring data, nor does it spell out how monitoring results translate into regulatory actions or mandatory mitigation, which will affect how stakeholders interpret and act on the data.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.