Learning from major accidents
Study CSB and HSE investigations to see which controls failed and why, then turn one case into a one-page lessons brief for a site, with an owner and a date.
- Optional
- Intermediate
- about 10 hours
Written by the GreenHired editorial teamSources last checked 20 November 2026How we research roadmaps
Reading a case for drama leaves you with an anecdote. Reading for failed controls leaves you with a check you can run on your own site on Monday. Go through a case in three passes: the summary and recommendations first, then the cause sections that match hazards you actually have, and the timeline last, to see how the pieces fit.
From a bypassed alarm to a Monday check
A report, not a real case, describes a storage tank that overfilled because a high-level alarm was bypassed during a maintenance job and never restored. The brief a site manager will read opens with what happened: a tank overfilled during a transfer, and its high-level alarm had been bypassed for a repair and nobody put it back.
It then names three system causes: the bypass had no named owner and no end time, the change was never reviewed, and the next shift’s handover did not mention it. It asks for one check this month: every area manager lists the alarms and trips bypassed on their unit today, who authorised each and when it ends. And it closes with an owner and a date: the operations manager, with the list returned to the EHS officer by an agreed date.
The brief says nothing about the footage or the damage. It names causes in words an operator would use and ends with a job someone can do this week. Writing your own why-chains is covered in incident investigation and root cause analysis.
Before you call it a pattern
Pick three reports and ask each the same questions: was a change managed (management of change covers the first), were safety-critical systems tested, did anyone act on a warning? Answer every cell with found, not found or the report is silent. Silent is not the same as no, so write it down as such. If two cases show a maintenance gap and the third is silent, the honest line is “two of three, one unknown”. A video title can suggest which report to open, but only the report holds the evidence.
Match the case to your own hazards
Choose by what your site handles. A woodworking shop gets more from a dust explosion report than from a refinery story. A site with bulk fuel storage should start with Buncefield, then search the CSB investigations list for storage-tank cases. Pair the reading with process safety and major-hazard regimes. This topic is optional, and it matters most if your site stores or processes hazardous substances in bulk. Check each report itself before you quote it, because summaries elsewhere can be wrong.
What you will learn
- How an independent investigation body structures a case: facts, timeline, causes, recommendations.
- How to read a long investigation report efficiently and pull out the controls that failed.
- What the Buncefield case shows about tank overfill, regulation and leadership.
- Which themes recur across cases, and the care needed before generalising from video titles.
- How to write a one-page lessons brief a site manager will read.
The parts of this topic
Using the CSB video libraryabout 2 hours
Watch short investigation videos and note the sequence of events, the barriers that failed and the root causes named.
The CSB describes itself as an independent, non-regulatory agency that investigates chemical accidents, conducts root cause investigations and makes recommendations rather than issuing fines. Its video room lists dozens of case videos, including BP-Husky, Didion Milling, Optima Belle, LyondellBasell and the TPC Group. Example: watch one video, pause after the incident and write down what you think the root causes were before the video names them, because passive watching leaves you remembering the dramatic footage and little else.
- About the CSB US Chemical Safety Board · Guide
Reading an investigation report efficientlyabout 2 hours
Read the executive summary, timeline and recommendations first, then dig into the causes that match your own site.
A long report has a common shape: a summary, the facts and timeline, an analysis of causes, and recommendations. Read the summary and recommendations first, then the sections on causes that match your own hazards. For a dust explosion report, read the housekeeping, ventilation and ignition source sections, then check your own dust-producing processes. OpenLearn's integrated management course also treats incident analysis, causes and multiple contributing causes. Read for the control failures, not for the story.
- Integrated safety, health and environmental management: an introduction The Open University (OpenLearn) · Course About 15 hours, level 3, free statement of participation.
Case: Buncefield, 2005about 2 hours
A UK fuel storage depot explosion and fire, investigated by HSE and the Environment Agency, with leadership and tank-overfill lessons.
HSE records that explosions at the Buncefield Oil Storage Depot in Hemel Hempstead on 11 December 2005 injured over 40 people, caused a large fire for several days and widespread damage, but no fatalities. HSE and the Environment Agency investigated and secured convictions against five companies, with almost 10 million pounds in combined fines and costs. HSE's page links the Process Safety Leadership Group report and related research. Read it for the leadership and regulation lessons as well as the tank overfill.
- Buncefield: response to the incident HSE (United Kingdom) · Guide
Recurring themes: change, maintenance and cultureabout 2 hours
Look for repeating patterns across cases, and check each report before you claim a pattern.
Across process safety investigations, common questions recur: was a change managed, were safety-critical systems maintained and tested, did warnings get acted on, did leaders know what was happening? Video titles such as 'Ignored Warnings', 'Outsourcing Responsibility' and 'Transient Hazards' hint at themes, but a title is not evidence. A useful test is to compare three reports and tabulate whether each had a change, a maintenance gap and a culture issue, taking the theme from what the investigators found, not from a favourite explanation.
- Organisational culture HSE (United Kingdom) · Guide
Writing a one-page lessons briefabout 2 hours
Turn a long case into a one-page brief with what happened, why, and what to check on your own site.
A lessons brief is not a summary of the report. It says what happened in two sentences, names three system causes in plain language, lists what to check on your own site this month and gives one owner and one date. After a case about a bypassed alarm, the brief asks each area manager to list the alarms currently bypassed on their unit. OSHA's case-study page lists employer examples of lessons learned and best practice for safety programmes. An accurate brief that gives no one a job to do changes nothing.
- OSHA safety management case studies OSHA (United States) · Guide
Practice task
Choose one CSB investigation or the Buncefield case. Write a one-page lessons brief for a site similar to the one in the case: what happened, three system-level causes, what to check on your own site this month, and one action with an owner.
Skills you build
Case study analysisLessons-learned writingProcess safety awarenessReport readingBriefing managers
Resources for this topic
Every source here is free. Each link opens the provider's own site in a new tab.
- CSB safety videos US Chemical Safety Board · Video Public videos on the CSB site covering incidents such as BP-Husky, Didion Milling and LyondellBasell.
- CSB investigations US Chemical Safety Board · Guide Searchable list of current and completed investigations.
- CSB recommendations US Chemical Safety Board · Dataset
- Control of Major Accident Hazards (COMAH) HSE (United Kingdom) · Guide
- Developing process safety indicators (HSG254) HSE (United Kingdom) · Guide
Live Environmental, health and safety (EHS) officer jobs
Roles whose title matches this career path.
Spot a problem with this topic?
Tell us what is wrong, missing or unclear here. Your note is attached to this topic.
Notes are sent from this page with JavaScript on. Without it, write to us on the contact page.