JamesCaruso
Staff member
I have so many of these, which is either a normal result of chasing 20+ years or is because I just plain suck. I think I am the George Costanza of chasing. If you remember the episode where he recounted all his failings and hard luck in order to win an apartment from an Andrea Doria survivor, this will sound just like that:
Jamestown KS wedge 5/29 2004 - all happy and giddy with a satellite tornado, having fallen behind the main meso that went on to produce a wedge. Maybe I was a bit rusty after being unable to take a 2003 chase vacation.
Hill City KS wedge 6/9 2005 - almost right under a rapidly rotating wall cloud that failed to produce; later saw one tornado from a distance and still later a tornado at Zurich; but much like @Michael Towers post above, I was demoralized after running into Bill Reid and him asking me, “did you see the wedge!?!” Umm...., no...
Quinter KS 2008 - saw the first one emerge from the rain near I-70 but wasn’t in great position on that storm to begin with. Stayed with it too far north and screwed up trying to intercept 2nd Quinter.
Kearney NEB 2008 - was on this storm but somehow failed to stay with the meso, missed the tornado, and ended up trying to outrun and ever-expanding precipitation shield. Maybe in 2008 we were a bit rusty, after being unable to take a chase vacation at all in 2007. (Haven’t missed a year since, although some trips have been short).
Canadian TX 2015 - on my way to a southwest KS target, paused in the Canadian area, liking the sky, liking the data, but stubbornly sticking to my original target, perhaps enticed by SPC products highlighting that area before highlighting the TX panhandle
Dora NM 2015 - was on this storm only by luck, not by targeting; we were simply on our way back to DEN for flights home the next day. But when it looked like it was lining out, we allowed it to just pass over us, only to learn that we somehow missed an almost Campo-like tornado, probably blocked from our view by the rain. This bothers me quite a bit because I’m not even sure how we let this happen and it was salt in the wounds from Canadian when it could have easily been our redemption.
Chapman 2016 - like many, were in the ICT area but we saw this storm go up on radar while en route and could have gone after it. But it seemed ridiculous to go after the first thing that had popped up, then 80+ miles away. If ICT didn’t work out, we stupidly had in our minds the contingency prospect of our first decent sit-down dinner in Wichita after five nights on the road chasing. Probably a bit complacent and less aggressive after Dodge City, figuring nothing could possibly be anywhere near as good as that anyway.
2018 - missed three consecutive tornado days - WY due to bad targeting, CO landspouts due to poor field adjustments along the OFB, and Dodge City by sticking with the supercell in northern OK, influenced by the ICT AFD that seemed to think the greater tornado risk was along the KS/OK border.
The above was in chronological order but I left the worst for last.
The entire last two weeks of May 2013 was one screw-up after another. Missed Rozel by starting in the right area but chasing the first storm up to the north as it turned to crap. Missed Shawnee by sticking to my original target just a bit too far north nearer the triple point in Enid. Missed Moore by heading down toward Duncan and somehow missing the tornado down there too. Completely blew the Bennington forecast and was down in the OK panhandle. Missed a tornado somewhere in northern OK on May 30 because we got stuck in the mud. I know this thread is about missed tornados, but to make my 2013 failure complete I also missed the Nebraska LP because it was 6pm, the skies were still blue, and I had a three hour drive back to Hays where I had already booked a room because it was Memorial Day weekend. And then to cap it all off, I went home on May 31 as scheduled, instead of changing my travel plans to be able to chase El Reno.
Like @Alex Elmore, I don’t get as upset about missing things when I just wasn’t on my chase vacation, but I can’t help wondering if I could have chased Hallam Nebraska in 2004 if I hadn’t pushed my trip back a day in order to attend a church committee meeting, or Bowdle SD if I had flown out on a Friday night instead of feeling obligated to stay at work to help a client with a project that turned out to be aborted anyway... When I finally flew out to DEN on that Saturday, I saw the massive anvil out the window.
Sent from my iPad using Tapatalk
Jamestown KS wedge 5/29 2004 - all happy and giddy with a satellite tornado, having fallen behind the main meso that went on to produce a wedge. Maybe I was a bit rusty after being unable to take a 2003 chase vacation.
Hill City KS wedge 6/9 2005 - almost right under a rapidly rotating wall cloud that failed to produce; later saw one tornado from a distance and still later a tornado at Zurich; but much like @Michael Towers post above, I was demoralized after running into Bill Reid and him asking me, “did you see the wedge!?!” Umm...., no...
Quinter KS 2008 - saw the first one emerge from the rain near I-70 but wasn’t in great position on that storm to begin with. Stayed with it too far north and screwed up trying to intercept 2nd Quinter.
Kearney NEB 2008 - was on this storm but somehow failed to stay with the meso, missed the tornado, and ended up trying to outrun and ever-expanding precipitation shield. Maybe in 2008 we were a bit rusty, after being unable to take a chase vacation at all in 2007. (Haven’t missed a year since, although some trips have been short).
Canadian TX 2015 - on my way to a southwest KS target, paused in the Canadian area, liking the sky, liking the data, but stubbornly sticking to my original target, perhaps enticed by SPC products highlighting that area before highlighting the TX panhandle
Dora NM 2015 - was on this storm only by luck, not by targeting; we were simply on our way back to DEN for flights home the next day. But when it looked like it was lining out, we allowed it to just pass over us, only to learn that we somehow missed an almost Campo-like tornado, probably blocked from our view by the rain. This bothers me quite a bit because I’m not even sure how we let this happen and it was salt in the wounds from Canadian when it could have easily been our redemption.
Chapman 2016 - like many, were in the ICT area but we saw this storm go up on radar while en route and could have gone after it. But it seemed ridiculous to go after the first thing that had popped up, then 80+ miles away. If ICT didn’t work out, we stupidly had in our minds the contingency prospect of our first decent sit-down dinner in Wichita after five nights on the road chasing. Probably a bit complacent and less aggressive after Dodge City, figuring nothing could possibly be anywhere near as good as that anyway.
2018 - missed three consecutive tornado days - WY due to bad targeting, CO landspouts due to poor field adjustments along the OFB, and Dodge City by sticking with the supercell in northern OK, influenced by the ICT AFD that seemed to think the greater tornado risk was along the KS/OK border.
The above was in chronological order but I left the worst for last.
The entire last two weeks of May 2013 was one screw-up after another. Missed Rozel by starting in the right area but chasing the first storm up to the north as it turned to crap. Missed Shawnee by sticking to my original target just a bit too far north nearer the triple point in Enid. Missed Moore by heading down toward Duncan and somehow missing the tornado down there too. Completely blew the Bennington forecast and was down in the OK panhandle. Missed a tornado somewhere in northern OK on May 30 because we got stuck in the mud. I know this thread is about missed tornados, but to make my 2013 failure complete I also missed the Nebraska LP because it was 6pm, the skies were still blue, and I had a three hour drive back to Hays where I had already booked a room because it was Memorial Day weekend. And then to cap it all off, I went home on May 31 as scheduled, instead of changing my travel plans to be able to chase El Reno.
Like @Alex Elmore, I don’t get as upset about missing things when I just wasn’t on my chase vacation, but I can’t help wondering if I could have chased Hallam Nebraska in 2004 if I hadn’t pushed my trip back a day in order to attend a church committee meeting, or Bowdle SD if I had flown out on a Friday night instead of feeling obligated to stay at work to help a client with a project that turned out to be aborted anyway... When I finally flew out to DEN on that Saturday, I saw the massive anvil out the window.
Sent from my iPad using Tapatalk
Last edited: