Gulf oil slick comes from device used in 2010 spill: Coast Guard

Gulf oil slick comes from device used in 2010 spill: Coast Guard

Gulf oil slick in the Gulf of Mexico, as seen on Sept. 21, 2012.

Gulf oil slick in the Gulf of Mexico, as seen on Sept. 21, 2012. (NOAA photo)

An undersea camera confirms that an oil slick discovered in the Gulf of Mexico came from a 100-ton device on the seafloor that BP had used several weeks after the 2010 oil spill in a failed attempt to cap its runaway Macondo well, the U.S. Coast Guard  said Thursday.

The oil  is not coming from the Macondo itself, which was sealed in a relief well operation months after the 2010 blowout.

Less than 100 gallons of oil per day is leaking from the containment device, the Coast Guard said. The oil will continue to dribble out slowly for the time being adding to the Gulf oil slick. Officials are trying to figure out the best course forward.

BP said the Coast Guard has determined the sheen is not feasible to recover and does not pose a risk to the shoreline, but the Coast Guard said it is still considering what should be done.

“The latest survey marks the third time since the Macondo well was permanently sealed in September 2010 that it has been visually inspected at the seafloor and confirmed not to be leaking,” BP said in a statement.

Transocean, which owned the Deepwater Horizon drilling rig that exploded after the Macondo blowout, declined to comment on the Coast Guard’s news release. Eleven workers died in the accident, and the government estimates that more than 200 million gallons of crude spewed from the well a mile below the surface of the water creating a massive Gulf oil slick.

According to the Coast Guard, remote operated vehicles deployed from the offshore construction vessel Skandi Neptune collected oil samples on Wednesday from the underwater site of the Deepwater Horizon incident to determine the source of the surface sheen….

Originally published on Fuelfix.com



Related Posts Plugin for WordPress, Blogger...

Leave a Reply

You must be logged in to post a comment