EF1 tornado in Gibson County, Indiana
Tornado May 19, 2022 · Gibson County, Indiana
NOAA records this tornado county by county. Its path ran through Wabash County, Illinois → Gibson County → Knox 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
The tornado crossed from Wabash County, Illinois into Gibson County. The tornado affected only a small corner of Gibson County between East Mt. Carmel and the White River. Several large trees were blown down. The peak rating in the Gibson County portion of the track was EF-1. The tornado then crossed the White River into Knox County, Indiana, where it paralleled the Gibson County line near the White River to U.S. Highway 41 and beyond.
The wider storm
Two rounds of severe thunderstorms occurred. The first round during the mid afternoon hours was associated with a surge of higher dew points northward. Storms erupted along this effective front over southwest Indiana, which was beneath a region of warm moist wind flow at 850 mb. Very large hail accompanied a few of these storms. The second round was an organized complex of thunderstorms that accompanied a pronounced mesoscale convective vortex (MCV) that tracked across Missouri and Illinois. A corridor of moderate to strong instability formed ahead of the MCV from southern Missouri into southern Illinois and Indiana. After a brief lull over Illinois, the storms redeveloped during the evening over the Wabash Valley region as a small cluster with an embedded supercell. The supercell produced a tornado that tracked into southwest Indiana.
Began near East Mt Carmel (38.4100, -87.7450).
Source: NOAA Storm Events Database, event 1018172. 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.