This week's setups have turned out to be eminently Plains-trip worthy, and were it not for the copyright-infringement issue, I'd have departed Wednesday evening and would already be out on the first trip of the season. Thursday's event was one or the ages, with two high-caliber tornado producing storms in northern Oklahoma.
Another pair of classic Plains supercell tornado days looks to be on tap for today (Saturday) and tomorrow (Sunday) before the ejecting wave brings the final events of the sequence to the Midwest on Monday and Tuesday:
NAM 500mb forecast for 7pm Monday evening
I'm currently working a short period of midnight shifts, and Sunday's event looks to have become too far west to safely make it in time from a 7am Sunday morning departure from St. Louis. That leaves Monday and Tuesday as the only events of this sequence I'll be able to chase.
While the model depictions of Monday's event check all of the boxes in the tornado department, even indicating outbreak potential: strong instability, good lapse rates and low level/deep layer shear - it is relatively common for these to be rather fragile and sensitive to any number of failure modes that crop up at the last minute (usually early-day storms and cloud cover are issues with such a strong jet core).
After Tuesday, medium-range models agree on the pattern shutting down as cold fronts scour the moisture down into the Gulf. Moisture is shown attempting a return around May 5, at which time we'll go back to watching things more closely.
Again, to maintain consistency with previous years' Plains trip probability tables, I'm plotting the chances for a trip as if I still had the resources to maintain my previous levels of operation. For this current system, the table will show 100%, as it would have been trip-worthy in a normal year (in fact a trip would already be in progress as we speak). Again, this is just to illustrate the impacts of copyright-infringement on my storm chasing operation.
The following table plots the probabilities* of a Great Plains chase expedition taking place for the date ranges shown:
2026 Plains Chase Expeditions - Probabilities as of April 25*
April 25-26
100%
April 27-May 4
2%
*Base/normal-season probability values are shown. Subtract 35 to 45 percentage points for effectivecopyright-infringement imposed probability values.
My work is, at this very moment you are reading this, generating the most income it ever has in my career. Yet, I was forced to shut down the professional side of my successul operation, against my will, due to one cause alone: 95% of that revenue is being stolen by piracy and copyright infringement. I've lost more than $1 million to copyright infringement in the last 15 years, and it's finally brought an end to my professional storm chasing operation. Do not be misled by the lies of infringers, anti-copyright activists and organized piracy cartels. This page is a detailed, evidenced account of my battle I had to undertake to just barely stay in business, and eventually could not overcome. It's a problem faced by all of my colleagues and most other creators in the field.
Web Site Design and Internet Marketing by CIS Internet
From Dan: Please Read
To my regular readers, I offer my apologies for this heavy-handed notice. Unfortunately it has become necessary, so please bear with me!
Please don't copy/upload this site's content to social media or other web sites. Those copies have been a critical problem for me, seriously harming this site and my photography/storm chasing operation by diverting traffic, viewers, engagement and income. "Credit" and "exposure" does not benefit this site or my operation, rather they threaten my ability to cover my operating expenses. Please read my full explanation for this notice here.
Before continuing, check each box to agree to and acknowledge these two statements:
Click this button to finalize this acknowledgement:
This chase was a routine television assignment in my role as a cameraman. As a result, many of these don't have a dedicated chase log.
This chase was only recorded in my mileage reports, no detailed log was written for it.
