I didn’t make it very far into the report before the political tone became apparent.
In the second paragraph of the first section (the Forward), the report says:
“A treasured American landscape, already battered and degraded from years of mismanagement, faced yet another blow as the oil spread and washed ashore.”
These type of political statements and adjectives that can easily agitate public opinion are common throughout the first three chapters that I read this weekend. My opinion is that an accident report should stand on the facts. Perhaps Chapter 4 will present them – I’m still reading.
However, the Editors of The Wall Street Journal were not convinced. In an article in the “Review & Outlook” of the editorial page titled: “Gulf Political Spill”, they said:
“Unable to name what difinitively caused the well failure, the commission resorts to a hodgepodge of speculation.”
It also says:
“Its [the report’s] section ‘The Root Causes: Failures in Industry and Government’ uses questionable decisions made by the Macondo players to suggest, with no evidence, that such behavior is the industry norm.”
Toward the end of the editorial, it says:
“The unbalanced, tendentious nature of the commission report vindicates those who suspected from the start that this was all a political exercise.”
They conclude the WSJ editorial with:
“The BP spill was a tragedy that should be diagnosed with a goal of preventing a repeat, not in order to all but shut down an industry that is vital to U.S. energy supplies and the livelihood of millions on the Gulf Coast.”
What I’d suggest is that you read the 398 page report for yourself and leave your comments here based on your own observations. Let me know what you think.
To download the report, go to:
Here are the important links to download the report …
First, download the report at:
But the report cites another report still to be written – The Chief Counsel’s Report. The final report references this report for more about the facts of the investigation. There is a place to request notification when the Chief Counsel’s Report is completed on the full report download page.
Sometimes people ask me what the most popular problem solving system (besides TapRooT®) is. That easy! Blame.
Here’s a self-executing PowerPoint to help you understand the concept …
Is this the way your employees view your root cause analysis?
Environmental Groups Blast Louisiana Refineries for “Accidents” Reported to the LA Dept of Environmental QualityDecember 14th, 2010 by Mark Paradies
Here’s the story from the New Orleans Times-Picayune:
While the groups complain about under-reporting, they then turn around to say that the numbers reported show that a BP Texas City type accident could threaten workers and local residents.
What do you think? A fair use of data or a political hit job?
Staff of the National Commission on the BP Deepwater Horizon Oil Spill & Offshore Drilling Issues Interesting Preliminary ReportsDecember 9th, 2010 by Mark Paradies
Here are links to the various reports:
I post several Holiday Safety PowerPoints that were given to me by TapRooT® Users. They are yours for toolbox holiday safety meetings.
Here is the first:
Monday Accident & Lessons Learned: Technical Investigation Report concerning the Fire on Eurotunnel Freight Shuttle 7412 on 11 September 2008November 22nd, 2010 by Mark Paradies
See the joint report by the French Bureau d’enquêtes sur les Accidents de transport terrestre and the UK Rail Accident Investigation Branch at:
The Summit starts next Wednesday, but I’ll be posting some of the talks so that people attending the Sumnmit can print them to take notes and preview what they will hear.
Caution: A PowerPoint of a talk isn’t the same as a talk. I know in my talks, there are things that are said that make the slides “come alive.” Also, some of the bullets on the slides are “for discussion.” They aren’t meant as a final conclusion, but rather as a starting point. Therefore, these talks should be observed and participated in at the Summit rather than being read as a final statement.
here is the Summit intro talk that will be delivered by Mark Paradies, Linda Unger, Ed Skompski, Ken Reed, Chris Vallee, and David Janney.
5-Day TapRooT® Advanced Root Cause Analysis Course in Macaé, Brazil, on November 8-12, In PortugueseOctober 6th, 2010 by Mark Paradies
UK Rail Accident Investigation Branch Publishes a Report on the Derailment at Dingwall, Scotland, 22 January 2010September 30th, 2010 by Mark Paradies
Safety & Health Practitioner (the official magazine of the Institute of Occupational Safety & Health) published an article titled: “Blame culture prominent on Transocean rigs“.
The first paragraph said:
“A culture of fear and blame is rife across the operations of offshore drilling contractor Transocean, according to a leaked HSE inspection report.”
Wow! That’s certainly an “explosive” claim. Especially with the weight of the UK Health and Safety Executive behind it.
For the complete story, see:
Teaching root cause analysis, I have lots of people ask me about 12 hours shifts, fatigue, and safety. If this is a question you are interested in, I have a free publication that might interest you …
It is written by the experts in fatigue and shift scheduling, Circadian Technologies. Get your copy at:
The American Petroleum Institute and the American National Standards Institute have published a recommended practice titled: Fatigue Risk Management Systems for Personnel in the Refining and Petrochemical Industries (ANSI/API Recommended Practice 775, First Edition, April 2010).
You can download the standard at this site:
Now, what do incident investigators need to know about this standard when performing a root cause analysis? If you are at a refinery or petrochemical plant, you are required to consider fatigue when doing your investigation. The standard says:
4.7 Incident/Near Miss Investigation
The investigation of incidents should be conducted in a manner that facilitates the determination of the role, if any, of fatigue as a root cause or contributing cause to the incident. Information collected should include the time of the incident, the shift pattern, including the number of consecutive shifts worked, the number of hours awake, the number of hours of sleep in the past 24 hours by the individuals involved; the shift duration (and any overtime worked); whether the incident occured under normal operations or an extended shift; whether an outage was occurring; and, other fatigue factors. It should be noted that for individual incidents, often no definitive conclusion regarding the role of fatigue may be possible. However, aggregate analysis of incidents may reveal patterns suggestive of the role of fatigue that is not apparent by evaluating incidents individually.
When using TapRooT®, fatigue has always been considered as part of the “15 Questions” asked for every Human Performance Difficulty. The first question asks:
“Was the person excessively fatigues, impaired, upset, distracted, or overwhelmed?”
This question is expanded on in the Root Cause Tree® Dictionary. These questions were developed with the help of Circadian Technologies. We also worked with them to develop a free internet based fatigue evaluation tool called FACTS (Fatigue Accident/Incident Causation Testing System). You can try it for free at:
Want to find out more about fatigue and FACTS? The attend the TapRooT® Summit. Rainer Gutkuhn (one of the designers of FACTS) will show attendees in the Behavior Change & Stopping Human Error Track how to use FACTS in an investigation.
That’s just one of the many great sessions at the Summit. See:
for the complete Summit Schedule.
Here’s an old document (1979 – in pdf format) where Admiral Rickover set out his tenets that assured reactor safety in the Nuclear Navy.
Click link below…
We will be discussing his philosophy at the TapRooT® Summit in the “Lessons Learned About Excellence and Safety From Admiral Rickover” session in the Improvement Program Best Practices Track on Thursday from 10:40-12.
Don’t miss this session where where you can learn how Process Safety Management and Operational Excellence originated.
To register for the Summit, go to:
And if your were a Navy Nuc … leave your comments here about your experience in the Nuclear navy and how it changed your approach to operations, maintenance, or life.
The Nuclear Regulatory Commission has developed 13 safety culture components that were updated and released earlier this year. They are:
- Work Control
- Work Practices
- Corrective action program
- Operating experience
- Self and independent assessments
- Environment for raising safety concerns
- Preventing, detecting, and mitigating perceptions of retaliation
- Continuous learning environment
- Organizational change management
- Safety policies
To read more about these safety culture components, see this NRC document:
Rafael Moure-Eraso, Chairman of the Chemical Safety Board, sent the letter below to Xcel Energy Inc., a utility with its headquarters in Minnesota. I’ve never seen a letter written so strongly from an investigator about the lack of cooperation about an investigation. Have you?
It would certainly be interesting to know more about what happened to cause the lack of cooperation.
Here’s link to the letter:
Here’s a pdf of the letter:
Monday Accident & Lessons Learned: UK Rail Accident Investigation Branch Publishes Bulletin About a Train Collision with a Level Crossing GateJuly 26th, 2010 by Mark Paradies
The UK RAIB’s report had three “Learning Points”:
1. Repeated occurrences of the same or closely related faults are likely to be a symptom of an underlying problem. Systems should be in place to identify repeated faults and to implement effective remedial action.
2. Maintenance requirements, particularly those applying to equipment connected with safety (such as the maintenance of gate stops (paragraph 13)), should not be left to local interpretation but should be determined by a competent person and recorded in a maintenance document.
3. It is important that signallers and crossing keepers at crossings of this type are given an unobstructed view of the gates, where it is practicable to do so.
To read the whole article, see: