EF3 tornado in Grady County, Oklahoma
Tornado May 6, 2015 · Grady County, Oklahoma
The path drawn at its surveyed width of 1,500 yards (0.85 mi) — zoom in and the swath grows to true scale. Other tornadoes recorded nearby that day are shown faint.
What the National Weather Service wrote
A large tornado developed east of Amber and moved slowly northeast near or along Interstate 44, then turned north impacting the community of Bridge Creek. The most intense damage occurred just east of the Interstate 44 and H.E. Bailey Turnpike Spur near Bridge Creek where EF3 damage was observed to a home (DI 2, DOD 7) and a mobile home (DI 4, DOD 12). A pickup truck was also thrown for several hundred yards in this area. Numerous homes and other buildings were damaged along the tornado path.
The wider storm
A potent Spring storm system took shape across the Southern and Central Plains. Strong surface cyclogenesis took shape during the day, allowing ample moisture to return northward with strong southerly flow. At the same time, a strong upper level shortwave trough allowed strong mid level westerlies to overspread much of the Plains region. With large instability and wind shear, the stage was set for widespread severe storm development. Storms initiated within the open warm sector ahead of the dryline. The first storm developed near Lawton and moved northeast along I-44 into parts of central Oklahoma, resulting in several tornadoes and large hail. Additional supercells spawned tornadoes across northern Oklahoma, and the slow moving nature of storms lead to several occurrences of flash flooding. Storms continued well into the night.
Began near Amber (35.1576, -97.8032).
Other tornadoes from the same storm system
14 more tornadoes the National Weather Service filed under this storm episode.
Source: NOAA Storm Events Database, event 581795. Narratives are written by the National Weather Service forecast office that issued the report.
Tornadoes near your address
See every tornado that passed near a place you know, measured to its path.
We couldn’t get your location. Check that location access is allowed for this site, or type an address.