Exxon Mobil pipeline leaks 'a few thousand' barrels of crude oil in Arkansas
By The Washington Post
Published: Sunday, March 31, 2013, 7:57 p.m.
Exxon Mobil said that one of its pipelines leaked “a few thousand” barrels of crude oil near Mayflower, Ark., prompting the evacuation of 22 homes and reinforcing concerns many critics have raised about the Keystone XL pipeline that is still awaiting approval from the State Department.
The Exxon Mobil pipeline breach took place late Friday, the company said, in the 20-inch diameter, 95,000-barrel-a-day Pegasus pipeline, which originates in Patoka, Ill., and carries crude oil to the Texas gulf coast, the country's main refining center. Mayflower is about 25 miles north of Little Rock.
The pipeline, which was built in the 1940s and recently expanded, was carrying low-quality Wabasca Heavy crude oil from Alberta, said Exxon Mobil spokesman Alan T. Jeffers. According to the authoritative Crude Monitor website, Wabasca Heavy is a blend of oil produced in the Athabasca region where the oil sands are located.
An existing Keystone pipeline carries crude oil that comes from the oil sands deposits in Alberta to Patoka, though Exxon Mobil's Jeffers said he did not know if this batch of crude oil came from the Keystone line.
Many critics of the Keystone pipelines say that corrosion risks are greater in pipelines carrying low-quality, bitumen-laden crude from the oil sands.
“This latest pipeline incident is a troubling reminder that oil companies still have not proven that they can safely transport Canadian tar sands oil across the United States without creating risks to our citizens and our environment,” said Rep. Edward J. Markey, D-Mass., who sits on the Natural Resources Committee.
TransCanada, owner of the Keystone pipeline system, has said that the new pipeline would be far safer than any other part of the nation's 2.6 million miles of oil, gas and chemical pipelines.
The Environmental Protection Agency declared the Arkansas leak a “major spill,” a label put on any spill of 250 barrels or more.
Exxon Mobil said it was preparing for a spill of up to 10,000 barrels, though it said that the spill estimate was likely to end up lower than that.
The company and other responders were battling to keep the crude oil, which leaked onto land in a Mayflower neighborhood, from leaking into the nearby Lake Conway, a popular game fishing spot.
Cleanup crews have deployed 3,600 feet of boom near the lake as a precaution, but as of Sunday afternoon no oil had reached the lake, Jeffers said.
Dikes had been built to prevent runoff into the lake, but heavy rains were making that difficult and runoff from storm drains into the lake were a concern, he added.
The company received phone calls from people in the area at the same time its pipeline monitors in Houston noticed a drop in pressure in the line, Jeffers said. The pipeline is buried about two feet deep in the Mayflower area, he said.
Exxon Mobil said responders were on the scene within a half hour.
The company said the cause of the spill was still under investigation.
Show commenting policy
TribLive commenting policy
You are solely responsible for your comments and by using TribLive.com you agree to our Terms of Service.
We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.
While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.
We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers.
We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.
We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.
We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.
We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.
- Obama, House Republicans trade accusations in thwarting immigration reform
- Denver wife killed 12 minutes into 911 call, sparking inquiry
- AC/DC not disbanding, lead singer Brian Johnson says
- 1986 Warhol self-portraits up for sale
- US Airways’ pornographic tweet won’t cost anyone a job
- Vermont Senate OKs GMO labels as industry insists genetically modified crops are safe
- Tea Party flap averted fraud probe by IRS, Justice, emails show
- Android systems running 4.1.1 softward carry Heartbleed bug
- Brutal CIA tactics deemed ‘valuable’ despite findings of leaked Senate report
- ‘Godfather’ of runaway salaries for elected officials sentenced in California
- Hoax bomb case causes concerns in Boston