Monday, September 17, 2018

Hail, Columbia, the “gem” of the natural gas providers

There is natural gas in this building – it powers the communal dryer and water heater – but I don’t have any in my unit. I considered getting the gasline extended into my kitchen when I reno’d a few years back, but decided against. Gas is certainly easier to cook on than electric, but I opted for the Euro-modern induction cooktop. I like it just fine. And I don’t have to worry about whether the guys who extended the gasline into my unit knew what they were doing.

Growing up, our home’s heating and cooking was gas-fueled, as was an apparatus (I believe it was called a calcinator) in the basement that burned paper trash (installed after Worcester outlawed burning trash in a barrel in your backyard).

Anyway, other than a vague worry about whether the line from Point A to Point B was put in right – which I really never had to worry about, since I chose not to us gas – I’m all for natural gas.

Oh, I see periodic signs around town that a gas leak has been detected. And the Dig Safe ads on TV.

But I don’t tend to sit around thinking that natural gas, while clear and present, is a clear and present danger.

Then, last week, there was a series of explosions in Lawrence, Massachusetts and a couple of its suburbs. Dozens of houses burnt down, thousands of people were evacuated, and one teenage boy lost his life while sitting in a car. (The chimney of an exploding house fell on the car.)

I had never heard of the company that was responsible for the gas pipes that went boom. I thought Eversource and National Grid were pretty much “it” for energy providers around here. But here they are, Columbia Gas of Massachusetts, now a household word.

They’re no secret, however, to state regulators. The company:

…has been fined tens of thousands of dollars by the state’s utilities regulator in recent years, and its corporate parent linked to serious blasts in at least two other states.

Since 2010, the Massachusetts Department of Public Utilities has fined Columbia Gas for safety violations that included faulty pressure testing and response procedures, insufficiently covering new service lines, improperly classifying leaks, and breaking rules around the use of leak repair kits.

The state agency found Columbia Gas was slow to respond to a 2012 Seekonk fire fueled by a broken gas pipe, and ordered the company to update its emergency response plans and develop new training programs.(Source: Boston Globe)

They were also responsible for a major explosion in Springfield a few years back in which 18 people were injured.

In that incident, a company worker investigating a gas odor at a downtown nightclub accidentally punctured a high-pressure gas line, triggering an explosion that leveled the building and damaged dozens of others, authorities said.

“It felt like a bomb fell in front of the building,” a neighbor told the Globe at the time.

The Massachusetts state fire marshal determined the Columbia Gas worker relied on incorrect sidewalk markings for the gas line’s location. The company reached an $850,000 settlement with the city and paid millions of dollars to settle other claims and lawsuits.

Indiana-based NiSource is Columbia Gas’ parent company. The day after the Lawrence explosions, their stock tumbled 12 percent in anticipation that the company would be on the hook for major settlements.

Columbia doesn’t sound like a gem, to say the least, but they have apparently been trying to upgrade aging gas infrastructure for the last few years, complying with federal and state regulations (which, contrary to some thinking, really are necessary and vital to our existence).

Trouble is, they and other gas companies may have been in too much of a rush, hiring people to fast-track fixes but not adequately training them.

Our governor isn’t placing much trust in Columbia. He put Eversource in charge of the recovery in Lawrence.

Conspiracy theorists have been speculating that hackers may have caused the explosions by jiggering around with gas pressure monitors and gauges which, thanks to the Internet of Things, are all connected to the outside, hacking world. But I’m guessing the problem is plain old aging infrastructure combined with human error.

We’ll see what the investigation into this one turns up. But it won’t be pretty. And it’s going to cost Columbia plenty. Wouldn’t want to be on their management team, that’s for sure.

No comments: