List of pipeline accidents in the United States in 2013

The following is a list of pipeline accidents in the United States in 2013. It is one of several lists of U.S. pipeline accidents. See also list of natural gas and oil production accidents in the United States.

Incidents

This is not a complete list of all pipeline accidents. For natural gas alone, the Pipeline and Hazardous Materials Safety Administration (PHMSA), a United States Department of Transportation agency, has collected data on more than 3,200 accidents deemed serious or significant since 1987.

A "significant incident" results in any of the following consequences:

  • fatality or injury requiring in-patient hospitalization
  • $50,000 or more in total costs, measured in 1984 dollars
  • liquid releases of five or more barrels (42 US gal/barrel)
  • releases resulting in an unintentional fire or explosion

PHMSA and the National Transportation Safety Board (NTSB) post incident data and results of investigations into accidents involving pipelines that carry a variety of products, including natural gas, oil, diesel fuel, gasoline, kerosene, jet fuel, carbon dioxide, and other substances. Occasionally pipelines are repurposed to carry different products.[1]

2013

  • On January 1, a Colonial Pipeline line was overpressured by improper operation, causing a spill of about 5,500 gallons of petroleum product in Greensboro, North Carolina. About 1,000 gallons of product was not recovered.[2]
  • On January 15, a utility crew struck and ruptured a 4-inch gas pipeline in Lewisville, Texas, causing a nearby house to explode later on. The explosion killed a man.[3]
  • An independent contractor installing fiber-optic cable for a cable company in Kansas City, Missouri inadvertently struck an underground gas line on February 19. Gas later caught fire, and created an explosion that destroyed a popular local restaurant, killing one of the workers there, and injuring about 15 others near the scene.[4][5]
  • A tug towing a barge struck and ruptured a Chevron LPG pipeline at Bayou Perot, a marshy area on the borders of Jefferson Parish and Lafourche Parish, Louisiana on March 12. The tug Captain was severely burned when the escaping gas ignited, and died several weeks later from those injuries.[6][7]
  • On March 8, pipeline equipment failure resulted in a spill of 6,000 barrels of crude oil, in eastern Columbia County, Arkansas.[8]
  • On March 18, a Chevron 8-inch petroleum products pipeline ruptured along a seam, spilling diesel fuel into Willard Bay State Park near Ogden, Utah. Wildlife was coated with diesel, but the fuel was prevented from entering into water supply intakes. About 25,000 gallons of diesel were spilled.[9][10]
  • A Williams Companies 24-inch gas gathering pipeline failed in Marshall County, West Virginia on March 22. There were no injuries.[11]
  • The 2013 Mayflower oil spill occurred when ExxonMobil's 20-inch Pegasus crude oil pipeline spilled near Mayflower, Arkansas on March 29, causing crude to flow through yards and gutters, and towards Lake Conway. Wildlife was coated in some places. Twenty-two houses were evacuated, due to the fumes and fire hazard. Estimates say the total amount of 190,000 gallons of diluted bitumen were spilled. Hook cracks and extremely low impact toughness in the LF-ERW seam of the pipe were identified as causes of the failure.[12][13][14][15]
  • On April 4, an explosion and fire occurred at a gas compressor station near Guthrie, Oklahoma. Nearby houses were evacuated. There were no injuries reported.[16]
  • A flash fire at a pipeline gas compressor station broke out when natural gas liquids ignited in Tyler County, West Virginia on April 11, seriously burning three workers, two of whom later died. The workers were performing pipeline pigging operations.[17][18]
  • On April 30, the Pegasus oil pipeline spilled a small amount of crude into a residential yard in Ripley County, Missouri, a month after the same pipe spewed thousands of barrels of crude in Arkansas. The Pegasus pipeline was out of service from the Mayflower, Arkansas spill, accounting for the minimal amount of oil spilled in Missouri.[19]
  • On May 9, diesel fuel was detected to be leaking from a Marathon pipeline in Indianapolis, Indiana. Over 20,000 gallons of diesel leaked, at a slow rate that was not detected by SCADA systems. Cleanup caused a nearby major road to be shut down for five days. There were no injuries reported.[20]
  • Late night on May 14, an explosion and fire hit a Williams Companies gas compressor station near Brooklyn Township, Pennsylvania. There were no reported injuries.[21]
  • On May 8, the Kinder Morgan Tejas pipeline compressor station near Crockett, Texas, required an emergency shutdown and subsequently had a fire that caused $7,502,188 in property damage.[22][23]
  • On May 18, a 24-inch fill line failed, on an Enbridge tank, in Cushing, Oklahoma, spilling about 105,000 gallons of crude oil. The cause was internal corrosion of the line.[24]
  • On May 30, two construction workers were injured, when a fire erupted during welding at a Williams Companies natural gas facility in Hunterdon County, New Jersey.[25]
  • A 12-inch gas transmission pipeline failed near Torrington, Wyoming on June 13. LF-ERW seam failure was suspected as cause. There was no fire or injuries.[26]
  • On June 18, in Washington Parish, Louisiana, a Kinder Morgan Florida Gas Transmission Company 30" diameter pipeline ruptured and exploded before dawn, jolting residents out of their beds. No one was seriously hurt but 55 homes were evacuated. The blast knocked down trees in an area about 200 yards across and the fire burned those within another 300 yards. "The ground around the crater is completely bare. The dirt around it is just like it had been cooked in a kiln," and an 80-foot section of pipe was destroyed.[27]
  • On July 4, a fire involved a gas compressor and a nearby ruptured 2-inch gas pipeline in Gilmore Township, Pennsylvania. There were no injuries.[28]
  • An 8-inch natural gas pipeline released gas from a rupture at 1,400 psi, for 90 minutes in New Franklin, Ohio on July 22, forcing 75 people to evacuate the area. Afterward, the local Fire Chief said that pipeline owners refused to give information to first responders in previous requests.[29]
  • Early on July 23, a downed 13,000 volt power line sparked a massive gas fire in Mamaroneck, New York when a gas main was damaged by the electricity. Three automobiles were destroyed, and houses were threatened for a time.[30]
  • On July 26, a leaking BP 20-inch crude oil pipeline spilled 50 to 100 barrels of crude oil in Washington County, Oklahoma. Some of the crude spilled into a drainage ditch leading to a water reservoir.[31]
  • On the evening of August 12, a 10-inch NGL pipeline exploded and caused a massive propane-ethane mix fire in Erie, Illinois. A number of nearby residents were evacuated for a while, but there were no injuries. About 772,000 gallons of mix were burned or lost. The cause was from a manufacturing defect.[32][33]
  • A leak developed on a valve on Longhorn Pipeline in Austin, Texas during maintenance on August 14, spilling about 300 gallons of crude oil. There were no evacuations.[34]
  • Atmos Energy crews dug into a 4-inch gas pipeline in Overland Park, Kansas on September 2, causing an explosion and fire. There was no major damage or injuries.[35]
  • A 10-inch gas gathering pipeline ruptured and burned in Newton County, Texas on September 21. About a dozen people from nearby houses were evacuated for a time. There were no injuries.[36]
  • On September 24, a Denton TX city water utility worker ruptured a 1/2-inch gas pipeline in Denton, Texas, which immediately caused a fire that gave the worker minor burns. There was no other significant damage.[37]
  • A farmer near Tioga, North Dakota smelled oil for several days, before discovering a leaking 6-inch 20-year-old Tesoro pipeline under his wheat field, on September 29. Crews tried to burn off the oil at first. The spill size was estimated at 865,000 gallons, and covered over seven acres. There were no injuries. Corrosion was suspected as being the cause. Governor Jack Dalrymple said he wasn't told of the spill until October 9. In May 2014, it was announced that it would 2 1/2 more years before the spilled crude would be cleaned up.[38][39]
  • On October 7, a gas pipeline burst in Howard County, Texas. There was no fire, but dangerous hydrogen sulfide in the gas forced evacuations of nearby residents. There were no injuries.[40]
  • On October 7, authorities were notified of a Lion Oil Trading and Transportation crude oil pipeline leak in Columbia County, Arkansas. It was estimated that the leak started on September 21. Oil spread into a Horsehead Creek tributary. The Environmental Protection Agency said that approximately 1,500 barrels of oil were lost, but one lawsuit against the oil company claimed the full amount was as much as 5,000 barrels.[41]
  • A 30-inch Northern Natural Gas pipeline exploded and burned in Harper County, Oklahoma on October 8. 220 feet of the pipe was ejected from the ground. Flames were seen for a number of miles, and four houses nearby were evacuated. Oklahoma Highway 283 was closed for several hours until the fire was determined to be under control and safe. There were no injuries.[42][43][44]
  • On October 29, a Koch Industries 8-inch pipeline spilled about 400 barrels of crude oil near Smithville, Texas. The oil polluted a private stock pond and two overflow reservoirs.[45]
  • A Chevron operated 10-inch LPG pipeline was ruptured by contractors for the company installing a Cathodic protection system, near Milford, Texas, on November 14, causing a large fire, and forcing the evacuation of Milford and 200 students of a nearby school. A nearby 14-inch pipeline was threatened by the failure, but did not fail. There were no injuries reported. About 183,000 gallons of propane burned.[46][47][48][49]
  • An ExxonMobil gas plant exploded and burned on November 17, near Kingsville, Texas. The plant burned for over a day, but there were no reported injuries.[50]
  • On November 18, a gas pipeline burst near Ranger, Texas, causing a fire in a field, with flames reaching 100 feet high. Some houses nearby were evacuated for a time. The owner of the pipeline, Hanlon Gas, had been installing a new compressor station, and they believe a malfunction led to the rupture and fire. There were no injuries reported.[51]
  • On November 28 a 30-inch Panhandle Eastern natural gas pipeline exploded in Hughesville, Missouri causing several nearby buildings to catch fire. There was a local evacuation but no injuries. Metallurgical examination determined the root cause of the failure to be corrosion.[52][53]
  • On December 9, a 2-inch pipe on a propane dehydrator failed at the Dixie Pipeline Terminal in Apex, North Carolina, forcing evacuations and sheltering in place at nearby businesses. There was no fire or explosion.[54]
  • A Sunoco pipeline was found leaking gasoline on December 20, near Coal Township, Pennsylvania, from external corrosion. About 266 to 471 gallons of product were spilled, and, 1,421 tons of soil were removed, as part of the remediation of that leak.[55]
  • On December 27, two natural gas company workers had minor burns when the pipeline they were working leaked, and the escaping gas exploded and ignited in Shrewsbury, Massachusetts. Flames 30 feet high knocked out phone service in the area.[56]
  • On December 31, a contractor accidentally cut a live LPG pipeline during demolition work at a pipeline facility, in LaPorte, Texas. 2 workers received minor burns, and, 30,000 gallons of LPG were burned.[57]

References

  1. Data sets of PHMSA Pipeline Safety-Flagged Incidents for 1986-2001, 2002-2009, and 2010-2017 can be downloaded from the tab by that name on the PHMSA's Pipeline Incident Flagged Files page at https://www.phmsa.dot.gov/data-and-statistics/pipeline/pipeline-incident-flagged-files, accessed 2018.01.10. PHMSA Corrective Action Orders are at https://primis.phmsa.dot.gov/comm/reports/enforce/CAO_opid_0.html. PHMSA Pipeline Failure Investigation Reports are at https://www.phmsa.dot.gov/safety-reports/pipeline-failure-investigation-reports. NTSB Pipeline Accident Reports are at https://www.ntsb.gov/investigations/AccidentReports/Pages/pipeline.aspx.
  2. "PHMSA: Stakeholder Communications – Operator Information". dot.gov. Archived from the original on March 7, 2016. Retrieved May 23, 2016.
  3. "Investigation of deadly Lewisville explosion continues". Archived from the original on October 21, 2014. Retrieved January 15, 2015.
  4. "Cable Contractor Involved in KC Gas Explosion". Archived from the original on October 28, 2013. Retrieved January 15, 2015.
  5. "OSHA cites drilling company in fatal explosion at JJ's restaurant". kansascity. Archived from the original on December 3, 2013. Retrieved January 15, 2015.
  6. "Fire erupts after tug hits Chevron LPG pipeline: Coast Guard". Reuters. March 13, 2013. Archived from the original on March 26, 2013.
  7. "Tug captain Chad Breaux dies of burns after Louisiana gas explosion". UPI. Archived from the original on February 3, 2016. Retrieved January 15, 2015.
  8. "Settlement reached in 2013 Columbia County case of 6,000-barrel oil spill from pipeline". Magnolia Reporter – Magnolia, Arkansas News. Archived from the original on May 21, 2016. Retrieved May 23, 2016.
  9. "Utah Local News – Salt Lake City News, Sports, Archive – The Salt Lake Tribune". Archived from the original on October 20, 2014. Retrieved January 15, 2015.
  10. "CPF No. 5-2013-5006H" (PDF). Archived from the original (PDF) on January 25, 2017. Retrieved November 28, 2016.
  11. "UPDATE 1-Williams natgas line ruptures in West Virginia". Reuters. March 22, 2013. Archived from the original on October 28, 2013.
  12. Visser, Nick (April 9, 2013). "Maddow Slams Exxon's 'Paper Towel' Cleanup Efforts". Huffington Post. Archived from the original on April 12, 2013.
  13. "Web Extra: Background on Pipeline that Ruptured Near Mayflower". Archived from the original on April 10, 2013. Retrieved January 15, 2015.CS1 maint: bot: original URL status unknown (link)
  14. "Exxon: Cause of pipeline failure 'manufacturing defects'". Thv11.com. July 10, 2013. Archived from the original on October 28, 2013. Retrieved January 15, 2015.
  15. "Employee ran 1 mile to escape Guthrie natural gas explosion". koco. Archived from the original on October 28, 2013. Retrieved January 15, 2015.
  16. "Archived copy". Archived from the original on July 14, 2013. Retrieved April 16, 2013.CS1 maint: archived copy as title (link)
  17. "Exxon says Missouri oil spills from already-ruptured Pegasus line". Reuters. May 1, 2013. Archived from the original on September 24, 2015.
  18. "Report: Copper wire to blame for 2013 20K-gallon pipeline leak on nor…". archive.is. November 28, 2016. Archived from the original on November 28, 2016. Retrieved November 28, 2016.CS1 maint: bot: original URL status unknown (link)
  19. "DEP: Compressor stations shows signs of explosion". Archived from the original on February 20, 2015. Retrieved January 15, 2015.
  20. "PHMSA: Stakeholder Communications". Primis.phmsa.dot.gov. Archived from the original on December 21, 2014. Retrieved January 15, 2015.
  21. "Skytruth Alert: NRC Report: Natural Gas near Crockett, TX 2013-05-08". SkyTruth Alerts. Archived from the original on August 13, 2014. Retrieved January 15, 2015.
  22. "Failure Investigation Report – Enbridge Pipelines, LLC, Tank 3013 24-inch Fill Line failure in Cushing, OK" (PDF). Archived from the original (PDF) on June 29, 2017.
  23. "News – MyCentralJersey.com – mycentraljersey.com". MyCentralJersey.com. Archived from the original on October 24, 2014. Retrieved January 15, 2015.
  24. "CPF No. 5-2013-1007H" (PDF). Archived (PDF) from the original on February 18, 2017. Retrieved November 28, 2016.
  25. "Gas line explosion rattles Washington Parish | Home | The Advocate — …". archive.is. October 3, 2014. Archived from the original on October 3, 2014. Retrieved November 28, 2016.CS1 maint: bot: original URL status unknown (link)
  26. "Observer-Reporter – Blaze hits compressor station in Gilmore Township". Observer-Reporter. Archived from the original on October 20, 2014. Retrieved January 15, 2015.
  27. Kathy Antoniotti. "City not privy to pipeline locations inside own borders". www.ohio.com. Archived from the original on October 23, 2014. Retrieved January 15, 2015.
  28. "Downed Wires Lead To Car Fires, Ruptured Gas Line In Mamaroneck " CBS New York". Archived from the original on September 19, 2015. Retrieved January 15, 2015.
  29. "Crews Work To Contain BP Pipeline Leak In Osage County". newson6.com. July 26, 2013. Archived from the original on February 3, 2016. Retrieved January 18, 2016.
  30. "PHMSA: Stakeholder Communications - Operator Information". dot.gov. Archived from the original on December 27, 2016.
  31. Koronowski, Ryan (August 13, 2013). "Natural Gas Pipeline Causes Cornfield To Explode In Western Illinois". thinkprogress.org.
  32. "Search Results – KEYE-TV Austin". Archived from the original on August 27, 2013. Retrieved January 15, 2015.
  33. "Update to gas explosion in Overland Park". fox4kc.com. Archived from the original on October 21, 2014. Retrieved January 15, 2015.
  34. "Gas line not yet repaired after explosion in Buna". Beaumont Enterprise. Archived from the original on October 20, 2014. Retrieved January 15, 2015.
  35. "City worker hits gas line". Archived from the original on September 23, 2015. Retrieved January 15, 2015.
  36. "Corrosion may have led to North Dakota pipeline leak: regulator". Yahoo! News. October 11, 2013. Archived from the original on October 23, 2014. Retrieved January 15, 2015.
  37. "Archived copy". Archived from the original on June 15, 2015. Retrieved June 14, 2015.CS1 maint: archived copy as title (link)
  38. "No Injuries Reported After Pipeline Explosion in Howard County". newswest9.com. October 7, 2013. Archived from the original on February 3, 2016. Retrieved January 18, 2016.
  39. "(With video and three photos) Oil spill cleanup continues along Horsehead Creek tributary near Macedonia". Magnolia Reporter – Magnolia, Arkansas News. Retrieved January 15, 2015.
  40. "Resident Describes Gas Line Explosion In Harper County". news9.com. October 9, 2013. Archived from the original on January 26, 2016. Retrieved January 18, 2016.
  41. "Pipeline explosion shoots flames into Oklahoma sky". The Christian Science Monitor. Archived from the original on July 27, 2014. Retrieved January 15, 2015.
  42. "CPF No. 4-2013-1016H" (PDF). Archived (PDF) from the original on December 23, 2016. Retrieved November 28, 2016.
  43. "Archived copy". Archived from the original on October 31, 2013. Retrieved October 30, 2013.CS1 maint: archived copy as title (link)
  44. "Small Town Residents Allowed To Return After Fiery Blast". Archived from the original on October 21, 2014. Retrieved January 15, 2015.
  45. "UPDATE 4-Chevron pipeline explodes, burns in rural Texas". Reuters. November 14, 2013. Archived from the original on December 12, 2013.
  46. "CPF 4-2014-5012" (PDF). Archived (PDF) from the original on February 11, 2017. Retrieved November 28, 2016.
  47. "PHMSA: Stakeholder Communications - Operator Information". dot.gov. Archived from the original on December 27, 2016.
  48. "ExxonMobil's King Ranch Gas Plant Continues Burning – KiiiTV.com South Texas, Corpus Christi, Coastal Bend". kiiitv.com. November 18, 2013. Archived from the original on February 3, 2016. Retrieved January 18, 2016.
  49. "Gas Pipeline Rupture Send Flames 100 Feet Into Air". BigCountryHomepage. Associated Press. Archived from the original on October 23, 2014. Retrieved January 15, 2015.
  50. "CPF No. 3-2014-10088" (PDF). Archived (PDF) from the original on January 15, 2015.
  51. "Pipeline explosion sends fireball 300 feet into air". fox4kc.com. Archived from the original on January 3, 2015. Retrieved January 15, 2015.
  52. "Archived copy". Archived from the original on December 13, 2013. Retrieved December 10, 2013.CS1 maint: archived copy as title (link)
  53. "News-Item". News-Item.
  54. "Crews respond to gas-line fire in Shrewsbury". Archived from the original on October 20, 2014. Retrieved January 15, 2015.
  55. https://portal.phmsa.dot.gov/analytics/saw.dll?Dashboard report 20140028 - 19395
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.