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

3/27/08 NOW: OK

cedwards

EF5
Joined
Feb 3, 2005
Messages
556
Location
Shawnee, OK
The storm in Muscogee county has a nice hook and couplet on it. It is now tornado warned. I suspect that it is being undercut by the front. I have been watching the towers going up from my back yard. I have a little timelapse of the towers early on.
 
Two tornado warned cells in Missouri. One in in Pulaski county has a MAJOR hook on it and a nice couplet just north of Lebanon. Hail also up to baseballs are possible according to the warning text. The other is near St. James, MO north of Rolla which also has a nice flying eagle shape to it. Dewpoints aren't great in this area so very surprised to this going on, but we are talking about SW Missouri lol.
 
Confirmed "dangerous tornado" near Council Hill, OK! Only moving at 20mph. This is so crazy!! I hate when this happens. I hope this doesn't head toward any towns because it sounds like a mean storm.
 
Those cells in MO. were showing high reflectivity too..a composite shot showed a 77 south of Eagle Springs recently with VILs in the 65+ area..this with consistent rotation in many cells showing hooks..Spring is in force there with 30s in north and 70s south in MO.
 
Looks like the three cells in Dent, Texas and Crawford are about to merge.
Correction: last radar loop shows they have merged.

Anyone look at Ottawa co in NE OK? Last loop there was nothing there and proof is almost at warning level.
 
Last edited by a moderator:
I'm trying to figure out why we didn't get a squall line almost instantly upon initiation. My current theory is that there was a sweet balance between the CAP and the amount of dynamic forcing ahead of the cold front. In Missouri a meso-low being picked up on sfc obs definitely had a lot to do with added low-level helicity. Regardless, i'm trying to figure out why the SPC/NWS offices have not gone with tornado watches when it was obvious they should have (this isn't the first time this spring.) If I see great shearing with height and the potential for the CAP to be busted I'm going tornado watch whether it verifies or not. A false alarm is one thing, but a miss is a complete different story.
 
I'm trying to figure out why we didn't get a squall line almost instantly upon initiation. My current theory is that there was a sweet balance between the CAP and the amount of dynamic forcing ahead of the cold front. In Missouri a meso-low being picked up on sfc obs definitely had a lot to do with added low-level helicity. Regardless, i'm trying to figure out why the SPC/NWS offices have not gone with tornado watches when it was obvious they should have (this isn't the first time this spring.) If I see great shearing with height and the potential for the CAP to be busted I'm going tornado watch whether it verifies or not. A false alarm is one thing, but a miss is a complete different story.

The "shape" of this frontal zone isn't much different than that from Monday of last week (in northern TX, a front that undercut all warm-sector storms). However, I think the weaker and more veered mid-level flow in this case may be aiding the discrete mode. Instead of the storms being moved beyond the surface cold front (i.e. rearward relative to the front), the cells today are able to stay ahead of the cold front long enough for vertical perturbation pressure gradients to become established, and long enough for said forcing to turn the cells to the right. If the mid-level flow were to be more backed and/or stronger, the storms may have been advected to the northeast more quickly, and they may have ended up being undercut by the front. In addition, flow near the equilibrium level is quite a bit weaker than 3-17-08, so there may be less significant seeding occuring. This is starting to veer into a DISC (more post-storm) type, so I'll stop here.

Oh yeah, forecast and analyzed instability from far NE OK into MO was relatively marginal. The 00z SGF sounding show significantly more CAPE than forecast, but that's a bit of hindsight. Given that we should see some near-surface stabilization soon, I'm not sure it would have been prudent for the SPC to replace a recently issued SVR box with a new Tor box if the tornado thread isn't expected to persist more than a couple of hours. Current RUC analysis shows very significant surface-based CINH and relatively meager sbCAPE. So, between the time the 00z SGF sounding came in and the time the current supercell will lose their surface-based "feed" may not be more than a couple of hours. The tornado threat didn't really look significant enough to warrant a Tor box, IMO.

FWIW, the SVR box did have 20% prob of "2 or more tornadoes", so the SPC did address the possibility of one or two tornadoes (in the probs and in a mesoscale discussion issue to discuss the status of the watch).
 
FWIW, the SVR box did have 20% prob of "2 or more tornadoes", so the SPC did address the possibility of one or two tornadoes (in the probs and in a mesoscale discussion issue to discuss the status of the watch).

That's exactly why we include probabilistic information with our forecasts - to express the uncertainty. I don't think 4 tornadoes and many more TOR warnings were the specific expectation today, but that doesn't mean that tornadoes were ruled out.

The possibility of supercells suggests a non-zero tornado threat. Supercells were mentioned in the text discussion of the first SVR TSTM watch, but I don't think you'd be that happy with everything becoming a TOR watch based on small probabilities.

Rich T.

p.s. The multi-year average is for 20% of SVR TSTM watches to verify with 2+ tornadoes.
 
FWIW, the SVR box did have 20% prob of "2 or more tornadoes", so the SPC did address the possibility of one or two tornadoes (in the probs and in a mesoscale discussion issue to discuss the status of the watch).

This comment may be more DISC:

Yeah as I understand it, the nature of the severe weather has to show an environment somewhat conducive and likely to form tornadoes in order to justify a Torn box. Otherwise severe and let NWS make the call on the warnings as they occur. If the environment changes or enough reasonable torns / torn warnings are produced then can upgrade to a Tornado box - assuming as Jeff mentions the situation will remain favorable to production of possible tornadoes.
 
Back
Top