EF0 tornado in Scott County, Iowa
Tornado June 24, 2023 · Scott County, Iowa
The path drawn at its surveyed width of 20 yards (0.01 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 developed about 2 miles east of Walcott along Interstate 80. The tornado tracked east and caused sporadic minor tree and structure damage at the Northwest Boulevard exit just north of I-80. The tornado then moved across the Davenport Airport, and caused damage to canopies, tents, and equipment, which was hosting an airshow. The tornado passed just south of the NWS office, then continued east, producing minor tree and structure damage along 210th St. The tornado followed an intermittent path of around 9.6 miles, and was on the ground intermittently for about 14 minutes. The tornado was rated EF-0, with maximum estimated winds around 75 mph. Occasional minor tree damage was also observed south of the path, due to straight line winds.
The wider storm
Scattered severe storms tracked across southeast Iowa during the mid-afternoon into early evening of June 24, producing large hail up to golf ball size in Van Buren County and tennis ball size hail near Ottumwa.
More organized clusters of severe storms tracked through Dubuque into far northwest IL during the evening and late night hours of June 24. Another storm cluster moved through the Quad Cities, producing wind gusts to 70 mph at the Davenport ASOS and damage to trees and power poles. An EF-0 tornado also tracked east along and north of I-80 near the Davenport Airport, causing sporadic minor tree and structure damage. This storm impacted the Quad City Airshow grounds, while no visitors were present.
Began near Maysville (41.6000, -90.7100).
Source: NOAA Storm Events Database, event 1103039. 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.