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

2025-03-29 REPORTS: OK/TX/KS

Joined
Apr 25, 2024
Messages
22
Location
Norman, Oklahoma
I started my day by waiting for four hours in Apache, Oklahoma hoping against the odds for the dryline to fire during the daytime. At around 7:15 PM, I bailed on the southern Oklahoma dryline target to reposition to the forming squall line up north. Unbeknowst to me, the dryline had finally decided to fire near Burkburnett, Texas. Around 9 PM, when I had gotten north of Calumet on my way to Kingfisher, I noticed the cell complex to my south, still struggling to organize but much healthier than the anemic quasi-linear cells to the north. Once I restarted my GPS logger, my situation looked like this:
1743456213038.png
I was originally planning to intercept the Burkburnett cell around Lindsay, hoping that it would wait until then to catch the RM vector and that it would be slow enough for me to be able to get ahead of it. However, the cell split and threw a left mover northwards toward Chickasha. I positioned north of Pocasset and was able to take the following timelapse.

View attachment 20250329-chickashaLeftMover.mp4
1743456212788.png
After the left mover had passed through and the inflow sector crapvection started to rain heavy enough to force me to put the camera in the car, I started to shift east to get the lightning on the back side of the storm. While it flashed frequently, exposed bolts were few and far between, and I pointed my camera west to capture the nighttime structure of the cold front squall line. While I'm happier with that shot on a technical level, it can't quite match the cool factor of the exposed left-moving meso over Chickasha.
View attachment 20250329-roundTwo.mp4

1743456982930.png
 
Back
Top