BP takes Gulf oil spill heat, but what about other companies?

BP accepts responsibility for the massive Gulf oil spill, making it a lightning rod for public rebuke. But other companies, including Transocean and Halliburton, may be legally liable, too.

By , Correspondent

  • close
    Company executives Lamar McKay of BP America, Inc. (L), Steven Newman of Transocean Limited (C), and Tim Probert of Halliburton (R), are sworn in during the Senate Environment and Public Works Committee hearing on the Gulf of Mexico oil spill May 11.
    View Caption

In headlines and among the public, the environmental disaster in the Gulf of Mexico typically is referred to as “the BP oil spill.”

But, the oil giant will not be the only company facing legal battles, and it may not be the sole entity found responsible. So, why is BP taking all the heat for what has become the largest offshore oil spill in US history?

The company has claimed full responsibility for both the spill and for whatever is necessary to clean up the oil that continues to flow. And in doing so, the company has become a lightning rod for public rebuke and boycotts of its products worldwide.

Recommended: The 10 most expensive US natural disasters

IN PICTURES: The Gulf oil spill's impact on nature

“I think they had no choice because it was their well,” says Peter Henning, a former Justice Department prosecutor now at Wayne State University Law School. “One of the big oil companies always takes the heat.”

Though Mr. Henning said BP likely will be taking most of the blame, it was not the only company working on the Deepwater Horizon oil rig when it exploded on April 20, killed 11 crew members and flooding the Gulf with oil.

Among the other companies working on the rig at the time were rig owner Transocean Ltd. and sub-contractors Halliburton Co., Weatherford International Ltd., and M-I SWACO.

Justice Department criminal probe

US Attorney General Eric Holder announced last week that the Justice Department has opened a criminal investigation focusing on BP as well as on Transocean and on Halliburton, which was doing work to cement the well 20 hours prior to when the spill began.

There are sure to be private and government lawsuits against all companies involved as well, says Zygmunt Plater, a Boston College law professor who chaired the legal research task force for the Exxon Valdez oil spill of 1989, until now the largest offshore spill in US history.

The Oil Pollution Act (OPA) of 1990, which the Exxon Valdez task force helped shape, essentially focuses the responsibility on one party for the sake of simplicity, says Mr. Plater. In this case BP is that party. However BP can and almost certainly will sue for contributions from other companies that may have been at all responsible for the spill.

However, Henning pointed out in a recent New York Times column that Transocean has an indemnification provision that may leave BP responsible for paying the cost of cleanup and recovery no matter what. Halliburton said in a recent call to investors that like Transocean they are legally indemnified from responsibility through their contract with BP.

“It will be the contract law fight of all contract law fights,” Henning said.

While legal judgments are yet to be determined, says Plater, “My guess is there will be a lot of pointing of fingers.”

The blame game has already begun.

Officials from BP, Transocean, and Halliburton testified before Congress on May 11. Three days later, President Obama called those hearings a “ridiculous spectacle.”

“You had executives of BP and Transocean and Halliburton falling over each other to point the finger of blame at somebody else,” said Mr. Obama in a May 14 speech.

Henning and Plater each say they’re not surprised that the other companies are keeping a low profile for the time being, letting BP become the face of the Gulf spill.

'A gathering storm of litigation'

“Their first reaction, of course, is self defense,” Plater said. “I’m sure they’re delighted BP is in the crosshairs, but they also know there is a gathering storm of litigation on the way.”

Additionally, “they’re not going to be able to duck [public scrutiny],” he said. “It’s just postponed.… It will be a top story for months, if not longer.”

According to BP spokeswoman Heidi Feick, the question of other companies stepping forward has not been discussed at BP. Their focus is on ending the spill and cleaning it up, she said.

During its congressional testimony last month, Halliburton said it accepts no blame for the spill. That's Transocean's position as well, according to a spokesman.

Inevitably, Henning said “BP will happily name everyone who was involved,” but in the meantime, BP will likely continue to act as a magnet for the blame, because continuing to point fingers before the oil stops flowing and cleanup is further along would damage BP’s already-sullied image.

“The court of public opinion isn’t fair; the media is not fair,” he said, adding that BP was the most recognizable name and easiest to blame immediately after the disaster began. “But whether it’s fair or not, [BP] will have to live with it.”

The blame will be sorted out through litigation, Henning said, but it will be a drawn out process likely lasting a decade or more.


What BP needs to do to salvage its oil-drenched image

Gulf oil spill: Why is it so hard to stop?

IN PICTURES: The Gulf oil spill's impact on nature

Share this story:

We want to hear, did we miss an angle we should have covered? Should we come back to this topic? Or just give us a rating for this story. We want to hear from you.




eZ debug

Clear cache:

Quick settings:

Timing: Jul 09 2014 11:55:12
Script start
Timing: Jul 09 2014 11:55:12
Module start 'content'
Timing: Jul 09 2014 11:55:12
Module end 'content'
Timing: Jul 09 2014 11:55:12
Before parse_includes
Strict: PHP: E_STRICT Jul 09 2014 11:55:12
Non-static method MugoViewExtras::get_view_extras() should not be called statically, assuming $this from incompatible context in /var/www/www.csmonitor.com/extension/mugo_view_extras/autoloads/template_operators.php on line 37
Warning: eZTemplate:def @ extension/csm_base/design/csm_design/override/templates/extra/archive.tpl:21[1] Jul 09 2014 11:55:12
Variable 'view_extra_node' is already defined.
Timing: Jul 09 2014 11:55:12
After parse_includes
Timing: Jul 09 2014 11:55:12

Timing points:

CheckpointElapsedRel. ElapsedMemoryRel. Memory
Script start 0.0000 sec0.0172 sec 1,285.9922 KB1,162.1094 KB
Module start 'content' 0.0172 sec0.0046 sec 2,448.1016 KB723.8984 KB
Module end 'content' 0.0218 sec0.0630 sec 3,172.0000 KB2,994.5078 KB
Before parse_includes 0.0848 sec0.0456 sec 6,166.5078 KB393.0547 KB
After parse_includes 0.1304 sec0.0007 sec 6,559.5625 KB-175.7266 KB
End 0.1311 sec  6,383.8359 KB 
Total runtime:0.1398 sec
Peak memory usage:7,078.5234 KB

Time accumulators:

 Accumulator Elapsed Percent Count Average
Load cache0.0068 sec4.8021%310.0002 sec
Mysql Total
Mysqli_queries0.0455 sec31.9404%590.0008 sec
Looping result0.0032 sec2.2670%570.0001 sec
Template Total0.0566 sec 39.7% 7 0.0081 sec
Template load0.0044 sec3.1158%70.0006 sec
Template processing0.0543 sec38.1186%70.0078 sec
Cache load0.0023 sec1.6093%70.0003 sec
state_id_array0.0022 sec1.5198%50.0004 sec
state_identifier_array0.0038 sec2.6422%50.0008 sec
String conversion0.0000 sec0.0350%30.0000 sec
dbfile0.0005 sec0.3277%190.0000 sec
View Extra building0.0248 sec17.4413%20.0124 sec
Total script time:0.1425 sec

CSS/JS files loaded with "ezjscPacker" during request:


Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/csm_base/design/csm_design/templates/pagelayout.tplEdit templateOverride template
1modules/mugo_view_extras/extra_cached.tpl<No override>extension/mugo_view_extras/design/standard/templates/modules/mugo_view_extras/extra_cached.tplEdit templateOverride template
1setup/debug_toolbar.tpl<No override>design/standard/templates/setup/debug_toolbar.tplEdit templateOverride template
 Number of times templates used: 3
 Number of unique templates used: 3
 Time used to render template usage: 0.0002 secs