The Government Oil Spill: Coast Guard Liable for Sinking of Deepwater Horizon Rig, Ensuing Chaos
The generally accepted view of the Deepwater Horizon disaster has focused on the blowout preventer and the non-standard procedures BP conducted just before the explosion and fire. However, most of the damage and the main source of the spill came from the collapse and sinking of the DH platform rather than the initial explosion. A new report by the Center for Public Integrity, based on testimony from people on scene and Coast Guard logs, contains evidence that the platform sunk because of a botched response from the Coast Guard, which failed to coordinate firefighting efforts and to have the proper resources to fight the fire:
The Coast Guard is not supposed to participate in firefighting, but instead assign an expert to coordinate the private firefighting efforts of the rig operator and its contractors. The Coast Guard failed to do so, and the result was an uncoordinated, “general response” effort that mainly relied on salt water to extinguish the fires. That is not the most effective way to fight rig fires; the best way is to use foam, which apparently wasn’t on hand. An expert would have known this, but as CPI’s report of the testimony shows, none was assigned:
The crippling budget cuts President Obama proposed for the Coast Guard also deserve a closer examination. Obama's spending plan reduced the blue water fleet by a full one-third, slashed 1,000 personnel, five cutters, and several aircraft, including helicopters. According to the Center for Public Integrity, the Coast Guard updated its official maritime rescue manual -- advising against firefighting aboard a rig -- just seven months before the Deepwater Horizon explosion. That change in policy came at a time when Adm. Thad Allen warned the budget cuts threatened to turn the Coast Guard into a "hollow force."
This entry was posted on at 10:31 AM and is filed under BP, Gulf oil spill, military, the left. You can follow any responses to this entry through the RSS 2.0. You can