Category Archives: Oil spill

Kalamazoo River 5 years later – still cleaning it up

Repost from OnEarth Magazine, Natural Resources Defense Council
[Editor:  Significant quote: “The Kalamazoo River still isn’t clean.  Let’s not forget how much it cost to (not completely) clean the Kalamazoo. The current price tag is $1.21 billion (and rising), making it the most expensive onshore oil spill in U.S. history.”  – RS]

Remember the Kalamazoo

Five years ago, a pipeline spilled a million gallons of tar sands crude into a Michigan river—and we’re still cleaning it up.
By Brian Palmer, July 22, 2015
Skimmers, like these used to clean up the Deepwater Horizon spill, were useless in Kalamazoo, where the tar sands crude sank to the bottom. Photo: NOAA

Five years ago, in the middle of the night, an oil pipeline operated by Enbridge ruptured outside of Marshall, Michigan. It took more than 17 hours before the Canadian company finally cut off the flow, but by then, more than a million gallons of tar sands crude had oozed into Talmadge Creek. The oil quickly flowed into the Kalamazoo River, forcing dozens of families to evacuate their homes. Oil spills of that magnitude are always disastrous, but the Kalamazoo event was historically damaging.

The first challenge was the composition of the oil. Fresh tar sands crude looks more like dirt than conventional crude—it’s far too thick to travel through a pipeline.

Try pumping this through a pipeline. Photo: Suncor

To get this crumbly mess to flow, producers thin it out with the liquid constituents of natural gas. Diluted bitumen, or dilbit, as it’s called in the tar sands industry, is approximately three parts tar sands crude, one part natural gas liquids.

When dilbit gushed into Talmadge Creek in 2010, the mixture broke apart. The volatile natural gas liquids vaporized and wafted into the surrounding neighborhoods. The airborne chemicals were so difficult to find and eliminate that Enbridge decided it would be better to simply buy some of the homes that were evacuated, preventing the residents from ever returning.

The tar sands oil, which stayed in the water, presented an even bigger chemistry problem. Most forms of oil, including conventional crude, are less dense than water. That’s why oil makes such pretty colors when dropped into a rain puddle—it floats and plays tricks with the sunlight. Traditional oil spill cleanup technology relies heavily on this density relationship. Skimmers and vacuums remove it from the surface. Floating booms prevent surface-level oil from moving into environmentally sensitive areas.

Tar sands crude behaves differently. “Tar sands bitumen is a low-grade, heavy substance,” says Anthony Swift, director of NRDC’s Canada Project (disclosure). “Unlike conventional crude, when bitumen is released into a water body, it sinks.” (See “Sink or Skim,” onEarth’s infographic on why tar sands oil is more difficult to clean up than conventional crude.)

Skimmers, like these used to clean up the Deepwater Horizon spill, were useless in Kalamazoo, where the tar sands crude sank to the bottom. Photo: NOAA

Put simply, the spilled dilbit traveled in every direction—into the air, with the current, to the bottom of the river—at the same time. The U.S. Environmental Protection Agency’s indisputably naïve response reveals how little anyone knew about tar sands crude. The EPA demanded that Enbridge remove the oil from wetlands surrounding the pipe by August 27, a little more than one month after the spill began. The agency wanted the stuff out of the creek, river, and shorelines by the September 27. Those deadlines would have been practical for a typical spill—but not for a tar sands oil spill. A half-decade later, some of the oil still remains—though, much of that has to do with Enbridge botching the cleanup effort (see onEarth’s three-part series, “The Whistleblower”).

Enbridge’s bungling began even before the spill. First, the company knew the pipeline was vulnerable by 2005, if not earlier. When the rupture finally came in July 2010, operators dismissed the alarms as a malfunction of the system for 17 hours before finally accepting that the pipeline had failed. Making things worse, six hours after Calhoun County residents were complaining to 911 about the smell of oil, Enbridge employees were still trying to fix the problem by pumping additional oil into the pipeline. In its review of the accident, the National Transportation Safety Board faulted Enbridge’s “culture of deviance” for what happened, pointing out that the response team in the first hours consisted of four local pipeline maintenance employees who were inadequately trained and made a series of bad decisions.

Not only did Enbridge fail to make the EPA’s initial cleanup deadline, it also blew through a series of fallback deadlines across more than four years. Not until late 2014 did the agency finally sign off on the remediation effort, handing the remaining responsibilities to the Michigan Department of Environmental Quality.

As the cleanup winds down, though, there is little cause for celebration. “The Kalamazoo River still isn’t clean,” says Swift. “The EPA reached a point where additional cleanup might do more harm than good. Much of the river is still contaminated.”

Some local residents accuse the company of overstating its progress. “In the process of beautifying everything and giving money to everybody and making everybody feel good about it, they’re not really telling people about the dangers still there in that water,” says Linda L. Cypret-Kilbourne of Michigan’s Potawatomi tribe.

It’s not clear when the river will go back to pre-spill quality. After conventional oil spills, crews eventually back off and allow microbes to break down the last bits of crude. That approach isn’t a good option in Kalamazoo. First, the area doesn’t have a large natural population of oil-eating microbes like the Gulf of Mexico has. In addition, tar sands crude contains very high levels of heavy metals, which don’t break down easily.

Let’s not forget how much it cost to (not completely) clean the Kalamazoo. The current price tag is $1.21 billion (and rising), making it the most expensive onshore oil spill in U.S. history.

The Kalamazoo River still isn’t clean. The EPA reached a point where additional cleanup might do more harm than good. Much of the river is still contaminated.

It’s tempting to dismiss the slow, botched, expensive, and still-unfinished cleanup as growing pains. Tar sands imports have risen significantly since 2010, as has public awareness of the difference between the Canadian crude and the conventional product. In the five years since the incident, we should have improved tar sands oil spill response. But we didn’t.

If another Enbridge spill were to happen tomorrow, the company might respond more quickly, but huge volumes of heavy tar sands crude would still pour out of the pipeline. David Holtz of the Michigan chapter of the Sierra Club told reporters that a rupture in Enbridge Line 5, another pipeline that runs through Michigan, would be disastrous.

“If they hit the shutoff valve immediately after a rupture, there would still be more than 650,000 gallons of oil spilled into the Great Lakes,” he said.

Cleaning it up would be as challenging today as it was five years ago. There have been no technological breakthroughs since 2010. The tar sands industry should accept a large portion of the blame for this stasis.

“The efforts to improve spill response have been caught up in a public relations war,” says Swift. “The tar sands industry wants you to believe that oil is oil, and that its product involves no heightened concerns. As a result, spill responders are working with largely the same tools today as in 2010.”

Tar sands pipelines—like the one operated by Enbridge, or TransCanada’s proposed Keystone XL pipeline—run for thousands of miles, crisscrossing the United States and Canada in elaborate networks. They entail certain risks, and those risks are not going away. We have to decide how to respond. If we accept them, we must work to minimize the consequences by developing the appropriate safety measures and technology. Or we can reject them by eliminating tar sands from our energy infrastructure. The one thing we must not do is to pretend they don’t exist. The Kalamazoo spill is a reminder. It won’t be the last.

 

Cause of biggest oil-related spill on land ever in North America – Nexen Energy, Fort McMurray, Alberta

Repost from Reuters
[Editor:  See also:  Nexen pipeline may have been leaking for over two weeks.  Also: Alberta pipelines: 6 major oil spills in recent history.  – RS]

Nexen says may take months to pinpoint cause of Alberta pipeline spill

By Mike De Souza, Jul 22, 2015 6:40pm EDT

FORT MCMURRAY, Alberta  –  Finding the root cause of the oil-sands pipeline leak discovered earlier this month in northern Alberta, one of the biggest oil-related spills on land ever in North America, will likely take months, a senior Nexen Energy executive said on Wednesday. Nexen, a subsidiary of China’s CNOOC Ltd, is putting a higher priority on cleaning up the spill from its pipeline and investigating its cause than on restarting the Kinosis oil sands project where the spill took place, Ron Bailey, Nexen’s senior vice president of Canadian operations, said during a tour of the site.

Bailey said there were about 130 workers doing clean-up and investigation work at the site.

The leak in the double-layer pipeline spilled more than 31,500 barrels of emulsion, a mixture of bitumen, water and sand, onto an area of about 16,000 square meters (172,000 square feet).

“We’ve actually shut in everything at Kinosis and our priority is not to bring Kinosis back on production,” Bailey said. “We will be focusing on understanding the root cause of any failure here and the reliability of our systems before we ever start up this system again.”

The spill site, south of the oil sands hub of Fort McMurray, was detected on July 15 by a contractor walking along the pipeline route. Nexen has not determined when the leak started or why a new state-of-the-art leak detection system failed.

Bailey said leak likely occurred after June 29, when the pipeline was cleaned with water.

Nexen executives on Wednesday brought journalists to tour the site, which smells like tar, and where the company was using sound cannons to deter birds and other wildlife from becoming entangled in the gooey emulsion.

Nexen Chief Executive Fang Zhi personally apologized for the spill on Wednesday, echoing an apology by the company on Friday.

The Nexen leak was larger than the July 2010 rupture of an Enbridge Inc pipeline that spilled an estimated 20,000 barrels of crude, with some reaching Michigan’s Kalamazoo River.

The Nexen spill dealt another blow to the oil sands industry in Alberta, which is under fire from environmental groups and aboriginal communities for its carbon-intensive production process.

Extracting and processing heavy grade oil from the massive oil sands deposits in the Western Canadian province requires large amounts of energy and water.

(With additional writing by Jeffrey Hodgson; Editing by Peter Galloway)

CSX Provides Update on W.Va. Oil Train Derailment Cleanup

Repost from ABC News

CSX Provides Update on W.Va. Oil Train Derailment Cleanup

By JOHN RABY Associated Press, Jul 21, 2015, 7:51 PM ET

GLEN FERRIS, W.Va. – CSX is continuing to closely monitor the environmental impact of a fiery oil-train derailment in southern West Virginia, a spokeswoman said Tuesday.The company held a public informational meeting that drew a sparse turnout Tuesday evening at the Glen Ferris Inn.

On Feb. 16, 27 cars of a CSX train’s 109 cars derailed during a snowstorm in Mount Carbon. Twenty of the cars leaked oil, some of which burned or was released into the ground.

Under a March consent order with the U.S. Environmental Protection Agency, the railroad agreed to a long-term plan for cleaning up and restoring the area around the derailment.

“It’s important for the community to know that we said we would be here,” CSX spokeswoman Melanie Cost said. “This is part of that process. We want to keep the open dialogue for them.”

Donna Shabdue lives near the derailment site and was forced to evacuate her home for more than a day. She showed up to the meeting to voice her concerns about local emergency response and pleaded for quickly informing the public about future incidents.

“They need to have a plan,” she said. “We didn’t know what to do. There needs to be a siren somewhere go off to evacuate. We didn’t know what to do. I just want out of there safely.”

The train was carrying 3 million gallons of Bakken crude and headed to Yorktown, Virginia. In recent years, trains hauling crude from the Bakken region of North Dakota and Montana have been involved in fiery derailments in six states.

The Federal Railroad Administration is investigating the West Virginia accident, which shot fireballs into the sky, burned down a nearby house and caused fires on the ground that smoldered for days.

The cause of the derailment hasn’t been released. Speed had previously been ruled out as a factor. The FRA has said the train was going 33 mph at the time of the crash. The speed limit was 50 mph.

CSX said more than 181,000 gallons of crude oil was recovered after the accident. About 10,000 tons of soil has been removed and shipped for disposal. Additional soil removal is planned next to the Kanawha River and a tributary at the derailment site.

Air, water and soil sampling continues. The water monitoring is at five locations along the river, including a drinking water intake, because of the occasional presence of oil sheens. CSX said the local drinking water supply has been unaffected by the spill.

Oil-absorbing booms were attached to a metal wall more than 410 feet long in the river as an additional containment measure. The wall will eventually be taken down once the sheens are no longer detected, Cost said.

Cost declined to disclose how much the company has spent on the cleanup.

Montana county has had 5 derailments in two years

Repost from The Dickinson Press

Montana county has had 5 derailments in two years

By Amy Dalrymple on Jul 20, 2015 at 11:22 p.m.
An investigator takes photos at the site of a crude oil train derailment on Saturday, July 18 east of Culbertson, Mont. Twenty-two oil tankers derailed, leaking an estimated 35,000 gallons of oil. (FNS Photo by Amy Dalrymple)

CULBERTSON, Mont. — Five train derailments have occurred in less than two years in the northeastern Montana County where crews continue cleaning up after last week’s oil train derailment.

In addition to the two train derailments that occurred last week within a 20-mile stretch of Roosevelt County, two railcars also derailed at Culbertson in February, according to the Federal Railroad Administration database, which is updated through April.

The cause of that incident, which did not cause injuries or release of hazardous material, was attributed to human error, according to information submitted to the FRA.

The area also had two train derailments in 2014, including the derailment of two Amtrak cars in April of that year in the neighboring community of Bainville.

Two people were hurt in the derailment, which caused more than $100,000 in damage to Amtrak equipment and nearly $500,000 in damage to the track, the FRA database shows.

The cause that derailment is listed as “track roadbed settled or soft,” according to information submitted to the FRA.

The other 2014 incident, which involved one railcar that derailed in December at Culbertson, was attributed to a broken wheel, the FRA database shows.

The entire state of Montana had 19 train derailments in 2014, the FRA information shows.

Last Tuesday, nine railcars derailed near Blair, Mont., damaging about 1 mile of track. The cause remains under investigation.

BNSF Railway inspects the track in that area at least four times per week, spokesman Matt Jones said.

The FRA and the Pipeline and Hazardous Materials Safety Administration continued collecting evidence Monday to investigate the cause of Thursday’s derailment involving 22 oil tankers. Four of the derailed tank cars leaked oil, the FRA said, and spilled an estimated 35,000 gallons of oil.

The train was not speeding at the time it derailed, an FRA spokesman said. It was traveling 44 miles per hour in a 45-mph zone, the spokesman said.

BNSF environmental specialists continue to clean up at the site. Oil will be removed from the remaining tank cars in the next several days, and the cars will be removed after that, Jones said.

Crews are excavating contaminated soil, said Daniel Kenney, enforcement specialist with the Montana Department of Environmental Quality, which is monitoring the cleanup. The spill was not reported to have contaminated any water sources and has not threatened human health, Kenney said.

The North Dakota Department of Mineral Resources confirmed Monday that Statoil, the company that owns the oil that was on the train, is in compliance with the state’s oil conditioning order.

The order, which took effect in April, aims to reduce the volatility of Bakken crude oil.

Statoil was meeting the order by operating its equipment at specific temperatures and pressures, said Department of Mineral Resources spokeswoman Alison Ritter. Companies also can comply by submitting vapor pressure tests to the state.

The train with was loaded by Savage Services in Trenton, N.D., and headed to Anacortes, Wash., the FRA said.

Jeff Hymas, a spokesman for Savage Services, said Monday the railcar inspection protocols at the Trenton terminal are consistent with FRA and BNSF requirements.