Tag: Meriden

It was clear, early on, that Friday had a significant chance for severe weather. I was concerned that the computer models downplayed it somewhat. But Thursday, within a few hours of being run, they had already blown the forecast in Michigan… so the computers weren’t to be totally trusted.

A little activity started on Central New York State toward early afternoon and the Storm Prediction Center threw up a Severe Thunderstorm Watch for the entire state, effective until 8:00 PM.

That was the right call.

A little background. I forecast the weather. The folks I work with forecast the weather. My competitors forecast the weather. But, we all leave watches and warnings to the Weather Service. The idea is to present a coordinated front, so as not to be confusing. In my 20+ years in weather I have heard few dissent from this concept.

After a watch is posted, it is the job of the Taunton, MA National Weather Service Office to put out a ‘redefining’ statement for all of Connecticut (even though they normally only forecast for 3 of the 4 northern counties and none of the shoreline). These are needed because watches are parallelograms and they don’t evenly fit within state or county borders. Without the redefinition, a watch area might include a small sliver of a state or something else equally confusing.

Taunton’s original statement only included their counties.

Then a correction to include the whole state.

But, by then the damage had been done. At the TV station our Weather Warn II computer was confused. It put up a Thunderstorm Watch and then alternated text for a “defined area” and mentioned the three original counties. If we would have aired it, it would have looked like the watch was only for three counties.

As I drove in, Kirk Varner, our news director (who reads this, I can’t blast him here), saw what was going on and basically shifted to manual. This system is supposed to work on its own, without intervention. At the moment, it can’t be trusted. But, thankfully, we had the right info on the screen.

Throughout the afternoon we saw scattered thunderstorms. They probably didn’t get to the ‘official’ severe limit, but were close enough to justify the watch box.

Thursday night, this same system had quieted down and then, with the watches expired, fired up. It even spawned tornadoes in Michigan on the ‘rebound.’

Tonight, the system again died down. And then a series of awful human judgment errors.

At 7:10 PM:

But, the threat hadn’t ended. All of a sudden, in Southern Windham County, the storms fired up rapidly and ferociously.

But, in Connecticut, these storms weren’t just over Windham County. They had crossed the border to New London County. In fact, by the time the warning went up, Northern New London County was seeing more action than Windham.

Windham County gets its warnings from Taunton, MA. New London County gets them from Upton, NY. No warning went up for New London County.

If there was reason for warning Windham County, there was reason for a warning to be issued for New London. This lack of coordination is a problem we face a few times a year, at the least.

At 7:51 PM, the watch and warning configuration in Connecticut was out of whack with what was actually happening. This system is supposed prepare and inform. It was confusing.

Thunderstorms continued, though weaker, until sometime past 10:00. Saturday will be a totally different weather animal – cooler and fresher.

I am not happy with what went on Friday. In many ways, I am powerless to change things unless I start ‘buying out’ of the unified watch and warning scenario.

I don’t think I’m ready for that… but I’m close.

——-

By the way, at 4:21 PM the dew point a Meriden, CT (KMMK) reached an unbelievable 79°! I can’t ever remember seeing a dew point that high in Connecticut.