4 ms·
It should be obvious that the text from the KPAH tweet at 7:03 is not your run-of-the-mill SVR warning or TOR watch (which aren’t issued by tweet, anyway). It w
by cbfrench 5y ago
It should be obvious that the text from the KPAH tweet at 7:03 is not your run-of-the-mill SVR warning or TOR watch (which aren’t issued by tweet, anyway). It was a very clear alert that a storm that had already produced a visibly-confirmed and dangerous tornado was heading toward that location. NWS offices don’t tweet out that kind of language that far in advance unless they are certain about it. They weren’t going to trigger an actual warning at that point, as there was still time for the storm to lift or dissipate, but when they finally did trigger the PDS warning for Mayfield[0] at 9:05, it had been clearly signaled beforehand that that storm was on the way and that it was serious.
So, no, local authorities aren’t going to sound the sirens based on a tweet over two hours in advance of an event (nor was anyone suggesting they should have done), but emergency managers should have been well aware in advance of the first warning issuance that a very dangerous tornado was on its way.
[0] https://mesonet.agron.iastate.edu/vtec/#2021-O-NEW-KPAH-TO-W-0036/USCOMP-N0Q-202112110305 https://mesonet.agron.iastate.edu/vtec/#2021-O-NEW-KPAH-TO-W...
- cbfrench 5y agoIt was pointed out to me above that the 2.5 hour figure is spurious. (Cliff Mass apparently didn’t account for the fact that time stamps on tweets display the time of the tweet in the reader’s local time zone, not in the OP’s—or OT’s in this case.) So, NWS Paducah tweeted that alert at 9:03 CST, effectively contemporaneous with their issuance of the PDS warning. Still a pretty good lead time for a TOR warning, but nothing like hours of notice. In any case, I stand corrected on that.