• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

Another Strong, And Unwarned, Tornado: North Carolina

Joined
Feb 19, 2021
Messages
790
Location
Wichita
This is from this afternoon. It is just incredible that this keeps happening! It has been upgraded to EF-3 and it destroyed 50,000 pallets of medicine at a Pfizer plant that heavily damaged.

As always, I'm open for questions and comments.
 
Last edited:
If I am reading it right, the report of the tornado went out at 1:27 with the listed time of the tornado as 12:37. So they may NOT have known the tornado was on the ground before they issued the warning. That said, I would certainly agree with you based on the radar images that the warning should have been issued sooner than it was.
 
If I am reading it right, the report of the tornado went out at 1:27 with the listed time of the tornado as 12:37. So they may NOT have known the tornado was on the ground before they issued the warning. That said, I would certainly agree with you based on the radar images that the warning should have been issued sooner than it was.

John, you have a point. I'm going to delete that portion of my essay to be fair to the Raleigh NWS.

That said, it is nearly impossible to believe it took them more than an hour to confirm there had been a tornado! What do these people do all day??
 
I looks to me like Tor Warning #6 was issued at 12:31 EDT, the LSR was at 12:37 EDT (although may have not been entered until later), and they updated Tor Waning #6 at 12:37 EDT to say it was observed and law enforcement confirmed. Survey does say it started about 12:25 EDT, so it is true that the first 6 minutes was unwarned.
 
I looks to me like Tor Warning #6 was issued at 12:31 EDT, the LSR was at 12:37 EDT (although may have not been entered until later), and they updated Tor Waning #6 at 12:37 EDT to say it was observed and law enforcement confirmed. Survey does say it started about 12:25 EDT, so it is true that the first 6 minutes was unwarned.

Randy, I haven't seen the survey. It has not been posted on Twitter nor do I see it on their web site. Can you forward a link?
 
I really like this gentleman's youtube channel. He does a good job breaking down the event.

Cameron Nixon’s paper about MCV tornadoes referenced in the video:

 
Back
Top