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

2024-06-01 REPORTS: TX

JamesCaruso

Staff member
Joined
Jul 5, 2009
Messages
1,876
Location
Newtown, Pennsylvania
Still catching up on 2024 chase reports. This particular Saturday's target was the Fort Stockton area. I have always had an aversion to going down there, and can't remember the last time I did. It's a no-man's land, with a very limited road network, and it's at the extreme southwestern edge of typical chase territory. But with activity - and therefore our trip - winding down, and the next day's target likely to be in the Lubbock area, I decided to go for it. After all, how many times do we see on radar a rogue isolated supercell chugging along down there?

My son and I ended up really enjoying the day! I think my anti-Fort Stockton bias is gone! Sure, it's not a place where you have much hope of getting close to a tornado if that's your thing, but there are plenty of opportunities for structure shots over interesting landscapes.

We arrived in Fort Stockton early and sat for a couple of hours in a gas stop parking lot right off the I-70 interchange. When the first couple of cells formed, we drifted west on I-70 and then south on route 67. We stopped to let the northern cell drift toward us.

IMG_2293.jpeg

Then we shifted south a bit to this location, and a TOR warning was issued shortly thereafter. The tiny polygon is because the storm was moving only 5 mph.

IMG_2295.jpeg

IMG_2297.jpeg

The forward flank of the storm coming up from the southwest overtook our meso, which I expected would be only a matter of time. We dropped further south for a look at this other storm.

IMG_2298.jpeg


IMG_2299.jpeg

Eventually this storm crossed route 67, and this is where the lack of roads hurt. We had to go all the way down to route 90 before we were able to go east, and it was at this time that the storm was TOR-warned in the road void between 90, 67, 385 and I-70.

IMG_2300.png

Once in Marathon, we watched new development to the south of the previous storm.

IMG_2301.jpeg

It was shortly after 7pm CDT, and I decided to call the chase at this point. I wanted to get back to Odessa, which is normally a 2-hour drive, but the storms were blocking 385 north out of Marathon, so I would have to go east to Sanderson and then up 285 (a 3-hour drive), or west back to 67 and then north (a 2.5-hour drive). I am often torn between staying on a storm until dark "just in case" something happens, and wanting to get a decent sit-down dinner. Given how things were looking, and also considering that the hail core was already getting pretty to close to the east road we would need to use to stay with the storm, dinner won.

Seven minutes after heading back west, we had just gotten through Marathon when I took another look at the radar. Velocity showed that the meso had ramped up, so I instantly began to second-guess my decision. But at this point I would have had even less of a chance to go east on 90 without the hail core impacting it. It also occurred to me that, with the MAF radar nearly 130 miles away, the velocity scan was probably looking at a higher-altitude slice of the storm, so the radar image was not a fair representation of surface winds (correct me if I'm wrong on that!)

Continuing west toward 67, we scored a nice rainbow and a great landscape/skyscape combo with side-lighting on falling hail.

IMG_2302.jpeg

On the way home, on 67 behind the storms, I noticed donut holes on reflectivity, co-located with 60k feet tops. I started to again regret that maybe I had bailed too soon, but at this point the storm was over route 90 anyway.

IMG_2303.png

And yes, we did get that nice dinner, at Cork & Pig in Odessa, open until 11pm on Saturday nights! ;)
 
Back
Top