• 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.

2019-05-28 EVENT: IA/IL/KS/MO/OK/TX

Ethan Schisler said:
I didn't chase the main target area on this event, due to having surgery the next day (I ended up doing some backyard chasing in IL that afternoon/evening). I had wondered this ever since this event and I'm not sure if this is the place to post it, but I wondered why NWS Wichita and Hastings have the Waldo-Lurray-Tipton tornado event listed as one single long track EF-2 tornado and don't mention any satellites or the fact that from the videos I've seen there were two primary tornadoes (The Waldo tornado that Adam Lucio has awesome video o along with Devin Pitts; which occluded and had a satellite), and then another large tornado that formed northeast and moved toward Tipton, KS that Pecos Hank and Skip Talbot videographed. It even appeared from their vantage point there were 3 tornadoes on the ground at once near Tipton, KS which struck me as rather extraordinary, especially how the far left vortex arced out of the main wall cloud and kinked around.

View attachment 22365

This is the piece written on the setup by NWS Hastings, along with the track map to go along with that.

View attachment 22366

Again I didn't chase this so I don't have any material of my own to contribute (maybe others can step in), but I've never seen a multiple tornado producing supercell like this get recorded in the NCDC storm data as a single long track tornado (in modern times, 2010+).. Just seems like the wrong way to document it. I had wondered this for over 2 years now and just thought if anyone else had any ideas the thinking behind this. Thanks!
Click to expand...
I don't know why this tornado was poorly surveyed to be honest
 
You must log in or register to reply here.

Similar threads

Jeff Duda
2024-05-21 EVENT: IA/IL/MO/KS/OK/AR
2 3
Replies
35
Views
3K
Jason N
Jason N
Blake Naftel
2024-05-07 EVENT: IN/OH/MI/IL/KY
Replies
14
Views
1K
Dan Robinson
Dan Robinson
2024-05-26 EVENT: AR/MO/IL/TN/IN/KY
2
Replies
21
Views
2K
Dan Robinson
Dan Robinson
Randy Jennings
2024-03-14 EVENT: TX/OK/AR/MO/IL
Replies
11
Views
1K
Randy Jennings
Randy Jennings
Blake Naftel
2024-05-26 EVENT: IL/IN/MI/OH/KY/IA/MO
Replies
0
Views
379
Blake Naftel
Blake Naftel
Back
Top