The El Reno Tornado of May 31st, 2013
I was in the field that day about 40 miles southwest of the actual tornado. I saw data I didn't expect and spent the next six months trying to explain it to people who weren't there. The storm didn't behave like any textbook case. That's the honest takeaway from studying this event properly. The tornado formed around 6:03 PM CDT near Highway 81 and Reinhardt Road, roughly ten miles west-southwest of El Reno, Oklahoma. It developed from a rapidly intensifying supercell that had already spawned a smaller tornado to its east. What happened next was not predictable by any existing model. The primary measurement came from the DOW network. The Doppler on Wheels radar, positioned near the intersection of Highway 81 and State Highway 9, captured a velocity couplet indicating winds of 301 mph at approximately 100 meters above ground level. That is 484 kilometers per hour. These readings came from the N0R radar at Norman and the WSR-88D network, cross-referenced with mobile DOW data. The National Weather Service in Norman initially classified it as an EF5, though the official rating was eventually revised down to EF3 because damage indicators didn't support the higher category. This discrepancy between measured wind speeds and actual surface damage became one of the most discussed problems in modern tornado meteorology.
Here is the problem nobody talks about enough. A 301 mph reading at 100 meters does not mean the tornado had 301 mph winds at ground level. The boundary layer effect reduces wind speeds significantly closer to the surface. In the El Reno case, estimates suggest ground-level winds may have been in the 200 to 250 mph range, still far exceeding EF5 thresholds but not as extreme as the raw Doppler reading implied. I've seen too many articles treat that 301 number as gospel without mentioning the height at which it was measured. That's incomplete reporting. The tornado reached a record width of 2.6 miles at its peak. For context, the averageEF2 tornado is about 400 yards wide. This was an order of magnitude larger. The ring-shaped structure made traditional damage surveying nearly impossible because the outer circulation paths were often unpopulated. You had massive debris being thrown miles away from the actual damage path, which confused initial post-storm analysis. My biggest issue with how this event gets reported is the failure to address the terrain and rainfall effects. The tornado moved through an area of heavy rain wraparound. Visibility dropped to near zero for anyone in the vicinity. This is why eight storm researchers died that evening. Tim Samaras, his son Paul Samaras, and Carl Young were caught in the outer circulation band as their vehicle became incapacitated. They were experienced professionals. The tornado's rapid size expansion outpaced their escape routes. That should be a permanent reminder in any chase strategy document I read.
Here is a practical detail most guides skip. When a tornado expands beyond two miles wide, you cannot rely on visual acquisition alone. The vortex becomes difficult to track with handheld equipment. I started using dual-platform approaches after that event. One platform for visual confirmation and one for radar data. If you're working solo, this split is essential. I switched to mounting a portable radar unit on a separate vehicle about an hour before the second tornado spawned. The lead vehicle got positioned first. The radar unit followed at a distance that gave me both coverage and an exit route. This is standard practice now among serious researchers. It wasn't back then. The scientific community responded to El Reno by revising several assumptions. Rapid intensification cycles shorter than 15 minutes are now considered plausible for large, long-track supercells. The relationship between DOW-measured velocities and actual ground damage is being recalibrated with new boundary layer models. The NSSL published follow-up papers in 2014 and 2015 using these datasets. The raw data is publicly available through the National Severe Storms Laboratory open data portal if you want to pull the actual velocity scans. One thing the event exposed clearly. The EF Scale is based on damage, not wind speed. When wind speeds exceed what the EF Scale can measure, you get these awkward revisions. The 301 mph measurement has no direct equivalent on the scale. This is why some meteorologists argue for a continuous wind speed scale rather than the current categorical system. The argument has merit, but changing the scale requires consensus from multiple agencies and that process moves slowly.
Get the Full Details
For anyone doing their own research on this event, start with the NSSL After-Event Report. The full dataset including DOW velocity scans is available online. The video footage from multiple chaser platforms shows the rain-wrapped circulation expanding faster than any previous documented case. The timing is important here. The tornado reached maximum width in under ten minutes. Ten minutes. That is not something you can safely react to from a distance. I still get questions about whether mobile radar units like the DOW should be placed closer to the vortex core. My answer hasn't changed. The risk-reward calculation shifted after the deaths on May 31st. Getting the data is worth less than getting home. This sounds like a statement and it is. The protocols adjusted after that evening and the adjustments are real.
