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

Hindsight - Nov 5 OK/KS storms

  • Thread starter Thread starter Phil Moyer
  • Start date Start date

Phil Moyer

I have a couple of newbie questions after yesterday evening's excitement.

First, people were calling the Oklahoma City-Ponca City-Arkansas City corridor on the evening of the 4th, well in advance of the SPC moderate risk update or MS discussions. What analysis factors caused you to pick that five or six county region so accurately? Was it data-driven or instinct driven? Were you looking at NAM Skew-T predictions, other model output, current observations? What differentiated those specific areas from adjacent areas that (correctly) didn't look as promising?

Second, at 1445 Central, the Oklahoma City WSR-88D was painting two nice targets: a large cell west of town, a little south of I-40, and a smaller cell just SW of Ponca City. The western cell, which became the Guthrie storm, was larger, had higher reflectivity, had earlier rotation, had a nice wall cloud - but the northern storm developed more rapidly and was tornado warned first. Why? What were the characteristics (or, "were there characteristics...) of the two storms that altered the development speed? Were there data sources that those of us 1,500 miles away should have been looking at to more accurately predict tornadogenesis?

I know these are pretty basic "understanding" level questions, so I apologize for not being up to speed....

Phil
 
I'd highly recommend in the future joining the chatroom - there were boatloads of chasers / mets / radar experts in there, as these types of questions are MUCH easier to answer in realtime vs trying to go back and figure out what we were saying and why.
 
Phil,

I think a lot of people were eyeballing areas from Wichita to Oklahoma City in the afternoon as this area had the best combination of instability and shear indicated on the forecast models. Given that the low level shear was forecasted to ramp up in the evening, I take it people were looking for a target a bit further east where storms/dryline/front would be after initiation. Ponca City is east and in between the two other cities, and has decent highways coming in and out of it.

As for the tornado warning. I believe the text said doppler radar indicated capable of producing a tornado. The NWS met must have seen more pronounced rotation in that cell at the time.
 
Phil- as far as forecasting goes, read and study as much as you can. There are TONS of free resources around the web, you just have to know where to look. Haby's Hints are a great place to start. Until you develop those skills, a good litmus test for where tornadoes are possible is the EHI forecast parameter available on some model websites. EHI= [Energy (CAPE) x Helicity] / 160,000. You need both CAPE and helicity for tornadoes and if either = 0, the output is 0.
 
As far as my target, I was OKC/I-40 and south all the way, because my morning analysis/observations were confirming what the rapid model output was advertising. The SPC's "forecast tools" page is solid gold IMO, that's the one site I lock onto in the waning hours before I leave. It only updates once an hour, but the parameters measured are invaluable to assessing real-time situations and in turn, using those obs over the course of a few hours in the morning to try and identify trends. It was becoming quite obvious that there were two target regions in the meat of the SPC outlook, which was OKC and southwest, and NC to NE Oklahoma. I'm always about thermodynamics first, shear second, so I chose the area I felt would have the greatest instability prior to initiation. I had a feeling those who went to the OK/KS border would have good storms as well, but, along with the greater instability factor, I figured the storms south of I-40 would move a bit slower, as they would be further away from the influence of the main jet core.

As for why one storm was tornado warned and one wasn't, that's why we're doing all the research :)
 
I'd highly recommend in the future joining the chatroom - there were boatloads of chasers / mets / radar experts in there, as these types of questions are MUCH easier to answer in realtime vs trying to go back and figure out what we were saying and why.

Sorry to have to ask this, but where is the chatroom located? Is this something that is only available during events?
 
The parameters I mainly look at for my forecasting are surface temps, dewpoints, theta-e, and wind speeds from the surface up to 500mb. These parameters will let you find any boundaries, how much surface moisture is available, how much shear you have, and storm motion and speed. CAPE is also good to see how much instability is available (but you have to keep in mind that fall, winter, and early spring storms can get the job done with much less CAPE than late spring storms). I tend to not pay much attention to the models until about 48 hours out (since I hate working with the GFS...it seems to almost always be too aggressive).

The main thing that caught my eye with the models was that the WRF picked up on precip initiation in central OK south of the OKC metro between 18 and 0Z, and it persisted on several runs. It didn't break out precip further north until 0Z, which would have been after dark. This was one of the few times I based my forecast purely on the models, since I felt like the boundaries (and particularly the dryline) would hold back until well after dark...and I wanted daylight storms to go after.
 
Even though I wasn't going to chase this event I still like to try my own at forecasting. The forecast skew-T's and model runs drew my attention to Ponca City due to the amount of shear and instability that was forecast to be in that area. The actual day of the event is when I rely heavily on surface obs and satellite images along with RUC guidance to try and help me better pinpoint an area. Although I still trusted this target, as the actual events of the day unfolded and seeing the sharp dryline approach from the West I started looking more to the SW for initiation, being that it would probably start before dark and with the daytime heating and instability this area would probably fire first but felt better about NE OK for possible tornadoes.
 
Back
Top