Home / Virginia / Rockingham
EF1 tornado in Rockingham County, Virginia
Tornado July 21, 2026 · Rockingham County, Virginia
NOAA records this tornado county by county. Its path ran through Pendleton County, West Virginia → Rockingham County; the totals above are for the whole tornado.
The path drawn at its surveyed width of 150 yards (0.09 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 tornado that began in Pendleton County, West Virginia, tracked through an unpopulated, wooded area across the ridge/state line. It reached the 24300 block of Gochenour Lane 3 miles southwest of Criders. Tree damage continued up Gobble Mountain before lifting.
In summary, thousands of trees were downed along this rural path. In peak intensity areas, most of the trees in the path were uprooted or snapped. Structural damage was mainly from tree falls, although there was some wind damage to siding and outbuildings noted.
The wider storm
A potent frontal system interacted with a very unstable airmass over a broad area from the Midwest to the Mid-Atlantic and Northeast. Clusters of thunderstorms produced scattered damaging wind gusts in the afternoon and evening. A cluster of supercells spawned five tornadoes over the mountainous region of eastern West Virginia and western Virginia in the mid afternoon to mid evening hours. This event was notable for where the tornadoes occurred. For example, two tornadoes occurred in Pendleton County, WV--the first tornadoes in the county since 1998; one tracked for over 12 miles across multiple ridgelines.
Began near Criders (38.7238, -79.0857).
Other tornadoes from the same storm system
3 more tornadoes the National Weather Service filed under this storm episode.
Source: NOAA Storm Events Database, event 1346865. 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.