EF1 tornado in Adair County, Oklahoma
Tornado April 14, 2026 · Adair County, Oklahoma
NOAA records this tornado county by county. Its path ran through Cherokee County → Adair County → Washington County, Arkansas; the totals above are for the whole tornado.
The path drawn at its surveyed width of 800 yards (0.45 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
This is the second segment of a three-segment tornado. The tornado moved into Adair County south of the 754 Road, and into rugged terrain. Trees were uprooted as it moved across the 4630 Roads southwest of Christie, and the roof of a manufactured home was damaged. The tornado uprooted numerous trees and snapped numerous large tree limbs along Highway 62, with more trees uprooted along Cemetery Road and Highway 59, and along the 4750 Road before moving into Washington County, AR. Based on this damage, maximum estimated wind in this segment of the tornado was 90 to 100 mph.
The wider storm
Strong to severe thunderstorms developed over central Oklahoma during the early evening of the 14th, ahead of a dry line and an approaching upper level disturbance. The thunderstorms moved eastward into eastern Oklahoma during the late evening as they organized into a squall line. The line of thunderstorms produced several tornadoes and damaging wind.
Another round of strong to severe thunderstorms developed across portions of eastern Oklahoma during the afternoon and evening of the 15th. The strongest thunderstorms produced large hail up to two inches in diameter and damaging wind.
Began near Titanic (35.9170, -94.7970).
Other tornadoes from the same storm system
4 more tornadoes the National Weather Service filed under this storm episode.
Source: NOAA Storm Events Database, event 1325206. 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.