EF2 tornado in Chilton County, Alabama
Tornado March 2, 2012 · Chilton County, Alabama
NOAA records this tornado county by county. Its path ran through Chilton County → Coosa County; the totals above are for the whole tornado.
The path drawn at its surveyed width of 700 yards (0.40 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 touched down just west of Interstate 65, south of exit 200 in Chilton County. Here, a few trees were snapped or uprooted. It quickly strengthened and grew to its maximum width of 700 yards as it crossed County Road 502. The tornado moved east across US Highway 31 near the intersection with County Road 526, 1.5 miles south of Verbena. The tornado intensified to 125 mph and destroyed one home and caused significant damage to another, as well as mowing down hundreds of trees around the two homes. The tornado continued to snap and uproot trees as it neared County Road 524, where it also destroyed two single-wide manufactured homes and caused significant damage to two homes. A total of thirteen homes were damage or destroyed in and around Verbena. The tornado then crossed into Coosa County, before it eventually lifted.
The wider storm
On March 2, 2012, a strong cold front moved through Central Alabama. Severe thunderstorms developed along and ahead of this front. Some of these thunderstorms were supercells. These supercells produced damage across southern and eastern sections of the area. Damaging straight line winds, tornadoes, large hail and localized flooding occurred with this event.
Began near Verbena (32.7246, -86.5361).
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 374379. 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.