Deepwater Horizon oil spill response

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.

Q4000-Discoverer-Enterprise.jpg This article is part of a series about the
Deepwater Horizon oil spill
File:Workers building boom against oil spill after Deepwater Horizon disaster.jpg
United States Environmental Services workers prepare oil containment booms for deployment

A variety of techniques were used to address fundamental strategies for addressing the spilled oil, which were: to contain oil on the surface, dispersal, and removal. While most of the oil drilled off Louisiana is a lighter crude, the leaking oil was of a heavier blend which contained asphalt-like substances. According to Ed Overton, who heads a federal chemical hazard assessment team for oil spills, this type of oil emulsifies well. Once it becomes emulsified, it no longer evaporates as quickly as regular oil, does not rinse off as easily, cannot be eaten by microbes as easily, and does not burn as well. "That type of mixture essentially removes all the best oil clean-up weapons", Overton said.[1]

On 6 May 2010, BP began documenting the daily response efforts on its web site.[2] On 28 April, the US military joined the cleanup operation.[3] The response increased in scale as the spill volume grew. Initially, BP employed remotely operated underwater vehicles (ROV's), 700 workers, 4 airplanes, and 32 vessels.[4] By 29 April 69 vessels, including skimmers, tugs, barges, and recovery vessels, were in use. By 4 May, the USCG estimated that 170 vessels, and nearly 7,500 personnel were participating, with an additional 2,000 volunteers assisting.[5] On 31 May, BP set up a call line to take cleanup suggestions which received 92,000 responses by late June, 320 of which were categorized as promising.[6]

In summer 2010, approximately 47,000 people and 7,000 vessels were involved in the response works. By 3 October 2012, federal response costs amounted $850 million, most of them reimbursed by BP. As of January 2013, 935 response personnel were still involved in response activities in the region. For that time BP's costs for cleanup operations exceeded $14 billion.[7]

Containment

File:New Harbor Island, La during the Deepwater Horizon oil spill.jpg
An oil containment boom deployed by the U.S. Navy surrounds New Harbor Island, Louisiana.

The response included deploying many miles of containment boom, whose purpose is to either corral the oil, or to block it from a marsh, mangrove, shrimp/crab/oyster ranch or other ecologically sensitive areas. Booms extend 18–48 inches (0.46–1.22 m) above and below the water surface and are effective only in relatively calm and slow-moving waters. More than 100,000 feet (30 km) of containment booms were initially deployed to protect the coast and the Mississippi River Delta.[8] By the next day, that nearly doubled to 180,000 feet (55 km), with an additional 300,000 feet (91 km) staged or being deployed.[9][10] In total, during the crisis 9,100,000 feet (2,800 km) one-time use sorbent booms and 4,200,000 feet (1,300 km) of containment booms were deployed.[11]

Some US lawmakers and local officials claimed that the booms didn't work as intended, saying there is more shoreline to protect than lengths of boom to protect it and that inexperienced operators didn't lay the boom correctly. Billy Nungesser, president of Plaquemines Parish, Louisiana, said the boom "washes up on the shore with the oil, and then we have oil in the marsh, and we have an oily boom. So we have two problems".[12] According to Naomi Klein, writing for the Guardian, "the ocean's winds and currents have made a mockery of the lightweight booms BP has laid out to absorb the oil." Byron Encalade, president of the Louisiana Oysters Association, told BP that the "oil's gonna go over the booms or underneath the bottom", and according to Klein, he was right. Rick Steiner, a marine biologist who closely followed the clean-up operations, estimated that "70% or 80% of the booms are doing absolutely nothing at all".[13] Local officials along the gulf maintained that there was a scarcity of boom, especially the heavier "ocean boom". BP, in its regional plan, says that boom is not effective in waters with waves more than three to four feet high; waves in the gulf often exceed that height.[14]

Louisiana barrier island plan

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The Louisiana barrier island plan was initialized to construct barrier islands protecting the coast of Louisiana from the spill. The plan was criticised due to expenses and ineffectiveness.[15][16] It is alleged by critics that the decision to pursue the project was made on a political basis with little input from the scientific experts.[17] The EPA expressed concern for the berms threaten wildlife.[18]

The presidential commission concluded in December 2010 that the $220 million sand berms captured a "minuscule amount" of oil (1,000 barrels (160 m3)) and proved "underwhelmingly effective" as well as "overwhelmingly expensive". Of the $360 million BP gave for the berms, Louisiana plans to spend $140 million to turn the 36 miles of berms into barrier islands.[19]

Dispersal

The spill was also notable for the volume of Corexit oil dispersant used, as well as the methods of application which that time were "purely experimental".[11] Although usage of dispersants was described as "most effective and fast moving tool for minimizing shoreline impact",[11] this use of dispersant was questioned at the time and its effects continue to be questioned and investigated.[20][21][22] Altogether, 1.84 million US gallons (7,000 m3) of dispersants were used; of this 771,000 US gallons (2,920 m3) were used subsea at the wellhead.[23]

Choice and composition of Corexit

A large four propeller airplane sprays Corexit onto oil-sheen water
A C-130 Hercules sprays Corexit dispersant onto the Gulf of Mexico

Corexit EC9500A and Corexit EC9527A were the principal dispersants employed.[24] The two formulations are neither the least toxic, nor the most effective, among the EPA's approved dispersants.[25] Twelve other products received better toxicity and effectiveness ratings, but BP says it chose to use Corexit because it was available the week of the rig explosion.[25][26] Critics contend that the major oil companies stockpile Corexit because of their close business relationship with its manufacturer Nalco.[25][27]

Environmental groups attempted to obtain information regarding the composition and safety of ingredients in Corexit through the Freedom of Information Act but were denied by the EPA. After Earthjustice sued on behalf of the Gulf Restoration Network and the Florida Wildlife Federation, the EPA released a list of all 57 chemicals in the 14 dispersents on the EPA's National Contingency Plan Product Schedule. The dispersants used contain propylene glycol, 2-butoxyethanol, and dioctyl sodium sulfosuccinate.[28][29]

Earthjustice and Toxipedia conducted the first analysis of the 57 chemicals found in Corexit formulas 9500 and 9527 in 2011. Results showed the dispersant could contain cancer-causing agents, hazardous toxins and endocrine-disrupting chemicals.[30] The analysis found "5 chemicals are associated with cancer; 33 are associated with skin irritation from rashes to burns; 33 are linked to eye irritation; 11 are or are suspected of being potential respiratory toxins or irritants; 10 are suspected kidney toxins; 8 are suspected or known to be toxic to aquatic organisms; and 5 are suspected to have a moderate acute toxicity to fish".[31]

Method and extent of use

To spray dispersants over 400 sorties flown were employed.[11] On 1 May 2010, two military C-130 Hercules aircraft were employed to spray oil dispersant.[32] More than half of the 1.1 million US gallons (4,200 m3) of chemical dispersants were applied at the wellhead 5,000 feet (1,500 m) under the sea.[33] This had never previously been tried but due to the unprecedented nature of this spill, BP along with the USCG and the EPA, decided to use "the first subsea injection of dispersant directly into oil at the source".[34]

Dispersants are said to facilitate the digestion of the oil by microbes. Mixing the dispersants with the oil at the wellhead would keep some oil below the surface and in theory, allow microbes to digest the oil before it reached the surface. Various risks were identified and evaluated, in particular that an increase in the microbe activity might reduce the oxygen in the water. The use of dispersants at the wellhead was pursued and NOAA estimated that roughly 409,000 barrels (65,000 m3) of oil were dispersed underwater.[35]

By 12 July 2010, BP had reported applying 1.07 million US gallons (4,100 m3) of Corexit on the surface and 721,000 US gallons (2,730 m3) underwater (subsea).[36] By 30 July 2010, more than 1.8 million US gallons (6,800 m3) of dispersant had been used, mostly Corexit 9500.[37]

Dispersant use was said to have stopped after the cap was in place.[38] Marine toxicologist Riki Ott wrote an open letter to the EPA in late August with evidence that dispersant use had not stopped and that it was being administered near shore.[39] Independent testing supported her claim. New Orleans-based attorney Stuart Smith, representing the Louisiana-based United Commercial Fisherman's Association and the Louisiana Environmental Action Network said he "personally saw C-130s applying dispersants from [his] hotel room in the Florida Panhandle. They were spraying directly adjacent to the beach right at dusk. Fishermen I've talked to say they've been sprayed. This idea they are not using this stuff near the coast is nonsense."[40]

Environmental controversy over Corexit

Sign protesting use of toxic Corexit chemical dispersant in the Deepwater Horizon oil spill, at the Bastille Day Tumble, French Quarter, New Orleans

Environmental scientists say the dispersants, which can cause genetic mutations and cancer, add to the toxicity of a spill, and that sea turtles and bluefin tuna are exposed to an even greater risk than crude alone. According to them, the dangers are even greater for dispersants poured into the source of a spill, where they are picked up by the current and wash through the Gulf.[41]

On 7 May 2010, Secretary Alan Levine of the Louisiana Department of Health and Hospitals, Louisiana Department of Environmental Quality Secretary Peggy Hatch, and Louisiana Department of Wildlife and Fisheries Secretary Robert Barham sent a letter to BP outlining their concerns related to potential dispersant impact on Louisiana's wildlife and fisheries, environment, aquatic life, and public health. Officials requested that BP release information on their dispersant effects. After three underwater tests the EPA approved the injection of dispersants directly at the leak site to break up the oil before it reached the surface.[42]

In mid-May, independent scientists suggested that underwater injection of Corexit into the leak may have been responsible for the oil plumes discovered below the surface.[26]

On 19 May, the EPA gave BP 24 hours to choose less toxic alternatives to Corexit from the list of dispersants on the National Contingency Plan Product Schedule and begin applying the new dispersant(s) within 72 hours of EPA approval or provide a detailed reasoning why the approved products did not meet the required standards.[43][44]

On 20 May, US Polychemical Corporation reportedly received an order from BP for its Dispersit SPC 1000 dispersant. US Polychemical said that it could produce 20,000 US gallons (76 m3) a day in the first few days, increasing up to 60,000 US gallons (230 m3) a day thereafter.[45] Also on 20 May, BP determined that none of the alternative products met all three criteria of availability, toxicity, and effectiveness.[46] On 24 May, EPA Administrator Lisa Jackson ordered the EPA to conduct its own evaluation of alternatives and ordered BP to scale back dispersant use.[47][48]

According to analysis of daily dispersant reports provided by the Deepwater Horizon Unified Command, before 26 May, BP used 25,689 US gallons per day (0.0011255 m3/s) of Corexit. After the EPA directive, the daily average of dispersant use dropped to 23,250 US gallons per day (0.001019 m3/s), a 9% decline.[49]

The 12 July 2010 BP report listed available stocks of Corexit which decreased by over 965,000 US gallons (3,650 m3) without reported application, suggesting either stock diversion or unreported application. Under reported subsea application of 1.69 million US gallons (6,400 m3) would account for this discrepancy. Given the suggested dispersant to oil ratio between 1:10 and 1:50, the possible use of 1.69 million US gallons (6,400 m3) in subsea application could be expected to suspend between 0.4 to 2 million barrels (64,000 to 318,000 m3) of oil below the surface of the Gulf.[citation needed]

On 31 July, Rep. Edward Markey, Chairman of the House Energy and Environment Subcommittee, released a letter sent to National Incident Commander Thad Allen, and documents revealing that the USCG repeatedly allowed BP to use excessive amounts of the dispersant Corexit on the surface of the ocean. Markey's letter, based on an analysis conducted by the Energy and Environment Subcommittee staff, further showed that by comparing the amounts BP reported using to Congress to the amounts contained in the company's requests for exemptions from the ban on surface dispersants it submitted to the USCG, that BP often exceeded its own requests, with little indication that it informed the USCG, or that the USCG attempted to verify whether BP was exceeding approved volumes. "Either BP was lying to Congress or to the Coast Guard about how much dispersants they were shooting onto the ocean," said Markey.[50]

On 2 August 2010, the EPA said dispersants did no more harm to the environment than the oil itself, and that they stopped a large amount of oil from reaching the coast by making the oil break down faster.[38] However, independent scientists and EPA's own experts continue to voice concerns regarding the use of dispersants.[51] According to a 2012 study, Corexit made the oil 52 times more toxic and allowed polycyclic aromatic hydrocarbons (PAHs) to more deeply penetrate beaches and possibly groundwater.[52][53]

Long-term effects of Corexit

NOAA states that toxicity tests have suggested that the acute risk of dispersant-oil mixtures is no greater than that of oil alone.[35] However, some experts believe that all the benefits and costs may not be known for decades.[35] A study from Georgia Tech and Universidad Autonoma de Aguascalientes (UAA), Mexico reported in late 2012 that Corexit made the oil up to 52 times more toxic than oil alone.[52][54] Additionally, the dispersant made oil sink faster and more deeply into the beaches, and possibly the groundwater.[53][55]

University of South Florida scientists released preliminary results on the toxicity of microscopic drops of oil in the undersea plumes, finding that they may be more toxic than previously thought. The researchers say the dispersed oil appears to be negatively affecting bacteria and phytoplankton – the microscopic plants which make up the basis of the Gulf's food web. The field-based results were consistent with shore-based laboratory studies showing that phytoplankton are more sensitive to chemical dispersants than the bacteria, which are more sensitive to oil.[56]

Because the dispersants were applied deep under the sea, much of the oil never rose to the surface – which means it went somewhere else, said Robert Diaz, a marine scientist at the College of William and Mary, "The dispersants definitely don't make oil disappear. They take it from one area in an ecosystem and put it in another," Diaz said.[33] One plume of dispersed oil measured at 22 miles (35 km) long, more than a mile wide and 650 feet (200 m) tall. The plume showed the oil "is persisting for longer periods than we would have expected," said researchers with the Woods Hole Oceanographic Institution. "Many people speculated that subsurface oil droplets were being easily biodegraded. Well, we didn't find that. We found it was still there".[57] In a major study on the plume, experts found the most worrisome part to be the slow pace at which the oil was breaking down in the cold, 40 °F (4 °C) water at depths of 3,000 feet (910 m) 'making it a long-lasting but unseen threat to vulnerable marine life'.[58] Marine Sciences at the University of Georgia reported findings of a substantial layer of oily sediment stretching for dozens of miles in all directions from the capped well.[59]

Removal

Dark clouds of smoke and fire emerge as oil burns during a controlled fire in the Gulf of Mexico, May 6, 2010.
File:A-whale-tanker.jpg
The Taiwanese retrofitted skimmer, A Whale

The three basic approaches for removing the oil from the water were: burning the oil, filtering offshore, and collecting for later processing. On 28 April 2010, the USCG announced plans to corral and burn off up to 1,000 barrels (160 m3) of oil each day.[9][60] In November 2010 the EPA reported that in-situ controlled burning removed as much as 13 million US gallons (49,000 m3) of oil from the water. By other data burnings remediating approximately 265,000 barrels (11,100,000 US gal; 42,100 m3) of oil.[11] There were 411 fires set between April to mid-July 2010 from which cancer-causing dioxins were released. The EPA stated that the release was minimal. A second research team concluded "there was only a small added risk of cancer to people breathing polluted air or eating tainted fish".[61]

Oil was collected by using skimmers. More than 60 open-water skimmers were deployed, including 12 purpose-built vehicles.[11] A Taiwanese supertanker, A Whale, was retrofitted after the Deepwater explosion for skimming large amounts of oil in the Gulf.[62] The ship was tested in early July 2010 but failed to collect a significant amount of oil.[63] Due to BP's use of Corexit the oil was too dispersed to collect, according to a spokesperson for shipowner TMT.[64]

The EPA prohibited the use of skimmers that left more than 15 ppm of oil in the water. Many large-scale skimmers exceeded the limit.[65] An urban myth developed that the U.S. government declined the offers from foreign countries because of the requirements of the Jones Act.[66] This proved untrue and many foreign assets deployed to aid in cleanup efforts.[67]

In mid June, BP ordered 32 machines that separate oil and water with each machine capable of extracting up to 2,000 barrels (320 m3) per day,[68][69] After testing machines for one week, BP decided to use the technology[70] and by 28 June, had removed 890,000 barrels (141,000 m3) of oily liquid.[71] The USCG said 33,000,000 US gallons (120,000 m3) of tainted water was recovered, with 5,000,000 US gallons (19,000 m3) of that consisting of oil. BP said 826,800 barrels (131,450 m3) had been recovered or flared.[72]

Oil budget

The table below presents the NOAA estimates based on an estimated release of 4,900,000 barrels (780,000 m3) of oil (the category "chemically dispersed" includes dispersal at the surface and at the wellhead; "naturally dispersed" was mostly at the wellhead; "residual" is the oil remaining as surface sheen, floating tarballs, and oil washed ashore or buried in sediment). However, there is plus or minus 10% uncertainty in the total volume of the spill.[72][73]

Category Estimate Alternative 1 Alternative 2
Direct recovery from wellhead 17% 17% 17%
Burned at the surface 5% 5% 5%
Skimmed from the surface 3% 3% 3%
Chemically dispersed 8% 10% 6%
Naturally dispersed 16% 20% 12%
Evaporated or dissolved 25% 32% 18%
Residual remaining 26% 13% 39%

Two months after these numbers were released Carol Browner, director of the White House Office of Energy and Climate Change Policy, said they were "never meant to be a precise tool" and that the data "was simply not designed to explain, or capable of explaining, the fate of the oil. Oil that the budget classified as dispersed, dissolved, or evaporated is not necessarily gone".[74]

Based on these estimates, up to 75% of the oil from BP's Gulf oil disaster still remained in the Gulf environment, according to Christopher Haney, chief scientist for Defenders of Wildlife, who called the government report's conclusions misleading. Haney reiterated "terms such as 'dispersed,' 'dissolved' and 'residual' do not mean gone. That's comparable to saying the sugar dissolved in my coffee is no longer there because I can't see it. By Director Lubchenco's own acknowledgment, the oil which is out of sight is not benign. "Whether buried under beaches or settling on the ocean floor, residues from the spill will remain toxic for decades."[75]

Appearing before Congress, Bill Lehr, a senior scientist at NOAA's Office of Response and Restoration, defended a report written by the National Incident Command on the fate of the oil. The report relied on numbers generated by government and non-government oil spill experts, using an "Oil Budget Calculator" (OBC) developed for the spill. Based upon the OBC, Lehr said 6% was burned and 4% was skimmed but he could not be confident of numbers for the amount collected from beaches. As seen in the table above, he pointed out that much of the oil has evaporated or been dispersed or dissolved into the water column. Under questioning from congressman Ed Markey, Lehr agreed that the report said the amount of oil that went into the Gulf was 4.1 million barrels (650×10^3 m3), noting that 800,000 barrels (130,000 m3) were siphoned off directly from the well.

NOAA was criticized by some independent scientists and Congress for the report's conclusions and for failing to explain how the scientists arrived at the calculations detailed in the table above. Ian MacDonald, an ocean scientist at Florida State University (FSU), claimed the NIC report "was not science". He accused the White House of making "sweeping and largely unsupported" claims that 3/4 of the oil in the Gulf was gone and called the report "misleading". "The imprint will be there in the Gulf of Mexico for the rest of my life. It is not gone and it will not go away quickly", he concluded.[76]

A formally peer-reviewed report documenting the OBC was scheduled for release in early October.[77] Markey told Lehr the NIC report had given the public a false sense of confidence. "You shouldn't have released it until you knew it was right," he said.

By late July, two weeks after the flow of oil had stopped, oil on the surface of the Gulf had largely dissipated but concern still remained for underwater oil and ecological damage.[78]

Markus Huettel, a benthic ecologist at FSU who has been studying the spill since 2010, maintains that while much of BP's oil was degraded or evaporated, as least 60% remains unaccounted for. Huettel cautions that only one category from NOAA's "oil budget", the 17% directly recovered from the wellhead, is actually known. "All the other categories, like oil burned, skimmed, chemically dispersed, or evaporated, are guesses that could change by a factor or two or even more in some cases". Huettel stressed that even after much research, some categories, like how much oil was dispersed at depth, will never be accurately known. "That oil is somewhere, but nobody knows where, and nobody knows how much has settled on the seafloor."[79]

Oil eating microbes

Several studies suggest that bacteria has consumed a part of oil in the sea.[7][80] In August, 2010, a study of bacterial activity in the Gulf led by Terry Hazen of the Lawrence Berkeley National Laboratory, found a previously unknown bacterial species and reported in the journal Science that it was able to break down the oil without depleting oxygen levels.[81] Hazen's interpretation had its skeptics. John Kessler, a chemical oceanographer at Texas A&M University says "what Hazen was measuring was a component of the entire hydrocarbon matrix," which is a mix of thousands of different molecules. Although the few molecules described in the new paper in Science may well have degraded within weeks, Kessler says, "there are others that have much longer half-lives – on the order of years, sometimes even decades."[82] He noted that the missing oil has been found in the form of large oil plumes, one the size of Manhattan[quantify], which do not appear to be biodegrading very fast.[83]

By mid-September, research showed these microbes mainly digested natural gas spewing from the wellhead – propane, ethane, and butane – rather than oil, according to a subsequent study.[84] David L. Valentine, a professor of microbial geochemistry at UC Santa Barbara, said that the oil-gobbling properties of the microbes had been grossly overstated.[85] Methane was the most abundant hydrocarbon released during the spill. It has been suggested that vigorous deepwater bacterial bloom respired nearly all the released methane within 4 months, leaving behind a residual microbial community containing methanotrophic bacteria.[86]

Some experts suggested that the oil eating bacteria may have caused health issues for residents of the Gulf. Local physicians noted an outbreak of mysterious skin rashes which, according to marine toxicologist Riki Ott, could be the result of proliferation of the bacteria in Gulf waters. In order to eat the oil faster, oil eating bacteria like Alcanivorax borkumensis has been genetically modified. Ott claims to have spoken with numerous residents and tourists of the Gulf who have experienced symptoms like rashes and "peeling palms" after contact with the water in the Gulf.[85][87]

Cleanup

On 15 April 2014, BP claimed that cleanup along the coast was substantially complete, but the United States Coast Guard responded that a lot of work remained.[88]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Lua error in package.lua at line 80: module 'strict' not found.
  12. Containment boom effort comes up short in BP oil spill. The Christian Science Monitor. (11 June 2010). Retrieved 2011-04-07.
  13. Gulf oil spill - A hole in the world | Naomi Klein | The Guardian
  14. BP spill response plans severely flawed | MNN - Mother Nature Network
  15. "Slosh and Berm: Building Sand Barriers off Louisiana's Coast to Hold Back Oil Spill Has Low Probability of Success" David Biello in Scientific American June 8, 2010, accessed July 19, 2010
  16. BP Oil Spill Sand Berm Cleanup - Oil and Sand Berm Controversy - Popular Mechanics
  17. "Sand berms partially political" article by Amy Wold in The Advocate (Louisiana) July 11, 2010, accessed July 19, 2010 Archived July 12, 2010 at the Wayback Machine
  18. EPA slams Jindal's sand berm plan | wwltv.com New Orleans
  19. Oil-spill panel calls Jindal's sand berms a $220M waste
  20. Oil dispersants used in Gulf of Mexico spill causing alarm | al.com
  21. Chemicals Meant To Break Up BP Oil Spill Present New Environmental Concerns - ProPublica
  22. Migratory Birds Carry Chemicals from BP Oil Spill to Minnesota Two Years After Disaster | Audubon Magazine Blog
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 25.2 Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Pensacola News Journal: Archives
  31. Impact of Gulf Spill's Underwater Dispersants Is Examined - NYTimes.com
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 35.2 Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Major Study Charts Long-Lasting Oil Plume in Gulf
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Burning off oil from BP spill in Gulf posed little health risk, feds say in new report (video) | al.com
  62. Gulf of Mexico may have godsend in form of TMT's 'A Whale' tanker as it tries to clean BP oil spill, NY Daily News
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Why Is the Gulf Cleanup So Slow?, Wall St. Journal, 2 July 2010
  66. The President Does a Jones Act, Wall St. Journal, 19 June 2010
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Gabbatt, Adam (16 June 2010). BP oil spill: Kevin Costner's oil-water separation machines help with clean-up. The Guardian.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Clarke, Sanchez, Bonfiles, Escobedo (15 June 2010). "BP 'Excited' Over Kevin Costner's Oil Cleanup Machine, Purchases 32". ABC News Good Morning America.
  71. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  72. 72.0 72.1 Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Is The Oil Spill Horror Over? : Story of the Week: Science Channel
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Tar Balls from BP Oil Spill Wash Up on Gulf Beaches
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. 85.0 85.1 Oil-eating microbes may not be all they're cracked up to be | The Upshot Yahoo! News. Yahoo!! News. Retrieved 2011-04-07.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Riki Ott: Bio-Remediation or Bio-Hazard? Dispersants, Bacteria and Illness in the Gulf. Huffington Post. Retrieved 2011-04-07.
  88. Lua error in package.lua at line 80: module 'strict' not found.