Bob Schafer
EF5
WHOA!
Where was that?
I guess that is not a pic you took, Scott, based on the URL?
Bob
Where was that?
I guess that is not a pic you took, Scott, based on the URL?
Bob
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.
It wasn't a synoptically obvious event, but you don't ignore >6000 CAPE w/ 100kt@H250, 50kt@H500, 40kt@H700 events, even if it is unidirectional. Surface winds were progged to be southwesterly but ended up being more southerly.
Reviewing the synoptic setup, I am still astounded that such a strong tornado formed. Based on the CAPS analysis from 2 pm, there really is nothing on the synoptic scale that would suggest that strong tornadic supercells would form. I think it is very likely that this event was driven by the all-too-familiar extreme CAPE/low level boundary combo. The storms moved very far to the right of the mean flow, muck like the Jarrell, Texas storm of 1997. I am sure someone will do a case study...should be interesting.
Gabe
I agree that the situation WAS very synoptically evident. SPC did a good job with the event, although they were playing it safe with their 5 % given the non-Oklahoma classic textbook setup. I didn't look at the radar data in detail, but I ask those whom were: was this storm playing along an outflow boundary from an earlier supercell? Nonetheless, the hodograph supported decent helicity, definitely contained adequate supercell shear, and the CAPE was tremendous, making this an obvious eye-opening day for the forecaster.
Here's the official damage report. -- F4 rating
http://www.crh.noaa.gov/ilx/events/jul132004/jul13.php
With the right boundary in the right place at the right time, I wouldn't have been suprised to have seen an even more historic vortex.
Chris
It wasn't 'obvious' that a 6hr discrete supercell with a violent tornado would occur synoptically, at least the night before.