← Revision history

Immutable archive snapshot

Edition 1

The 2012 Chevron Richmond Refinery Fire · 21 July 2026

Field-by-field comparison

Initial edition

TitleChanged
Before publication

Not present

Edition 1

The 2012 Chevron Richmond Refinery Fire

Quick readChanged
Before publication

Not present

Edition 1

On 6 August 2012, severely corroded piping ruptured in the No. 4 Crude Unit at Chevron's Richmond refinery. Hot hydrocarbon liquid formed a large flammable vapor cloud that ignited while workers were nearby. Nineteen employees were endangered, surrounding communities sheltered in place, and about 15,000 residents sought medical attention. Federal inquiries found repeated missed opportunities to replace vulnerable pipe and deeper process-safety and regulatory failures.

DateChanged
Before publication

Not present

Edition 1

6 August 2012

LocationChanged
Before publication

Not present

Edition 1

No. 4 Crude Unit, Chevron Richmond Refinery

BeforeChanged
Before publication

Not present

Edition 1

The refinery knew that sulfidation corrosion could thin carbon-steel pipe and had inspected the crude unit over many years. The failed component contained unusually low silicon, making it more susceptible, yet inspection strategies and industry guidance did not reliably find the most vulnerable individual components.

Trigger and conditionsChanged
Before publication

Not present

Edition 1

Workers observed a small leak from the 4-sidecut line while the unit remained in operation. As they approached and attempted to assess it, the thinned pipe ruptured catastrophically. High-temperature gas oil partially vaporized, created an expanding cloud, and ignited. The workers escaped through the cloud without fatalities.

AftermathChanged
Before publication

Not present

Edition 1

A major fire burned within the refinery and smoke crossed neighboring Richmond and San Pablo communities. Contra Costa County issued a shelter-in-place warning. The Chemical Safety Board conducted a multi-part investigation addressing metallurgy, corporate safety culture, emergency response, industry standards, and California's regulatory system.

Long-term consequencesChanged
Before publication

Not present

Edition 1

The incident drove stronger California refinery process-safety rules, local settlements, inspection and pipe-replacement requirements, worker participation, and federal enforcement. The EPA later required safeguards across Chevron's U.S. refineries, building on changes first applied at Richmond.

Why it mattersChanged
Before publication

Not present

Edition 1

Corrosion is ordinary and predictable; catastrophe followed because knowledge about it did not produce timely replacement of the most vulnerable pipe. The fire also shows that refinery risk crosses the fence line through smoke, medical demand, warnings, and community trust.

What remains todayChanged
Before publication

Not present

Edition 1

The Richmond refinery continues to operate beside communities with a long history of industrial exposure and environmental-justice organizing. CSB reports, regulatory changes, community air monitoring, and visible refinery infrastructure preserve the incident's ongoing relevance.

UncertaintyChanged
Before publication

Not present

Edition 1

The widely cited 15,000 figure counts people who sought medical attention, not 15,000 confirmed injuries caused by toxic exposure. This file keeps that distinction. The marker is intentionally area-level because the failed pipe lies inside an active restricted refinery.

Editorial creditChanged
Before publication

Not present

Edition 1

Chaos Tourist editorial

SourcesChanged
Before publication

Not present

Edition 1

Chevron Richmond Refinery Fire
Chevron Settlement Information Sheet
CSB Board Approves Chevron Refinery Final Report

Claim citationsChanged
Before publication

Not present

Edition 1

Not present