The 2012 Chevron Richmond Refinery Fire
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.
- When
- 6 August 2012Exact day
- Where
- No. 4 Crude Unit, Chevron Richmond RefineryUnited States · General area
- Evidence
- VerifiedSources reviewed below
- Sensitivity
- Includes loss or traumaPresented with care
The place
Before
What existed before
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.
Cause
Trigger and conditions
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.
Sequence
Timeline
Small leak detected in crude unit
Workers investigate leaking 4-sidecut piping while the process remains operating.
Corroded pipe ruptures and vapor ignites
A hydrocarbon cloud engulfs nearby workers before they escape and a major fire begins.
CSB releases interim findings
Investigators identify sulfidation corrosion and missed opportunities for inherently safer replacement.
Final investigation approved
The CSB adopts its final report and safety recommendations after three linked reports.
After
Aftermath
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 consequences
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.
Significance
The essential question
Why this still matters
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 today
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.
Evidence
Sources
Sources support specific claims; inclusion does not imply that every source is equally authoritative on every question.
- 01Chevron Richmond Refinery Fire
U.S. Chemical Safety and Hazard Investigation Board
Primary federal investigation hub for the rupture, fire, metallurgy, process-safety findings, and recommendations.Open source - 02Chevron Settlement Information Sheet
U.S. Environmental Protection Agency
Federal enforcement history connecting the Richmond fire to shelter-in-place, medical demand, and nationwide process-safety improvements.Open source - 03CSB Board Approves Chevron Refinery Final Report
U.S. Chemical Safety and Hazard Investigation Board
Final Board findings on worker danger, community medical visits, safety culture, and emergency response.Open source
Community
Discuss this Chaos File
Start a focused topic or join an existing conversation about evidence, context, the location, or what this record leaves unresolved.
Be the first person to give this file a conversation of its own.
The record keeps moving
Continue tracing
Move into a connected subject, place, or turning point. You choose the thread.