Efforts to stem the Deepwater Horizon oil spill
This article is part of a series about the Deepwater Horizon oil spill |
||
---|---|---|
Efforts to stem the Deepwater Horizon oil spill were ongoing from the time that the Deepwater Horizon exploded on April 20, 2010 until the well was sealed by a cap on July 15, 2010.[1] Various species of dolphins and other mammals (61 casualties), birds (2,095 casualties), and the endangered sea turtles (467 casualties) have been killed either directly or indirectly by the oil spill.[2] The Deepwater Horizon spill has surpassed in volume the 1989 Exxon Valdez oil spill as the largest ever to originate in U.S.-controlled waters; it is comparable to the 1979 Ixtoc I oil spill in total volume released (Ixtoc discharged 140 million US gallons (530,000 m3) to 148 million US gallons (560,000 m3); as of mid-July 2010, Deepwater Horizon has spilled 90 million US gallons (340,000 m3) to 180 million US gallons (680,000 m3)).[3][4]
Much of the oil is so far down in the Gulf that only nature, including microbes, will be able to remove it using a process called bioremediation.[5] Terry Hazen of the Department of Energy's Lawrence Berkeley National Laboratory said the process could take months or years.[5] But after six weeks of research, he said that microbes could work quickly in 84 °F (29 °C) water as opposed to colder-temperature waters. The A Whale, which is an oil tanker converted into a giant oil skimmer owned by the Taiwan Marine Transport Co (TMT), could do little because of BP's use of chemical dispersants, the company said.[6] Robert Bea of The University of California, who worked on the Ixtoc spill and the 1969 Santa Barbara oil spill, said the old methods would be the best ones. Dispersants, he said, did not work except in keeping beaches clean, and they hurt the environment.[5]
Contents
Non-explosive closure attempts
Short Term Efforts
The first attempts to stop the oil spill were to use remotely operated underwater vehicles to close the blowout preventer valves on the well head; however, all these attempts failed.[7][8] The second technique, placing a 125-tonne (276,000 lb) containment dome (which had worked on leaks in shallower water) over the largest leak and piping the oil to a storage vessel on the surface, failed when gas leaking from the pipe combined with cold water formed methane hydrate crystals that blocked the opening at the top of the dome.[9]
On May 14, engineers began the process of positioning a 6-inch (15 cm) wide riser insertion tube into the 21-inch (53 cm) wide burst pipe.[9] There was a stopper-like washer around the tube that plugs the end of the riser and diverts the flow into the insertion tube.[10] The collected gas was flared and oil stored on the board of drillship Discoverer Enterprise.[11] 924,000 US gallons (22,000 barrels) of oil was collected before removal of the tube.[12]
On May 26, BP tried to close the well using a technique called "top kill", which also failed.[13] This process involved pumping heavy drilling fluids through two 3-inch (7.6 cm) lines into the blowout preventer to restrict the flow of oil before sealing it permanently with cement.[14][15][16]
On May 29, BP moved to the Lower Marine Riser Package (LMRP) Cap Containment System by removing the damaged riser from the top of the blowout preventer and covering the pipe by the cap which connects it to a riser. The cap was attached on June 3, and the system began to capture the leaking oil.[17] On June 6, the CEO of BP Tony Hayward, stated that the amount captured was "probably the vast majority of the oil."[18] However, Ira Leifer, a member of the Flow Rate Technical Group (FRTG), claimed that more oil was escaping than before the riser was cut and the cap containment system was placed.[19]
On June 16, a second containment system connected directly to the blowout preventer became operational carrying oil and gas through a subsea manifold to the Q4000 service vessel with a processing capacity for about 5,000 barrels (210,000 US gallons; 790 cubic metres) of oil per day. Oil and gas are both burned on Q4000 in a clean-burning system.[20]
As Discoverer Enterprise's processing capacity was insufficient, drillship Discoverer Clear Leader and the floating production, storage and offloading (FPSO) vessel Helix Producer 1 were added, offloading oil with tankers Evi Knutsen, and Juanita.[21][22] Each tanker has a total capacity of 750,000 barrels (32,000,000 US gallons; 119,000 cubic metres).[20] In addition, FPSO Seillean, and well testing vessel Toisa Pisces would process oil. They are offloaded by shuttle tanker Loch Rannoch.[20]
On July 5, BP announced that its one-day oil recovery effort accounted for 24,980 barrels (3,972 m3) of oil, and the flaring off of 57.1 million cubic feet (1,620,000 m3) of natural gas. The total oil collection to date for the spill was estimated at 657,300 barrels (104,500 m3).[23] The government's estimates suggested the cap and other equipment were capturing less than half of the oil leaking from the sea floor as of late June.[24]
On July 10, robots removed the containment cap to replace it with a better-fitting cap ("Top Hat Number 10"); this meant all of the leaking oil would escape until the new cap was in place.[25] A broken pipe was taken out on July 11 and replaced with a flange spool resembling a pipe, on top of which the new cap was located.[26][27] The well integrity test was scheduled to take place after the installation of a three-ram capping stack over the lower marine riser package of the Deepwater Horizon semi-submersible rig on July 13. On July 14, BP announced that the test would be delayed under Allen's orders; oil continued to flow into the Gulf.[4][28]
Temporary closure
On July 15, 2010, BP announced that it had successfully plugged the oil leak using a tightly fitted cap. The cap, weighing 75 tons and standing 30 feet (9.1 m) high, is now bolted to the failed blowout preventer. It consists of a Flange Transition Spool and a 3 Ram Stack and is a temporary solution.[29][30]
President Barack Obama cautiously welcomed the news that the leak had been stopped, though stressing, "it is important we don't get ahead of ourselves".[31] If the cap holds for the planned 48 hours, its valves will be reopened temporarily in order to allow for seismic tests to ensure that oil is not escaping into the bedrock.[29] At the time of the stoppage, oil had been leaking continuously into the Gulf of Mexico for 85 days, 16 hours and 25 minutes since the Deepwater Horizon drilling rig exploded on April 20, 2010.[29]
Until July 19, 2010, there was no evidence that the well had ruptured, meaning that the cap appeared to be working.[31][32] According to Thad Allen, the retired US Coast Guard admiral in charge of the operation to stop the leak, the cap will be used to channel the flowing oil to surface ships for collection after the 48-hour test period and will be used to shut the well down during bad weather rather than permanently cap the well, which is expected to happen in mid-August 2010, when relief wells have been completed.[32] However, on July 19, 2010, seepage was detected from the seafloor within two kilometres of the well. Allen believes it probably has nothing to do with the well, as oil and gas are known to ooze naturally from fissures in the bottom of the Gulf of Mexico.[33][34]
On July 22, Adm. Thad Allen faced a difficult decision. Forecasts of the track of tropical storm Bonnie made it imperative that the support ships and rigs leave the site. The capping stack would thus be unsupervised for several days. The safe option would have been to open the valves and relieve pressure in the riser; however, that would obviously have the effect of turning back on the gush of oil and gas, with no option to either collect it or burn it off. Allen, in consultation with Energy Secretary Steven Chu, made the decision to leave the valves closed. Kent Wells, a senior vice president of BP, said “We have enough confidence to leave the well shut in.”[35] Since the storm proved weaker than expected on July 24, the ships returned to finish off the job once and for all. Efforts to close the well on a permanent basis soon began.[36]
Permanent closure
BP drilled two relief wells into the original well to enable them to block it. Once the relief wells reached the original borehole, the operator pumped drilling fluid into the original well. Transocean's Development Driller III started drilling a first relief well on May 2 and was at 13,978 feet (4,260 m) out of 18,000 feet (5,500 m) as of June 14. GSF Development Driller II started drilling a second relief on May 16 and was halted at 8,576 feet (2,614 m) out of 18,000 feet (5,500 m) as of June 14 while BP engineers verified the operational status of the second relief well's blowout preventer.[37][38][39][40][41][42] The relief wells began operating in August 2010[43] at a cost of about $100 million per well.[44][45]
Despite delays caused by Tropical Storm Bonnie, the first phase of stopping the leak was expected to start on July 30. Lining a relief shaft with steel casing was expected to resume on July 28, and a relief tunnel would take a week to drill but may be needed if phase one does not work.[36]
Adm. Thad Allen said on July 26 that the "static kill", using mud and cement poured into the top of the well, could start on August 2. The "bottom kill" would follow, with mud and cement entering the well under the sea floor, possibly by August 7.[46]
Starting at 15:00 CDT on August 3, first test oil then drilling mud was pumped at a slow rate of approximately two barrels/minute into the well-head. Pumping continued for eight hours, at the end of which time the well was declared to be "in a static condition."[47]
At 09:15 CDT on August 4, with Adm. Allen's approval, BP began pumping cement from the top, sealing that part of the flow channel permanently.[48]
On August 4, Allen said the static kill was working.[49] Two weeks later, though, Allen said it was uncertain when the well could be declared completely sealed. The bottom kill had yet to take place, and the relief well had been delayed by storms. Even when the relief well was ready, he said, BP had to make sure pressure would not build up again.[50]
On September 10, Allen said the bottom kill could start sooner than expected because a "locking sleeve" could be used on top of the well to prevent excessive pressure from causing problems. BP said the relief well was about 50 feet (15 m) from the intersection, and finishing the boring would take four more days.[51] On September 16, the relief well reached its destination and pumping of cement to seal the well began.[52] Officials said on September 18 that the cement pumped in from the base of the well had completed the sealing of the well.[53] On September 19, after pressure testing, Allen declared the well "officially dead".[54]
Considerations of using explosives
In mid-May 2010, United States Secretary of Energy Steven Chu assembled a team of nuclear physicists, including hydrogen bomb designer Richard Garwin and Sandia National Laboratories director Tom Hunter.[55] On May 24 BP ruled out conventional explosives, saying that if blasts failed to clog the well, "We would have denied ourselves all other options."[56]
Federal officials also ruled out nuclear devices due to environmental and political risks (Doing so is a violation of Comprehensive Nuclear-Test-Ban Treaty that the United States has signed.[57] Admiral Thad Allen stated, "since we don't know the condition of that well bore or the casings, I would be cautious about putting any kind of kinetic energy on that well head, because what you may do is create open communication between the reservoir and the sea floor."[58] Allen also said that the result could be oil seeping through cracks and through the seafloor, "and then be uncontrolled until the reservoir pressure equalized with the hydrostatic pressure; I think that's a risk that's too great to take a chance on, myself."[59] Casing integrity concerns also influenced the pressure chosen for the top kill procedure.[60]
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references>
tag; parameter "group" is allowed only.
<references />
, or <references group="..." />
- ↑ http://www.nytimes.com/2010/07/16/us/16spill.html?hp New York Times – July 16, 2010
- ↑ Collection Report(PDF). U.S. Fish and Wildlife Service. 5 July 2010.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ 5.0 5.1 5.2 Berkeley scientist advises on clean-up in gulf oil spill - June 4, 2010 U.S. Fish and Wildlife Service. 5 July 2010.
- ↑ Giant oil skimmer 'A Whale' deemed a bust for Gulf of Mexico spill | NOLA.com
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 20.0 20.1 20.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 29.0 29.1 29.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ BP's Deepwater Oil Spill - Tests End and the Kill Begins, Well Reaches Static Condition
- ↑ BP begins pumping cement in next stage of 'static kill'
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Achenbach, H.; MacGillis, A. (30 May 2010). As 'top kill' effort fails, BP must fall back on oil spill containment strategy. Washington Post. Retrieved 2010-07-04.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.