Tornado outbreak sequence of May 2003

From Wikipedia, the free encyclopedia
(Redirected from May 2003 tornado outbreak)

Tornado outbreak sequence of May 2003
A tornado in the middle of the fields striking a motor plant.
The MooreSoutheast Oklahoma City tornado hitting the GM motor plant on May 8.
TypeTornado outbreak, Flood event
DurationMay 3, 2003 (2003-05-03)–May 11, 2003 (2003-05-11)
Highest winds
Tornadoes
confirmed
363 tornadoes (62 significant)[note 1]
Max. rating1F4 tornado
Duration of
tornado outbreak2
7 days, 22 hours
Largest hail4.75 in (12.1 cm) in Mahaska County, Iowa
Fatalities42 deaths (+9 non-tornadic deaths), 652 injuries (+52 non-tornadic injuries)
DamageUS$4.1 billion (US$5.8 billion 2019 CPI)
Areas affectedGreat Plains, Eastern United States
1Most severe tornado damage; see Fujita scale
2Time from first tornado to last tornado
Part of the Tornadoes of 2003

From May 3 to May 11, 2003, a prolonged and destructive series of tornado outbreaks affected much of the Great Plains and Eastern United States. Most of the severe activity was concentrated between May 4 and May 10, which saw more tornadoes than any other week-long span in recorded history; 335 tornadoes occurred during this period, concentrated in the Ozarks and central Mississippi River Valley. Additional tornadoes were produced by the same storm systems from May 3 to May 11, producing 363 tornadoes overall, of which 62 were significant.[note 1] Six of the tornadoes were rated F4, and of these four occurred on May 4, the most prolific day of the tornado outbreak sequence; these were the outbreak's strongest tornadoes. Damage caused by the severe weather and associated flooding amounted to US$4.1 billion (US$5.8 billion in 2016), making it the costliest U.S. tornado outbreak of the 2000s. A total of 50 deaths and 713 injuries were caused by the severe weather, with a majority caused by tornadoes; the deadliest tornado was an F4 that struck Madison and Henderson counties in Tennessee, killing 11.

Overview[edit]

A map displaying a high risk for severe weather over the Ozarks with a slight risk extending throughout the Mississippi River Valley.
The Storm Prediction Center's convective outlook for May 4 highlighting the regions with the greatest likelihood of severe weather. This day proved to be the most active and deadly of the event with 81 tornadoes and 38 fatalities.[2]

During the first half of May 2003, atmospheric conditions across the Central and Southeastern United States proved exceptionally favorable for widespread severe weather. Idealized patterns for large tornado outbreaks occurred each day from May 3 to 11, resulting in a prolonged and extensive series of outbreaks. Warm, moist air flowed northward from the Gulf of Mexico across the Central United States and reached as far north as Missouri. This created an anomalously large warm sector–the airmass behind a warm front and ahead of a dry line–for thunderstorms to develop within. The unusually far-reaching nature of this airmass resulted in the greatest tornadic activity occurring outside the climatological maximum area for tornadoes in May. Atop the northward surface winds, the upper-level jet stream blew almost perpendicular, creating strong wind shear across Kansas, Missouri, Oklahoma, and Tennessee. Multiple shortwave troughs initiated tornadic events throughout the outbreak. As severe weather shifted east across the country, another trough would cross from the Pacific to the Central United States and reignite activity. The cause of these successive troughs is unknown, but they proved a key factor in the prolonged nature of the outbreak. Throughout this period, no cold fronts propagated south from Canada; the lack of these allowed the atmosphere to continually destabilize and fuel further thunderstorms.[2] The pattern finally ceased on May 11–12 with the active pattern shifting to New England the formation of a ridge over the Rocky Mountains.[3]

Throughout the nine-day outbreak, 363 tornadoes touched down across the United States. Of these, 62 reached at least F2-intensity, while 6 reached F4. The most prolific and violent day of the outbreak was May 4; 79 tornadoes touched down, of which 4 reached F4-intensity. Between May 4 and May 10, 335 tornadoes developed across 26 states, setting a record for the most tornadoes ever documented over the course of a week. At least one significant tornado was reported daily across nine consecutive days, with at least a dozen tornadoes total occurring daily over the same timeframe.[2] Due to the temporal expanse of the event, it was classified as a tornado outbreak sequence—a "continuous or near-continuous sequence of tornado outbreak days"—with only three historical events of comparable longevity and severity according to data compiled by Thomas P. Grazulis.[4] May 2003 ultimately became the most active month for tornadoes in recorded history until it was later surpassed by April 2011.[2][5] In total, the widespread severe weather event caused an estimated $4.1 billion (2003; $5.8 billion 2019 CPI-adjusted) in damage and 41 deaths alongside 642 injuries.[2][6]

Meteorological synopsis[edit]

On April 30, meteorologists at the Storm Prediction Center (SPC) noted the likelihood of a major tornado outbreak across a large area of the Central and Eastern United States for the period of May 2–6.[2] Ahead of the most active day, the SPC issued a rare high-risk outlook for severe weather across eastern Oklahoma, eastern Kansas, western Missouri, and northwestern Arkansas.[7] A total of 127 severe weather watches and 4,050 warnings (2,960 severe thunderstorm and 1,090 tornado) were issued from May 4. Of the watches, 25 were classified as Particularly Dangerous Situations, a type of watch reserved for the most life-threatening events. The issuance of such watches resulted in an average lead-time of 2 hours and 3 minutes for fatal tornadoes. Seven of the eight fatal tornadoes occurred within a high-risk outlook area, with the eighth just outside in a moderate-risk area. An average of 12 watches were issued each day; May 6, 8, and 10 saw more than 20 each. Watches were continuously in effect from 16:40 UTC on May 4 through 12:00 UTC on May 9. May 6 saw the greatest number of advisories with a record 921 warnings. The SPC and the National Weather Services offices in Kansas City, Springfield, Memphis, Paducah, and Oklahoma City received a letter of praise signed by 11 members of the United States House Committee on Science, Space, and Technology commending their high-quality service during the event. Furthermore, the SPC webpage received an average of 5.6 million views per day during the outbreak.[3]

May 3[edit]

Confirmed tornadoes on May 3, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 10 2 1 0 0 0 13
Looping radar imagery
Radar animation of a supercell that produced at least four tornadoes in Haskell County, Texas, on May 3

On the morning of May 3, the SPC predicted that a trough would intensify over the eastern U.S., resulting in a wide and expanding area of increased wind shear and atmospheric instability across the southeastern U.S. Strong southerly winds in the lower levels of the troposphere over the central Great Plains were also expected to advect warm and moist air into the Great Plains. These factors were forecast to provide a conducive environment for severe weather across much of the U.S.; the SPC would delineate moderate risks[note 2] for severe weather in parts of the central Great Plains, Red River region, and southeastern U.S. over the course of the day, with a lesser but nonetheless extant expectation of severe weather extending outwards from the focal areas.[9] The first severe watch on May 3 was a severe thunderstorm watch issued for parts of the Gulf Coast at 14:14 UTC (9:14 a.m. CDT) in connection with a mesoscale convective system that had been tracking southeast over eastern Mississippi and western Alabama during the morning. The outflow from this complex of storms was expected to also trigger additional severe thunderstorms within an environment favorable for large hail and strong winds near the Gulf Coast.[10][11] However, the SPC noted that the day's most conducive environment of severe weather—conditional on the development of storms—lay farther west over the southern Great Plains along a decaying warm front and a dry line.[10]

The SPC issued a tornado watch at 18:15 UTC (1:15 p.m. CDT) for parts of Arkansas, Louisiana, Oklahoma, and Texas. Although an atmospheric sounding from Fort Worth, Texas, showed the presence of a capping inversion that prevented storm development, sufficient daytime heating could initiate storms that could develop in the otherwise favorable conditions for severe weather in place.[12] By 21:00 UTC (4:00 p.m. CDT), a line of towering cumulus and cumulonimbus clouds emerged along the dry line east of Lubbock, Texas, resulting in a focused threat area for large hail, strong wind gusts, and isolated tornadoes in southwestern Oklahoma and northwestern Texas.[13] Concurrently, decreasing air pressures, steepening lapse rates, and increasing moisture resulted in another conducive area for severe weather over the central Great Plains and along the eastern periphery of the Rocky Mountains.[14] A tornado watch was issued for northeastern Colorado and northwestern Nebraska in response to this emergent favorability for severe weather at 22:10 UTC (5:10 p.m. CDT).[15]

By 01:00 UTC (8:00 p.m. CDT), severe thunderstorms were active over the Oklahoma/Texas region and the Dakotas/Nebraska area.[16] The final tornado watch of the day was issued for western Oklahoma and northwestern Texas at 01:05 UTC (8:05 p.m. CDT) and expired at 07:00 UTC (2:00 a.m. CDT).[17] Tornadoes were reported in Mississippi, Nebraska, South Dakota, and Texas throughout the day; there were 18 tornado reports, though only 14 tornadoes were confirmed.[18][19] Although the SPC received its first tornado report at 21:17 UTC (4:17 p.m. CDT) from Meade County, South Dakota,[18] the first confirmed tornado was an F0 tornado that touched down at 21:41 UTC (4:41 p.m. CDT) near Minatare in Scotts Bluff County, Nebraska.[20] The strongest tornado of the day was an F2 tornado that touched down near Lake Stamford in Texas at around 00:10 UTC (7:00 p.m. CDT). The tornado originated from an isolated supercell thunderstorm that had developed along the dry line in northwestern Texas; the same thunderstorm produced at least three other tornadoes during its two-hour traversal of Haskell County, Texas.[21]

May 4[edit]

Confirmed tornadoes on May 4, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 31 23 13 8 4 0 79
Animated weather radar data
Radar imagery of a storms moving through the Kansas City area on May 4

May 4 was the most active day of the tornado outbreak sequence: the SPC received 94 tornado reports, though surveys and reanalyses confirmed 79 tornadoes.[22][19][23] In terms of the number of tornadoes, May 4, 2003, was the second most prolific day for tornadoes in the U.S. since 1970, behind only the 1974 Super Outbreak.[24] The 38 tornadoes confirmed in Missouri was the highest single-day total for the state and were more numerous than any previous month on record.[25] The day's severe weather was largely driven by a powerful mid-tropospheric disturbance moving northeast across the central and northern Great Plains in tandem with an unusually strong area of low pressure over northeastern Kansas.[3][26] These weather features were also positioned beneath a negatively-tilted trough and an anomalously robust portion of a jet stream.[26] A cold front and dry line were located south and southwest of the low-pressure area while a warm front spanned from the system southeast to the Tennessee Valley.[3]

This atmospheric setup was highly conducive for tornadogenesis, and accordingly the potential for a major tornado outbreak was forecast well in advance.[26] The National Weather Service office in Pleasant Hill, Missouri, noted the potential for severe weather on May 4 as early as April 28.[3] In their Day 2 Convective Outlook, issued on May 3, the SPC indicated that the eastern fringes of the southern Great Plains and the lower and central Mississippi Valley had a moderate risk of experiencing severe weather on May 4.[27] At 13:00 UTC (8:00 a.m. CDT) on May 4, the agency noted a high risk of severe weather for parts of Arkansas, Kansas, Missouri, and Oklahoma, predicting a "significant severe thunderstorm event" and the potential for "long-track and violent tornadoes" within the high risk region. Additionally, areas within this region had at least 25 percent chance of experiencing a nearby tornado and at least a 10 percent change of experiencing a nearby significant tornado. The SPC cited the confluence of high instability (characterized by convective available potential energy [CAPE] values between 2000 and 4000 J/kg) and strong wind shear as factors contributing to the anticipated tornado outbreak.[28]

By around 15:00 UTC (10:00 a.m. CDT), the conducive conditions for severe weather projected in computer forecast models had begun to come to fruition. An area of low pressure centered south of Hastings, Nebraska, was intensifying amid strengthening winds aloft. A dry line extended south of the cyclone over areas east of Dodge City, Kansas. A warm front also extended outwards from the low pressure system towards Topeka, Kansas, and Joplin, Missouri. Behind the front, dew points exceeded 60 °F (16 °C).[29] The warm front moved north as the day progressed, bringing along with it the warm and moist maritime tropical air mass.[26] The SPC expected that both the warm front and the dry line would serve as a focus for storm development as the storm system evolved.[29] The rapid development of storms just north of the low pressure system and the increasingly conducive conditions available to these storms led the SPC to issue their first tornado watch of the day at 16:40 UTC (11:40 a.m. CDT) for parts of northeastern Kansas and south-central and southeastern Nebraska.[30] Roughly an hour later, additional tornado watches—all classified as Particularly Dangerous Situations—were issued for parts of Arkansas, Iowa, Kansas, Missouri, Nebraska, and Oklahoma ahead of an emerging line of towering cumulus and cumulonimbus clouds spanning from southeastern Nebraska to northeastern Kansas.[31][32] As the low pressure system intensified—its central pressure falling 6.6 mbar (6.6 hPa; 0.19 inHg) in 2 hours—conditions continued to become more favorable for the formation of strong tornadoes.[33]

Image of a tornado
The tornado that struck Stockton, Missouri, on May 4

The day's first tornado was a brief F0 landspout that touched down in Scott County, Kansas, at 19:59 UTC (2:59 p.m. CDT).[34][35] A line of thunderstorms developed over northeastern Kansas after 19:30 UTC (2:30 p.m. CDT) and later produced nine tornadoes in northeastern Kansas and northwestern Kansas. Four of these tornadoes touched down in the Kansas City, Missouri, area, including two F4 tornadoes. Concurrently, additional tornadic storms developed along the dry line in southeastern Kansas during the afternoon. These storms produced an F4 tornado and an F3 tornado that tracked for 85 mi (137 km), impacting Jericho Springs, Missouri, and Stockton, Missouri.[35] The diminishing of the capping inversion along the dry line that had prevented storm development earlier in the day led the SPC to issue a tornado watch at 20:00 UTC (3:00 p.m. CDT) for south-central and southeastern Oklahoma and north-central and northeast Texas.[36] One supercell developed over northeastern Oklahoma and moved into southwestern Missouri, producing an F3 tornado that struck Pierce City, Missouri.[35]

Conditions within the preexisting risk areas remained favorable for tornadoes into the evening while the tornadic risk increased farther east, prompting the SPC to issue a tornado watch for new areas of Arkansas, Kentucky, Mississippi, Missouri, and Tennessee at 23:55 UTC (6:55 p.m. CDT).[37] Tornadoes developed over Arkansas during the afternoon and evening of May 4, including two tornadoes with 35-and-42-mile (56 and 68 km) path lengths.[35] At 01:00 UTC (8:00 p.m. CDT), the SPC indicated a high risk for severe weather for parts of Arkansas, Missouri, and Tennessee as the tornado outbreak remained in progress and tornado-producing supercells persisted into the overnight hours,[38] outlining that "a dangerous tornado situation [was] developing along the warm front" between northeastern Arkansas and western Tennessee and that any developing storms would rapidly assume supercell characteristics.[39] Southerly winds had continued to bring tropical air into the region, raising surface temperatures to near 80 °F (27 °C) and bringing dew points above 70 °F (21 °C) by 03:00 UTC (10:00 p.m. CDT). Storms that had initially formed over northeastern Arkansas and the Missouri Bootheel at around 22:00 UTC (5:00 p.m. CDT) quickly strengthened and acquired supercell characteristics; some of these storms entered western Tennessee by 02:00 UTC (9:00 p.m. CDT), producing tornadoes and damaging winds and hail. Over the next two hours, the morphology of these storms varied between a unified squall line with embedded rotation or a set of discrete supercells.[40] One of the storms encountered highly conducive conditions and produced an F4 tornado near Denmark, Tennessee, that later tore through Jackson, Tennessee.[35][40]

May 5[edit]

Confirmed tornadoes on May 5, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 16 11 0 1 0 0 28

The atmospheric environment continued to remain conducive for tornadoes well into the night of May 4–5. Tornado watches were issued and remained in effect for various parts of Alabama, Arkansas, Illinois, Indiana, Kentucky, Mississippi, Missouri, North Carolina, Oklahoma, and Tennessee during the early morning hours of May 5 as conditions supported both the persistence of preexisting supercell thunderstorms and the development of new storms.[41] Radar imagery indicated that the threat for severe weather had begun to diminish by around 09:00 UTC (4:00 a.m. CDT).[42] Nonetheless, the potential for isolated tornadoes continued through the night in connection with a cluster supercell thunderstorms over Middle Tennessee.[43] The SPC predicted May 5 would be another active day for severe weather, projecting a Moderate Risk of severe weather a day in advance before projecting a High Risk at 16:30 UTC (11:30 a.m. CDT) on May 5 for areas surrounding the border between Arkansas and Louisiana;[44][45] the anticipated overlap of 50–55 kn (58–63 mph; 93–102 km/h) wind shear and CAPE exceeding 3000 J/kg was cited as contributing factors to the day's anticipated supercell development and consequential high risk for severe weather.[45] The forecast high risk region was later shifted towards the Tennessee Valley following the increase of air divergence and the persistence of wind shear and atmospheric instability in that area.[46] The principal weather features on May 5 included a longwave trough centered over the western U.S., a powerful upper-tropospheric trough over the Mississippi Valley, and a cyclone over Iowa tracking northeastwards towards Wisconsin, with the most significant weather expected to coincide with an area of steep lapse rates.[47][45]

Three F0 tornadoes were reported in northern Mississippi between 12:55–13:55 UTC (7:55–8:55 a.m. CDT).[19][48] Despite an initial weakening of thunderstorms over western Tennessee during the morning of May 5, the overarching airmass remained unstable and supportive of tornado formation.[49] Supercell thunderstorms formed over the state within this environment by 16:00 UTC (9:00 .a.m. CDT) as temperatures rose above 80 °F (27 °C) and dew points eclipsed 70 °F (21 °C).[50] Eight confirmed tornadoes touched down in Tennessee between 14 and 22 UTC (9 a.m. CDT).[19][23] One of these tornadoes produced F3-rated damage near Belleville, Tennessee, and was ultimately the day's strongest tornado.[35][51] The presence of very cold air in the middle and upper levels of the troposphere facilitated another locally favorable environment for severe thunderstorms over southern and eastern Michigan after about 21:00 UTC (5:00 p.m. EDT).[52] Some thunderstorms formed in tandem with a lake breeze from Lake Michigan and then moved along a warm front, producing hail, damaging winds, and several funnel clouds, particularly near the front where wind shear was maximized.[19] The complex of thunderstorms also produced an F1 tornado in Oakland County.[53][54]

At around 15:00 UTC (10:00 a.m. CDT), thunderstorms began to form east-southeast of Dallas, Texas, amid a region with a weak capping inversion. Due to the favorable environment downwind, the SPC assessed the likely emergence of tornadic supercells as these storms moved towards the Ark-La-Tex region and accordingly issued a tornado watch for the area.[55] However, no tornadoes were reported in Arkansas, Louisiana, or Texas during the day.[48] Despite otherwise supportive conditions for tornadogenesis, rawinsondes launched at 18:00 UTC (1:00 p.m. CDT) suggested that the capping inversion remained in place within the SPC's High Risk region, suppressing the development of storms.[46] Farther east, a mesoscale convective system formed over Mississippi during the evening within an energetic environment supportive of strong updrafts;[56] however, the cluster of thunderstorms weakened after 03:00 UTC (10:00 p.m. CDT) as air pressures increased, resulting in a diminished threat for severe weather.[57] The SPC no longer depicted a high risk of severe weather in their 01:00 UTC (8:00 p.m. CDT) convective outlook, showing at most a moderate risk for severe weather for northern Mississippi and surrounding areas. Overnight, a front extending from eastern Michigan to eastern Oklahoma and an outflow boundary extending from southeastern Arkansas towards Georgia were the primary foci for thunderstorm growth.[58]

May 6[edit]

Confirmed tornadoes on May 6, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 41 26 6 1 1 0 75
Image of a computer screen with radar data
The Tennessee Emergency Operations Center on May 6

At 06:00 UTC (1:00 a.m. CDT) on May 6, the SPC projected a Moderate Risk of severe weather centered on the Ozarks, where dew points above 70 °F (21 °C) and steep lapse rates were expected to foment a highly unstable atmosphere ahead of a rapidly developing low-pressure area and its associated cold front and dry line. Warm temperatures throughout the eastern U.S. were also forecast to contribute to a Slight Risk of severe weather across parts of the Southeastern U.S. and the Mid-Atlantic states.[59] Winds in the mid-levels of the troposphere were similar to the situation on May 4, shaped once again by a strong storm system over the central and northern Great Plains and the overlap of fast southwesterly winds at altitude with moist air below.[3] The persistence of 70 kn (81 mph; 130 km/h) winds in the mid-levels of the troposphere—resulting in strong wind shear—led to a maintained risk for tornadoes along an outflow boundary near the Tennessee Valley and along a warm front draped over Georgia and the Carolinas during the early morning hours of May 6.[60][61] A line of severe thunderstorms with a bow echo apparent on weather radar moved east across northern Georgia and the Carolinas during this period;[62] two F1 tornadoes and an F0 tornado were confirmed over central South Carolina.[19]

A second large complex of thunderstorms persisted over Middle Tennessee, northern Mississippi, and northern Alabama during the pre-dawn hours, with the unstable atmosphere and high wind shear creating an attendant risk for supercells, tornadoes, and heavy rain.[63] Among these was a high-precipitation supercell that developed near the warm front in northern Alabama and produced several tornadoes.[64] Ten tornadoes—all rated either F0 or F1—occurred in northern Alabama near the state border with Tennessee between 11 and 16 UTC (6-11 a.m. CDT) amid increasing wind shear.[19][65] Additional severe thunderstorms in the morning became active over southern Illinois, eastern Kansas, western Missouri, Central Texas, during the period.[66][67][68] At around 17:00 UTC (1:00 p.m. EDT), a line of storms exhibiting rotation on weather radar moved into northern Georgia, approaching an area where wind shear favored an isolated tornado threat.[69][70] Over the next two hours, six tornadoes occurred near the Georgia–South Carolina border, of which the strongest was an F2 tornado that tracked across Madison and Elbert counties in Georgia.[19]

Temperatures along a front in Oklahoma had risen to near 80 °F (27 °C) by 15:00 UTC (10:00 a.m. CDT), producing a highly unstable atmosphere marked by CAPE values ranging between 3000 and 4000 J/kg and lapse rates of around 8.5 °C/km.[71] A broad area of rising air and an unstable atmosphere was also present to the north over eastern Kansas and western Missouri.[72] By 20:00 UTC (3:00 p.m. CDT), a supercell was approaching Jefferson City and Columbia in Missouri while cumulus clouds showed signs of further development along a dry line to the south between Tulsa, Oklahoma, and Abilene, Texas.[72][73][74] Atmospheric conditions were becoming progressively supportive of severe weather as a low-pressure area strengthened along the Kansas–Oklahoma border;[73] a line of severe thunderstorms soon developed along a warm front over Missouri appended to the low-pressure system as a new line of storms arose to the south over northeastern Oklahoma.[75] The thunderstorms over Missouri evolved into a strong cluster of supercells by 22:40 UTC (5:40 p.m. CDT) and were moving east-southeast into an area centered over southern Illinois with CAPE values near 2500 J/kg and dew points near 70 °F (21 °C).[76][77] These storms persisted into western Kentucky after nightfall, advancing on the leading edge of a localized pool of high air pressure and cold air.[78][79] There were 24 tornadoes in Missouri, 9 in Illinois, and 9 in Kentucky between 21 and 05 UTC (4 p.m.–12:00 a.m. CDT), including an F3 tornado that struck Jackson, Missouri, and an F4 tornado that took a path 33 mi (53 km) path through southern Illinois.[35][19] A new area of accelerated winds in the upper levels of the troposphere—known as a jet streak—triggered the formation of storms east of the Dallas–Fort Worth metropolitan area and along the cold front over eastern Oklahoma by around 04:00 UTC (11:00 p.m. CDT).[80] An F2 tornado touched down in Wood County, in northeastern Texas at 04:45 UTC (11:45 p.m. CDT) and took a 54.4-mile (87.5 km) mile path through four counties.[81]

May 7[edit]

Confirmed tornadoes on May 7, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 16 13 1 0 0 0 30

The SPC predicted a Slight Risk for a broad area of the Eastern and Central U.S. in their 06:00 UTC (1:00 a.m. CDT) Day 1 Convective Outlook for May 7. Several shortwave troughs in the upper levels of the troposphere were expected to track northeastward or eastward across the region, overlapping with a broad and wavy front that extended from New England to New Mexico.[82] At the time, a large mesoscale convective system, formed from the merger of supercells and other storms, was producing torrential rainfall over Tennessee and Kentucky with rain rates of 2–3 in (51–76 mm) per hour.[83][84] Another complex of severe thunderstorms ahead of a cold front advanced across the Ark-La-Tex region after 07:00 UTC (2:00 a.m. CDT) with high wind shear in place;[85] four tornadoes occurred in the region between 5–11 UTC (12–6 a.m. CDT).[19] These storms continued to move east through an unstable environment, with a nearby outflow boundary producing enhanced vorticity supportive of tornado development;[86] crossing several states, the storms reached the Atlanta, Georgia, area by around 1535 UTC (11:35 a.m. CDT).[87][88][89] Additional storms continued to develop farther west over the same states as the surrounding air mass remained unstable with CAPE values between 1500 and 2000 J/kg.[90] Six tornadoes occurred in Alabama, Arkansas, Louisiana, Mississippi, and Texas before noon, including an F2 tornado near Houston, Mississippi, that proved to be the only significant tornado during the day.[19][35] The persistence of warm and moist air with the aid of daytime heating maintained the severe weather potential into the afternoon for the same areas.[91][92] Fifteen tornadoes, all rated F0 or F1, touched down in Alabama, Mississippi, Georgia, between 17–1 UTC (12–8 p.m. CDT);[19] most of the day's tornado reports occurred in these states.[93] Thunderstorms sustained over the area into the evening before the surrounding airmass stabilized, resulting in a weakening of the storms by midnight.[94][95][96]

Another line of storms moved in the Mid-Atlantic region during the afternoon, tracking into an environment supportive of severe weather;[97][98] three tornadoes occurred in North Virginia and Maryland during the afternoon evening as the storms moved southeast, along with damaging winds in the Washington, D.C. area.[19] Conditions were also marginally supportive of supercell thunderstorms in the Dakotas and the Rust Belt during the day.[99][100] In the early afternoon, cumulus clouds began to build in the vicinity of San Angelo and Junction City in Texas as temperatures warmed above 90 °F (32 °C).[101] Although the presence of a capping inversion initially prevented storm development,[101] its subsequent weakening led the SPC to issue a tornado watch for northwestern Texas and southwestern Oklahoma at 22:00 UTC (5:00 p.m. CDT);[102] within an hour, a pair of supercells developed over northwestern Texas.[103] Overnight, a low-level jet with winds of around 50 kn (58 mph; 93 km/h) brought additional moisture into North Texas and Oklahoma, causing a warm front over Oklahoma to advance north and promoting atmospheric destabilization.[104] Supercells rapidly developed near the warm front by 03:35 UTC (10:35 p.m. CDT) over northern Texas and southern Oklahoma, prompting an issuance of a tornado watch along the Red River; these storms became tornadic and persisted into May 8.[35][105]

May 8[edit]

Confirmed tornadoes on May 8, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 25 11 5 3 1 0 45
Map of severe weather risk regions in the US
The SPC's convective outlook for May 8 indicated a High Risk of severe weather over the Central US, marking the third of four days during the tornado outbreak in which such a risk was forecast.

The SPC predicted that May 8 would be another significant day for severe weather. A negatively-tilted trough was forecast to move northeast across Kansas, prompting cyclogenesis in the region along the leeward side of the Rocky Mountains.[106][107] During the day, a low-pressure area would intensify over southeastern Colorado, forcing a warm front northward from Oklahoma to Kansas and resulting in a weather pattern resembling the severe weather setup from May 4.[35] Clearing skies were expected to allow CAPE values to rise unstable levels of around 3000–4000 J/kg, and, when combined with strong southwesterly winds aloft, were forecast to produce an environment conducive to the development of supercell thunderstorms. The SPC initially projected a Moderate Risk of severe weather over the central Great Plains before raising a High Risk for severe weather on May 8 centered on the Kansas City area.[106][107] A more conditional risk for severe weather was predicted along a dry line over the southern Great Plains due to the presence of a capping inversion that was forecast to limit the coverage of storms.[107]

The cluster of supercells that developed on the evening of May 7 along the Red River near a warm front remained active over the region into the early morning hours of May 8.[108] One large supercell within the cluster produced three F2 tornadoes between 6–8 UTC (1–3 a.m. CDT) in Jefferson, Marshall, and Love counties in south-central Oklahoma.[19][35] The same storm continued across eastern Oklahoma before weakening after crossing into Arkansas at around 12 UTC (7 a.m. CDT).[109][110] Atmospheric conditions remained supportive of storm development further along the warm front to the east towards the Tennessee Valley through the morning hours and into the afternoon before warming air aloft resulted in increased convective inhibition.[111][112][113][114] Another belt of storms, presenting primarily a threat of large hail, were concurrently active to the north between south-central Nebraska to northwestern Arkansas, supported by strong warm air and moisture advection;[115] these storms also weakened as the influx of warm and moist air diminished.[116]

Radar image of a storm
Radar image of the supercell that produced the F4 tornado in the Oklahoma City area

By 16:30 UTC (12:30 p.m. CDT), temperatures within the areas under the SPC's Moderate and High risk regions over the central Great Plains, central Mississippi Valley, and lower Ohio Valley warmed above 80 °F (27 °C) with dew points above 70 °F (21 °C). Although a capping inversion remained in place, forcing for the uplift of air was expected to be sufficient to overcome the temperature inversion; the SPC indicated that the atmospheric conditions would lead to any emergent storm rapidly organizing into a supercell.[117] At 17:17 UTC (11:17 a.m. MDT), the first of five brief tornadoes confirmed in Colorado during the day—all rated either F0 or F1—touched down in Adams County.[19] The severe thunderstorms in northeastern Colorado had developed with the aid of orographic lift and strong vorticity in the upper-levels of the troposphere.[118] The quick formation of cumulus clouds ahead of a low pressure area by around 18 UTC (1 p.m. CDT) over central Kansas indicated that supercell development in the area was imminent.[119]

Cumulus clouds were also becoming more numerous and robust ahead of the dry line between southwestern Oklahoma and south-central Kansas. The atmospheric environment in the region had become favorable for severe weather sooner than anticipated with CAPE values reaching above 4500 J/kg and wind shear ranging between 40 and 50 kn (46 and 58 mph; 74 and 93 km/h).[120] These potent conditions were also present as far south as Central Texas, though the stronger capping inversion farther south meant more widespread severe activity was less likely.[121] The SPC issued a tornado watch for northeastern Colorado, northwestern Kansas, and southwestern Nebraska at 18:30 UTC (12:30 p.m. MDT), followed by a second tornado watch for areas along the dry line in south-central Kansas and central Oklahoma at 18:35 UTC (1:35 p.m. CDT).[118][122] A third tornado watch was issued for northern Kansas and southern Nebraska at 18:50 UTC (1:50 p.m. CDT) and the air mass overhead became increasingly unstable with CAPE values over 3000 J/kg ahead of a developing low-pressure area in the vicinity of Russell, Kansas.[123]

Supercell thunderstorms quickly formed and intensified along and north of a warm front ahead of the strengthening low-pressure area and over Kansas and Nebraska after 20 UTC (3 p.m. CDT),[124] accompanied by the formation of additional storms over eastern Kansas an hour later.[125] The day's first tornado in Kansas was an F0 tornado that touched down in Cloud County at 20:32 UTC (3:32 p.m. CDT).[19][126] A smaller area of low pressure forming along the dry line near the Lawton, Oklahoma, area produced conditions locally supportive of tornadogenesis.[127] The first storms developing in this region initially failed to intensify as a result of the strong capping inversion overhead. However, these storms also caused the capping inversion to gradually diminish;[128][129] the emergent storms became more sustained after 20:00 UTC (3:00 p.m. CDT).[129] By the evening hours, a broken line of intense supercell thunderstorms were advancing east across eastern Kansas and Oklahoma within a moderately to highly unstable airmass as the pressure of the nearby cyclone deepened to 993 mbar (993 hPa; 29.3 inHg).[130]

Two tornadic supercells in Oklahoma produced five tornadoes in the state during the afternoon.[131] One strong supercell within an environment supportive of a strong or violent tornado approached the Oklahoma City metropolitan area shortly before 22 UTC (5 p.m. CDT).[132] It spawned three tornadoes, with the final being an F4 tornado that caused significant damage in Moore, southeastern Oklahoma City, Midwest City, and Choctaw.[35][19][131] The second supercell produced an F3 tornado in Osage County.[131] A total of 21 tornadoes touched down in Kansas during the day, of which 5 were significant tornadoes with the strongest rated F3.[19] One supercell led to five tornadoes in Osage and Douglas counties in Kansas, including one F3 tornado.[133] The storms over Kansas persisted after 0 UTC (7:00 p.m. CDT), with tornadoes reported in eastern Kansas and western Missouri during the evening hours, while the strength of the capping inversion to the south suppressed more widespread severe weather.[134][135] At 01:00 UTC (8:00 p.m. CDT), the SPC noted that tornadic supercells and conditions conducive to severe weather remained present, though the main risk area shifted east towards the central Mississippi River valley.[136] The final tornado of the day was an F0 tornado in that lifted at 03:04 UTC (10:04 p.m. CDT) in Johnson County, Missouri.[19][137]

Outside of the highest risk areas for severe weather, the SPC also noted the potential for severe weather in the Tennessee and Ohio river valleys amid the northward advance of a warm front was expected to advect moist and warm air, and around Virginia near a weak and slow-moving cold front.[107][117] Severe thunderstorms tracked southeast through parts of the Mid-Atlantic states during the afternoon; one F0 tornado was reported in Essex County, Virginia.[138][139] Widespread thunderstorms—some with mesocyclones—formed over parts of eastern Missouri, Illinois, southwestern Indiana, and western Kentucky during the afternoon in response to the influx of warm and moist air;[140] four tornadoes occurred in these states during the day.[19]

May 9[edit]

Confirmed tornadoes on May 9, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 16 11 1 1 0 0 29

The SPC projected a Moderate Risk of severe weather for parts of the Central Plains on May 9, assessing the potential for atmospheric conditions in the region to become unstable. CAPE values of 3500–4500 J/kg were anticipated alongside steep lapse rates aloft and strong wind shear.[141] Severe weather was also forecast for the Mid-Atlantic region and the Ohio Valley.[142] As the day progressed, a mid-tropospheric jet stream developed across the Great Plains in response to an intensifying low-pressure region over the Great Basin and a strengthening ridge of high pressure extending north into the Great Lakes.[3] The northward-traveling warm front spanning from North Carolina low-pressure area in eastern Nebraska and a dry line over Kansas and Oklahoma were expected to be foci for the day's severe weather;[141] this same dry line led to the tornadoes in central Oklahoma on May 8 and had moved west.[129] In the early morning hours, a large area of thunderstorms with high cloud bases was tracking east across northern Illinois within a region of warm air advection, generating large hail and damaging winds despite meager atmospheric instability.[143][144]

By around 17 UTC (1 p.m. EDT), some of the storms had congealed into a mesoscale convective system and were beginning to take a more southward trajectory into West Virginia and Virginia.[145] Additional thunderstorms developed across eastern West Virginia and northern Virginia over the next hour, prompting the issuance of a tornado watch for the region.[146] Supercells traversed southeast across parts of Virginia and North Carolina throughout the afternoon and into the evening.[147][148][149] They reached the Outer Banks before 2 UTC (9 p.m. EDT) and eventually weakened as the surrounding air within the planetary boundary layer became more stable.[149] Preliminarily, the eight tornadoes initially reported in Virginia were tied for the second most ever recorded in the state within a 24-hour period.[35] Ultimately, five tornadoes were confirmed in Virginia and nine tornadoes were confirmed in North Carolina on May 9, with the first tornado touching down in Augusta County, Virginia, at 17:55 UTC (1:55 p.m. EDT) and the final tornado lifting from Greene County, North Carolina at 01:10 UTC (9:10 p.m. EDT); all tornadoes in these two states were rated either F0 or F1.[19]

Nighttime photograph of a tornado
The F3 tornado that hit parts of northeastern Oklahoma City on May 9

Closer to the main risk region, scattered thunderstorms began to form and strengthen over northwestern Texas by around 14 UTC (9 a.m. CDT) in response to the advection of warm air.[150] Another cluster of potentially severe thunderstorms formed along the Ohio River in the early afternoon in the wake of the storms that moved through West Virginia, and additional storms continued to form in the region through the afternoon and evening in the vicinity of a well-defined warm front.[151][152][153] Further convective activity developed in southeastern Missouri and southern Illinois during the afternoon as CAPE values reached over 4000 J/kg, indicative of a highly unstable atmosphere.[154] The storms over Texas and Oklahoma were initially transient but became more sustained as a weak shortwave trough began to traverse the region.[155] More thunderstorms developed along the dry line by the late afternoon over Texas and Oklahoma with conditions remaining favorable for the formation of supercells,[156] including surface temperatures above 90 °F (32 °C) and dew points above 70 °F (21 °C).[129] The air mass to the east of the dry line was also becoming exceptionally unstable;[157] by 23:05 UTC (6:05 p.m. CDT), three tornado watches were in effect along a band from North Texas and central Indiana.[157][158][159]

After 1 UTC (8 p.m. CDT), winds aloft over Oklahoma strengthened, resulting in increased wind shear and increased tornado potential.[160] One supercell quickly developed along the dry line in Greer County and was marked with a severe thunderstorm warning at 23:32 UTC (6:32 p.m. CDT) as it tracked northeast.[129] This supercell eventually produced ten tornadoes in Oklahoma, accounting for all of the state's tornadoes that day; the first of the tornadoes was an F0 tornado that touched down at 01:50 UTC (7:50 p.m. CDT) in Caddo County, while the final twister lifted at 05:31 UTC (12:31 a.m. CDT) from Creek County the next day. The strongest of the ten tornadoes was an F3 tornado that hit parts of northeastern Oklahoma City, triggering a tornado emergency and marking the second consecutive day that tornadoes impacted the Oklahoma City area; this tornado was also the strongest tornado of the day.[19][161][162] The supercell later dissipated in northeastern Oklahoma.[161] During the same period, five tornadoes also occurred in northwestern Missouri where storms had been developing throughout the evening along a front, buoyed by the low-level that supported the tornadic activity in Oklahoma;[163][164][165] the strongest of these tornadoes was rated F2 and tracked across Lafayette and Saline counties.[19]

May 10[edit]

Confirmed tornadoes on May 10, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 24 15 7 3 0 0 49
Weather maps of the continental U.S. at 12:00 UTC (7:00 a.m. CDT) on May 10
Contour map
Winds and height of the 500 mbar (500 hPa; 15 inHg) pressure level

A meteorologist at National Weather Service St. Louis, Missouri, described the weather pattern over the U.S. as "synoptically evident" for severe weather on May 10.[166] A powerful shortwave trough was forecast to move out of the southwestern U.S. into the southern Great Plains during the day, dragging along a portion of the jet stream with winds exceeding 100 kn (120 mph; 190 km/h). The approach of this jet stream was expected to increase the divergence of air aloft, leading to the cyclogenesis of a low-pressure area over the central Mississippi Valley that would track northeast towards the Great Lakes.[167] This weather pattern would lead to the low-pressure system and its associated frontal boundaries moving through an unstable air mass exhibiting wind shear as high as 91 kn (105 mph; 169 km/h), leading to a potentially significant outbreak of severe weather.[166][167] While the SPC initially indicated a Moderate Risk of severe weather for the day for an area centered on the central Mississippi Valley,[167] a High Risk was later delineated for parts of northeastern Missouri and central Illinois in the agency's 13:00 UTC (8:00 a.m. CDT) forecast update as the potential for strong tornadoes became increasingly evident.[168]

At around midnight, a low-pressure area was centered over central Oklahoma and southwestern Kansas, with a warm front extended out towards Chanute, Kansas. Strong 50–60 kn (58–69 mph; 93–111 km/h) winds aloft brought warm and moist air into the region, leading to enhanced convergence of air and fueling thunderstorm development along the warm front.[169] Some of these storms acquired supercell characteristics.[170][171] The intense supercell that had produced the tornadoes in Oklahoma the previous day continued into May 10, accompanied by dew points above 70 °F (21 °C) and a moderately unstable environment characterized by CAPE values between 2500 and 3000 J/kg;[161][172] the storm spawned a final F1 tornado in Creek County at 05:25 UTC (12:25 a.m. CDT) before dissipating.[161] Another pair of F0 tornadoes occurred in Butler at around 08:00 UTC (3:00 a.m. CDT).[19] Widespread thunderstorms were also active early in the morning between Indiana and Pennsylvania in connection with a broad swath of rising air within an unstable air mass with dew points approaching 70 °F (21 °C).[172]

As the warm front over the central U.S. developed further, additional storms initiated over northern Missouri by 11 UTC (6:00 a.m. CDT).[173][168] These storms organized into a mesoscale convective system and tracked east towards central Illinois along and north of the warm front, later developing a mesoscale convective vortex.[174][175] Isolated supercells later developed in the morning over central Illinois and western Indiana, aided by strong winds in the mid-levels of the troposphere and strong wind shear in the lower-levels of the troposphere.[176][177] Eight tornadoes touched down in Illinois and Indiana between 12 and 17 UTC (7 a.m.–12 p.m. CDT); the strongest of these tornadoes was rated F1.[19] The complex of storms also enhanced the advection of warm air downrange farther east, bolstering the development of thunderstorms farther east by destabilizing the local air mass.[178][179] This favorable environment for rising air continued to spread east in tandem with a shortwave trough tracking across the Ohio Valley, extending conducive conditions for thunderstorm development eastward to Virginia and North Carolina in the early afternoon.[180][181] An F3 tornado tracked 25 mi (40 km) across Mason and Lewis counties in Kentucky from 20:45–21:25 UTC (4:45–5:25 p.m. EDT); this was Kentucky's only tornado that day.[19] Clusters of supercells developed and persisted over the Ohio Valley and over Virginia and North Carolina through the afternoon and evening,[182][183] leading the SPC to issue three tornado watches.[184]

A map of severe weather risk regions
The SPC's convective outlook for May 10, indicating a High Risk of severe weather near St. Louis

Farther west, an outflow boundary remained between St. Louis, Missouri and east-central Kansas in the wake of the thunderstorms earlier in the morning, serving as a potential region for rapid thunderstorm development.[185] An atmospheric sounding taken over Oklahoma City at 12 UTC (7 a.m. CDT) indicated that a robust capping inversion was in place over the region, though satellite imagery and radar data also indicated that storms were beginning to develop vertically by around 14:17 UTC (9:17 a.m. CDT).[186] At 16:30 UTC (11:30 a.m. CDT), the SPC expanded the High Risk region to include a wider swath from northeastern Oklahoma to Ohio as confidence increased in an afternoon and overnight tornado outbreak with strong to violent tornadoes materializing.[185][187] As the area of low pressure over the central U.S. intensified, the air mass over eastern Kansas and western Missouri rapidly destabilized at around 17 UTC (12 p.m. CDT).[188]

Warm and moist air also advanced north into southeastern Iowa and western Illinois ahead of the low-pressure region,[189] with conducive conditions for tornadogenesis eventually extending as far north as southern Wisconsin after 23 UTC (6 p.m. CDT) as the low-pressure area quickly strengthened over Iowa.[190] Isolated thunderstorms and towering cumulus clouds began to rapidly form along a dry line over central Oklahoma by around noon, with the local atmospheric conditions supportive of strong tornadoes.[191] Additional supercell thunderstorms quickly emerged over Missouri and eastern Kansas over the next few hours, surrounding by an unstable air mass with CAPE values between 4000 and 5000 J/kg and high wind shear.[192] Though wind shear was high enough to inhibit tornadogenesis, cyclical thunderstorm developments increased the odds of tornadogenesis as the storms tracked east.[193]

At 21:02 UTC (4:02 p.m. CDT), an F0 tornado briefly touched down in Linn County, Missouri.[194] Over the next seven hours, 38 tornadoes were documented across primarily rural areas of Iowa, Illinois, Missouri, and Wisconsin.[19][166] Most of these tornadoes were spawned by nine discrete supercells that formed after 19 UTC (2 p.m. CDT) in western Missouri and southeastern Kansas along the dry line. These afternoon and evening storms were also enhanced by the outflow boundary left behind by the morning storms over Missouri: the boundary created a strong density gradient, increased wind shear, and lowered the height of the lifting condensation level, producing a localized area of heightened favorability for tornado formation.[166][195] Two of the tornadoes—one in Missouri and the other in Illinois—received an F3 rating; these were the highest-rated tornadoes of the day.[19][166] The longest-tracked tornado of the day, rated F2, touched down near Canton, Missouri, and lifted near Lima, Illinois, resulting in a tornadic path length spanning 89 mi (143 km).[166] The supercells persisted overnight, tracking towards the Great Lakes region with the nearby low-pressure area continuing to intensify.[196][197][198] The day's final tornado lifted from Woodford County, Illinois, at 03:35 UTC (10:35 p.m. CDT).[19]

May 11[edit]

Confirmed tornadoes on May 11, 2003
FU F0 F1 F2 F3 F4 F5 Total
0 1 9 2 3 0 0 15

The SPC predicted that the outbreak of severe weather that began on May 10 would continue into May 11, projecting a High Risk of severe weather over parts of Illinois and Indiana that would continue into the morning hours of May 11; additional severe weather was also expected throughout much of the Ohio and Mississippi valleys as the low-pressure system over Iowa intensified. A strong cold front extending south-southwest from the low-pressure area to northwestern Texas was expected to be a catalyst for severe weather as it swept through a moderately unstable air mass with strong winds throughout much of the troposphere.[199][200] Many of the thunderstorms active across the Mississippi Valley towards the end of May 10 began to coalesce into linear complexes of storms towards the end of the day.[201] These storms continued into May 11, developing into a squall line with embedded bow echoes that extended from western Indiana southwestward to the Mississippi River near Memphis, Tennessee. The storms were supported by an unstable air mass with dew points above 70 °F (21 °C) as they tracked east at 40–45 kn (46–52 mph; 74–83 km/h),[202] producing strong winds and tornadoes.[203] According to the National Climatic Data Center, 11 tornadoes touched down in Kentucky and Tennessee between 6–11 UTC (1–6 a.m. CDT), though a 2015 reanalysis conducted by the National Weather Service Nashville, Tennessee, found additional tornadoes that placed the total at 15.[19][204] The first tornado was an F3 tornado that touched down in McLean County, Kentucky, at around 06:18 UTC (1:18 a.m. CDT).[19] There were two other F3 tornadoes in central Tennessee, with one tracking across both Hickman and Williamson counties and the other striking parts of Rutherford County.[204] The squall line persisted into the later part of the morning, moving across eastern Tennessee towards western North Carolina and Virginia.[205]

By around 13:00 UTC (8:00 a.m. CDT), the extratropical cyclone that had intensified over the central and midwestern U.S. over the past day reached the upper Great Lakes region. While the squall line had begun to weaken by this point over the lower Appalachians, the SPC predicted that reintensification of the squall line along Interstate 95 was likely. The agency highlighted a Moderate Risk of severe weather across parts of the Mid-Atlantic states, with damaging winds constituting the primary severe weather threat.[206] Warm advection led to the formation and intensification of isolated storms over New York and Pennsylvania by around 14 UTC (10 a.m. EDT).[207] By 14:30 UTC (10:30 a.m. EDT), clearing skies ahead of an advancing cold front led to rapid destabilization of the air mass over eastern Ohio, western Pennsylvania, western New York, and northern West Virginia, with CAPE values reaching 1000–2000 J/kg amid dew points nearing 70 °F (21 °C).[208] The SPC issued a tornado watch an hour later for this destabilizing region.[209] Another tornado watch, tagged as a Particularly Dangerous Situation, was issued by the SPC at 17:50 UTC (1:50 p.m. EDT) for central New York and central and eastern Pennsylvania as showers began to increase ahead of the approaching cold front.[210]

Although the SPC anticipated a considerable outbreak of severe weather along the strong cold front the day's severe weather was ultimately isolated and limited to parts of New York and Pennsylvania.[200][211] There were only two weak tornadoes on May 11 in connection with the storms that passed through this region: an F0 tornado Lycoming County, Pennsylvania, and an F1 tornado in Wayne County, New York.[19][200] The lack of storm activity despite otherwise conducive atmospheric conditions may have been caused by subsiding air in the mid-levels of the troposphere over the region as a result of convergent winds aloft, limiting the coverage and depth of thunderstorms.[211] The lack of strong thermal gradients where instability was highest also contributed to the lack of severe weather.[211] While the storms that produced the two tornadoes exhibited strong rotation, most storms on May 11 did not produce any substantial severe weather.[200] Unlike in previous days, the day also featured a strong cold front that swept across the U.S., displacing the moist and unstable air mass that had remained over the central and eastern U.S.[2] After May 11, the development of a ridge of high pressure over the Rocky Mountains—as opposed to the persistence of low pressure over the western U.S. in previous days—precipitated the end of the period of severe weather that began on May 3.[3]

Confirmed tornadoes[edit]

Confirmed tornadoes by Fujita rating
FU F0 F1 F2 F3 F4 F5 Total
0 180 121 36 20 6 0 363
Confirmed tornadoes and tornado warnings from
21:00 UTC April 30–19:00 UTC May 11, 2003
Animation showing all confirmed tornadoes and their intensities during the outbreak and tornado warnings issued by the National Weather Service. Concentrations of tornadoes occurred along the Kansas–Missouri border and at the confluence of the Mississippi and Ohio Rivers.
 F0 tornado  F3 tornado
 F1 tornado  F4 tornado
 F2 tornado  Tornado warning

Kansas City metropolitan area[edit]

Kansas City metropolitan area tornadoes
Damages wrought by the tornado in Gladstone, Missouri
Tornadoes
confirmed
5
Max. rating1F4 tornado
Fatalities2 deaths, 67 injuries
Damage$138.5 million (2003 USD)
Power outages33,000
1Most severe tornado damage; see Fujita scale

Northern parts of the Kansas City metropolitan area suffered heavy damage from tornadoes on May 4 in what was considered the most significant outbreak for the region since 1977.[212][213] Five tornadoes occurred in the northland suburbs of Kansas City, of which four were caused by a single supercell; the strongest of these was classified as an F4.[214][215] All flights via Kansas City International Airport were halted and passengers in the terminals were evacuated underground into tunnels for a half-hour.[213] At the height of the storms, the Kansas City Power and Light Company reported that 33,000 of its electricity customers were without power, including Providence Medical Center where 22 persons were treated for injuries.[216] Despite the severity of the tornadoes and the populations affected, Lynn Maximuk of the National Weather Service Weather Forecast Office in Pleasant Hill, Missouri credited the partnerships between the National Weather Service and local emergency and media crews with the relatively low number of casualties.[217]

The first tornado in the Kansas City area touched down in Leavenworth County, Kansas and was first noted by Fort Leavenworth officials at around 3:45 p.m. CDT. Initially, the tornado remained over country but began damaging structures after crossing the Missouri River into Platte County, Missouri near the intersection of Missouri Route 92 and North Farley Road.[215] There, sixteen homes experienced minor damage, with the tornado producing a maximum of F1 damage over its 3 mi (4.8 km)-long and 50 yd (46 m)-wide track.[218][219] North of Route 92, major damage to two barns and nearby damage to trees and fences was assessed by survey crews to have been caused by downburst winds from the parent thunderstorm.[215]

A succession of four tornadoes from the same thunderstorm in Kansas City area began with the touchdown of an F2 tornado in southern Leavenworth County at approximately 3:54 pm. CDT. The 6 mi (9.7 km)-long damage path extended from northwest of Linwood, Kansas to the south of Basehor, Kansas, with the worst damage occurring to homes near the intersection of 166th Street and Kansas Road.[215] Two people were injured by the tornado.[220] The second tornado—the strongest of the Kansas City tornadoes—began north-northwest of the Kansas Speedway at 3:54 pm. CDT in Wyandotte County, Kansas, initially producing F0–F1 damage. However, the tornado quickly grew in size and intensity, causing F3 damage to two homes south of Parallel Parkway near Interstate 435 and expanding to a width of over 500 yd (460 m). Low-end F4 damage was observed near the intersection of 91st Street and Leavenworth Road; one fatality occurred nearby within a region of F2–F3 damage. The tornado continued into the northeastern portions of Wyandotte County where the twister produced a second region of low-end F4 damage near 79th Street and Cernech Road. Four 150 ft (46 m)-tall metal power poles built to withstand winds in excess of 200 mph (320 km/h) were damaged there. The tornado remained damaging but weakened over the remainder of its path, causing F1–F2 damage along the Missouri River across both Wyandotte County and Platte County in Missouri. The tornado crossed into Platte County near Riverside and Parkville, Missouri at around 4:30 p.m. where it caused damage over a narrower expanse to commercial areas. F1-rated damage was observed after the tornado crossed Interstate 635 before lifting east of the highway at 4:42 pm. CDT in Clay County, Missouri.[215] Overall, the F4 tornado killed two people and injured another thirty; one woman succumbed to her injuries seven months later. Communities in its path incurred a $47.5 million damage toll to property, of which $32 million occurred in Wyandotte County and $15.5 million occurred in Platte County. A total of 83 buildings were destroyed and another 582 sustained at least some degree of damage.[221][222]

A new circulation developed northeast of the first F4 tornado and developed into another F4 tornado that impacted the Gladstone, Missouri area between 4:45–5:00 pm. CDT. Initial damage was wrought to tree and roofs near Shady Lane and Antioch Road, with the severity rated F1. Intensification was quick thereafter, with marginal F4 damage noted in the Carriage Hills subdivision.[215] Roofs and windows were damaged and business signage were destroyed.[216] The tornado continued towards the northeast, causing F1–F3-rated damage before dissipating near Interstate 435;[215] the total damage toll amounted to $31 million and 13 people were injured.[223] The final tornado in the Kansas City region on May 4 impacted the Liberty, Missouri area and was the costliest of those in the metropolitan area. Rated F2, the tornado caused substantial damage at William Jewell College and at locales near downtown Liberty before lifting around 5:15 pm. CDT over rural areas of Clay County.[215] The most severe damage covered a swath that included eastern parts of the college campus and areas along Excelsior Springs Road,[224] with the overall damage cost totaling $60 million.[225]

Pierce City–Battlefield, Missouri[edit]

Pierce City–Battlefield, Missouri
F3 tornado
Max. rating1F3 tornado
Fatalities3
1Most severe tornado damage; see Fujita scale

In Pierce City, Missouri, two people were killed following the collapse of a National Guard Armory.[226] One person was killed and widespread damage occurred near the Clever and Billings communities of Christian County, Missouri.[227] Significant damage occurred to infrastructure in Battlefield, Missouri, including damage to 400–500 homes. The city's fire station collapsed due to the tornado.[228] Downed power lines forced the closure of roads leading to Republic, Missouri.[226]

Stockton, Missouri[edit]

Stockton, Missouri
F3 tornado
Max. rating1F3 tornado
Fatalities3 deaths, 37 injuries
Damage$49 million (2003 USD)
1Most severe tornado damage; see Fujita scale

At 5:31 pm. CDT (22:31 UTC), a tornado began near Liberal, Missouri.[229] As it moved northeast across Barton County, it uprooted numerous trees and produced F1 damage to outbuildings. The tornado entered Cedar County and progressed north of Jericho Springs where it destroyed a mobile home consistent with F2 intensity. The tornado remained over generally rural areas and caused solely tree and power line damage prior to reaching the intersection of Highway Z and County Road 825. There, a well-built frame home and two nearby outbuildings were completely destroyed, with their debris scattered across the adjacent roadway. Damage at this location warranted an F3 rating. Continuing northeast, the storm grew to between 0.5–0.75 mi (0.80–1.21 km) wide and entered downtown Stockton.[230] In the city, 350 structures were demolished while an additional 650 received major damage.[231] Numerous vehicles were flipped and tossed, including two cars from a local dealership which were blown approximately one block to the northeast of their original location. Damage was consistent with an upper-end F3 here.[230] Three people died in Stockton: one man died after being struck by flying debris after his frame house was destroyed, one man died after being struck by flying debris after leaving his home during the tornado's approach, and one man died after refusing to seek shelter in his basement. Thirty-seven others were injured.[231]

Franklin, Kansas[edit]

Franklin, Kansas
F4 tornado
Tornado near Franklin
Max. rating1F4 tornado
Fatalities4 fatalities, 20 injuries
1Most severe tornado damage; see Fujita scale

A large tornado touched down in Neosho County, Kansas at 4:32 pm on May 4. The tornado was initially about 250 yards (230 m) wide and produced F2 damage as it crossed into Crawford County. Aerial damage surveys indicate an increase in width and intensification as the tornado approached the community of Ringo (5 miles (8 km) east of Girard), in Crawford County. Dramatic scouring of the ground was observed, homes were swept from their foundations, and heavy objects such as vehicles were tossed long distances (over 100 yards (90 m)). The NWS described the damage in this portion of the track as "high-end F4", though it is speculated that the tornado could have reached F5 intensity in this area. As it passed Ringo and entered the unincorporated town of Franklin (5 miles (8 km) north of Frontenac), the path reached over 12 mile (0.8 km) wide at points. Major devastation occurred in Franklin, as numerous buildings and homes were demolished, with some swept away. and Three people were killed in town, and 20 others were injured. The tornado continued producing "high end F4" damage to homes as it passed the town of Mulberry, where a train was derailed from the winds of the storm, and crossed into Barton County, Missouri. In Missouri, the twister demolished several farm houses, killing an 88-year-old man. Some of the homes were swept completely away. Its path began to narrow several miles into Missouri; video and eyewitness accounts suggest that the tornado was "roping out" at this point. It finally lifted to the north of Liberal, Missouri after having traveled for approximately 35 miles (56 km). Almost immediately after the Franklin tornado lifted, a second large tornado was reported to have touched down on the east side of Liberal. The Franklin tornado was covered on an episode of The Weather Channel's Storm Stories, and was described by meteorologist Jim Cantore as "one of the most violent tornadoes ever caught on film- a twister that would shred southeast Kansas".[citation needed]

Denmark-Jackson-Oak Grove-Westover-Northwestern Lexington, Tennessee[edit]

Denmark-Jackson-Oak Grove-Westover-Northwestern Lexington, Tennessee
F4 tornado
Max. rating1F4 tornado
Fatalities11 deaths, 86 injuries
1Most severe tornado damage; see Fujita scale

This strong and deadly F4 tornado would touch down in Madison County, Tennessee just north of the small community of Mercer and would track in a east-northeasterly direction, the then tornado struck the small rural community of Denmark in the southwestern part of the county. As the tornado headed for Jackson, the twister struck the McKeller-Sipes Regional Airport. The tornado then struck Oak Grove and Westover. The tornado then struck Jackson at F4 intensity. The tornado exited the town where it passed near several small communities. After tracking for 39 miles the F4 would dissipate over the northwestern edge of Lexington. The F4 would result in 11 deaths and 86 injuries, at peak width the tornado would grow to a peak width of 880 yards (0.5 miles) wide

Oklahoma City, Oklahoma[edit]

Oklahoma City, Oklahoma
F4 tornado
Radar shot of the Moore/Oklahoma City supercell at its peak intensity in southeastern OKC
Max. rating1F4 tornado
Fatalities134 injuries
Damage$370.5 million (2003 USD) [232][233][234]
1Most severe tornado damage; see Fujita scale

Four years after an F5 tornado caused incredible damage across much of the Oklahoma City metropolitan area during the 1999 Oklahoma tornado outbreak, another strong tornado affected the area. The storm responsible for the tornado developed across Grady County during the mid-afternoon hours and produced a weak tornado near Newcastle and west of Moore. Just after 5:00 pm, a new tornado touched down on the west side of Moore west of Interstate 35 and moved east northeast across the city; the tornado proceeded to cause damage across southeastern sections of Oklahoma City, including Tinker Air Force Base near Interstate 40, and also near Midwest City and Choctaw.[235] Despite extensive damage along the path, no fatalities were caused by the tornado, although dozens of injuries were reported across Cleveland and Oklahoma Counties.

Extensive damage was widespread across the southeastern Oklahoma City metro area

Within Moore city-limits, the peak damage caused near the center of the tornado was mostly rated as F2, although a few isolated locations received F3-rated damage; F3 damage in Moore was observed near 12th Street where several businesses, two hotels, an office building, a church, several restaurants, a child center and a Headstart Program building were either severely damaged or destroyed. The tornado also damaged numerous homes in the Highland Park subdivision which was mostly destroyed by the F5 tornado which passed just a few blocks north of the May 8, 2003, tornado. Other homes on the north side of the city also sustained significant damage before the tornado crossed the Cleveland-Oklahoma county line.[235]

In the Oklahoma City area, the General Motors Oklahoma City Assembly sustained major damage as did as a manufacturing plant near Interstate 240 where F4 damage was observed. Several other businesses were either damaged or destroyed. At Tinker Air Force Base, a storage bunker and several fences were damaged. Several subdivisions in eastern Oklahoma City, Choctaw and Midwest City were also affected by the tornado with several homes sustaining significant damage.[235]

Other regions[edit]

Several cities in the Ozarks region were impacted by tornadoes on the evening of May 4.[226] More than 100 buildings in Crawford County, Missouri were damaged.[216]

Non-tornadic impacts[edit]

Southeastern United States[edit]

Aerial view of flooded businesses along a thoroughfare.
Flooding in Chattanooga, Tennessee along the banks of South Chickamauga Creek

Accompanying the record period of tornadic activity was a significant flood event that impacted parts of the Southeastern United States. A stagnation of the typical eastward movement of storm systems across the United States resulted in the stalling of a warm front over Tennessee, keeping the region in a moist air mass with dew point temperatures above 60 °F (16 °C)—characteristic of highly moisture-laden air.[236] The floods lasted for eight days, affecting a 272,100 km2 (105,100 sq mi) area and displacing 2,000 people.[237]

Rains in southeastern Tennessee beginning on April 30 saturated surfaces and elevated river levels, amplifying a period of heavy precipitation beginning on May 5 that featured repeated passages of thunderstorms over the same areas.[19] The positioning of a high pressure area over the western Atlantic maintained a southerly wind throughout the region, producing a prolonged flow of moisture from the Gulf of Mexico.[236] During the following five days, over 9 in (230 mm) of rain would fall across the watersheds of the Little Tennessee and Hiwassee rivers, including more than 12 in (300 mm) of rainfall reported over a 35-hour span in McMinn County. The nearby South Chickamauga Creek in Chattanooga reached a record crest of 29.32 ft (8.94 m) on May 8. The resulting damage in the Chattanooga area from the swollen tributaries was evaluated at $20 million. The Tennessee River at Chattanooga reached a stage of 36.1 ft (11.0 m), within a foot of the record high set in February 1973; riverside flooding prompted the evacuation or rescue of hundreds of individuals from adjacent counties and along its tributaries.[19] Similar impacts were felt in West and Middle Tennessee, necessitating a 20-county presidential disaster declaration due the floods, tornadoes, and associated severe weather. Flooding along Saunders Fork Creek in Cannon County resulted in the deaths of three people in two vehicles.[238] Another fatality occurred after a driver and their vehicle went airborne in crossing a washed out section of road in Wayne County; a total of 18 roads and bridges were washed out by the flooding in the county. The floods in Wayne County also inundated 100 homes, resulting in the rescue of 50 people.[239]

Flood impacts extended southward from Tennessee. Drawing moisture from the moist tropical air mass, thunderstorms associated with the severe weather outbreak on May 7 produced torrential precipitation over Alabama. Northern and northeastern areas of the Greater Birmingham area of Alabama experienced up to 11 in (280 mm) of rainfall from several storms over the course of a few hours on May 7, resulting in historic flooding.[240] Radar estimates suggested that as much as 5–8 in (130–200 mm) fell in some locations in one hour. Throughout Jefferson County—which includes Birmingham—at least 120 thoroughfares were blocked by floodwaters. All roadways in Leeds and Brookside were flooded. Many schools and homes were also inundated, resulting in several rescues and evacuations. Total property damage in the county alone reached $1 billion.[241] Rivers swelled downstream from the accumulated rainfall, impacting areas not directly affected by the storms. An elevated Tallapoosa River nearly isolated Wadley, Alabama, with Alabama State Route 22 connecting Wadley to points east becoming fully submerged.[240] Across Central Alabama, the Red Cross reported damage to more than 700 homes.[242] Due in part to the heavy rains between May 4–8, May 2003 was the wettest month for Huntsville since 1983.[243]

A map of rainfall totals across the United States.
Heavy rainfall on May 6 straddled the southern Tennessee border, impacting much of the Tennessee River basin.

The same storms produced heavy rainfall across the northern and central portions of Georgia. With soils saturated from prior rains, the prolonged precipitation period produced seasonally anomalous runoff that flowed into creeks and rivers, resulting in rapid rises of streams and associated rivers, including Chickamauga Creek, Conasauga River, Chattahoochee River, Flint River, and Sweetwater Creek. Near West Point, the Chattahoochee River rose to 23.2 ft (7.1 m), reaching its highest levels since 1961.[244] The flooding washed out roads, damaged at least 200 residential buildings, and inundated numerous businesses. Two people were killed in the state as a result of the floods overtaking their vehicles.[245][246] Much of Georgia was also impacted earlier by widespread severe weather on May 2, with large hail or wind damage reported in most counties beginning in the afternoon hours. The primary impacts transitioned from hail to strong downbursts after sunset as what ultimately became a singular line of storms tracked southward. The largest hail of the day—approximately the size of baseballs—occurred near Trion in Chattooga County.[247]

Severe weather swept across South Carolina on May 6, concentrated in two waves of thunderstorms organized in a mesoscale convective system.[248][249] The complex originated over northern Georgia and persisted within an unstable airmass.[249] Storm activity resulted in golf-ball-sized hail in four counties while strong winds caused some scattered tree and building damage.[248] A macroburst in McCormick County destroyed a mobile home and damaged several others due to falling trees, resulting in $80,000 in damage.[250] On May 9, storms in North Carolina near the state border with Virginia produced large hail and strong winds, cutting power to 1,900 customers of Progress Energy Inc.[251] Hail as large as 4.25 in (108 mm) in diameter was documented in Northampton County, damaging vehicles and homes.[252]

A pair of damaging hailstorms impacted the Paducah, Kentucky area on May 4. The first took a path from near Cairo, Illinois to Lake Barkley in Kentucky and dropped hail as large as 2.75 in (70 mm) in diameter near Calvert City, Kentucky, breaking windshields and denting vehicles.[253] Minor damage was inflicted to the roofs of hundreds of homes.[254] One person was injured in Paducah by the hailstorm; this was the first reported hail-related injury in the warning area of National Weather Service Paducah, Kentucky since 1994.[255] Causing tens of millions of dollars in damage, the hailstorm was one of the most destructive in far western Kentucky's history; the damage toll included $10 million in damage for Marshall County, Kentucky and $20 million in damage in nearby Massac County, Illinois.[254] The second storm produced hail from Pope County, Illinois to McLean County, Kentucky. The storms were complemented by other hailstorms, albeit less significant, across the region.[253] Thunderstorms in the Louisville area cut power to 24,000 homes and businesses.[256] On May 5, heavy rains impacted areas of northeastern Kentucky, resulting in flooding along the banks of Tygarts Creek and the Little Sandy River; the floods caused $1.3 million in damage.[257]

In addition to an F0 tornado-producing storm in the Northern Virginia, a second severe thunderstorm producing strong winds caused damage in the Virginian suburbs of Washington, D.C. on May 7, downing power lines and trees in Fairfax County and near Falls Church. A microburst with winds of up to 70 mph (110 km/h) downed trees in eastern Warrenton.[258] The same storms persisted into southern Maryland, downing trees in the La Plata area and St. Mary's County.[259] On May 8, a fast-moving thunderstorm caused a power outage affecting 4,100 people in Gloucester County, Virginia, felling trees and downing power lines.[260] Several damaging severe thunderstorms tracked across Virginia on the following day, producing winds as high as 92 mph (148 km/h) as measured in Centenary. In addition to damage to infrastructure, one person was killed by a fallen tree in Arvonia.[261] In West Virginia, storms along and south of a warm front produced severe weather and flooding rains, particularly in the Little Kanawha River watershed. Overflowed banks resulted in inundation in some areas of Webster, Braxton, and Randolph counties, resulting in over $1 million in damage.[262] Strong thunderstorm winds in Greenbrier County felled trees and power lines, resulting in one injury.[263]

Midwestern United States[edit]

Satellite image of an expansive cloud system over North America characterized by a cyclone near the center of the image and a line of clouds emanating downwards from the cyclone.
A strong cold front associated with a low-pressure area near the Great Lakes produced damaging winds across the Midwest on May 11

Large hail and strong winds were reported across south-central Nebraska on May 4, including gusts as strong as 80 mph (130 km/h) north of Pauline. Hailstorms in the state that day collectively caused about $1.3 million in damage, including the loss of inventory at two car dealerships in the Holdrege area.[264] Softball-sized hail damaged cars and homes near Offutt Air Force Base.[256] Kansas was also impacted by hail and strong winds, resulting in downed power lines.[265] Four days later, 38 freight cars on a BNSF Railway in Chase County, Kansas were derailed by thunderstorm winds, including one car filled with sulfur dioxide. The chemical release prompted the evacuation of about 250 residents and six firemen and law enforcement personnel were treated for respiratory ailments caused by the compound.[266]

Exacerbating the significant tornado outbreak, storms along the dry line in Missouri also produced widespread hail on May 4, peaking at 3.50 in (89 mm) near Gladstone.[267] Another bout of storms two days later caused flooding in northern Jefferson County, submerging roads and resulting in one death.[268] De Soto was particularly hard hit, with a school severely damaged by straight-line winds alongside downed trees and power lines.[269][270] Wind gusts in the De Soto storm were estimated to have been near 100 mph (160 km/h), destroying 6 single-family homes and inflicting major damage to 27.[271] Flooding was also reported in Phelps County and washed out roads in Laclede County, in addition to producing small hail and minor damage to infrastructure.[272][273] More severe storms struck the state two days later;[274] in Bates County, hail as large as 4 in (100 mm) damaged 1,100 homes and 750 cars, resulting in a $6.75 million damage toll.[275] A wind gust of 104 mph (167 km/h) was measured at Whiteman Air Force Base,[276] though the site did not sustain any damage.[277] Wind gusts estimated at 85 mph (137 km/h) produced a swath of damage in the Hallsville and Centralia areas, damaging four mobile homes and injuring one person.[278] One person was killed on May 9 after attempting to traverse a low-water crossing in Monroe County.[279] The following day, severe storms in the St. Louis area disrupted power to 10,000 electricity customers and caused flashed flooding in the region.[280]

The SPC predicted the potential for severe winds for a large portion of the Ohio River Valley for the evening of May 10 and early morning hours of May 11

The repeated storm activity brought frequent thunderstorms over Iowa, causing intermittent periods of heavy rainfall and flooding. The heaviest rainfall occurred on May 4, when Des Moines set a rainfall record for the day with 2.73 in (69 mm) being reported. Some roads were flooded in the city's metropolitan area with flash flooding occurring in some counties, though the precipitation was overall beneficial for the state's agricultural interests and water supplies.[281] The storms on May 4 also produced scattered hail with sizes generally between 0.25–1 in (6.4–25.4 mm) across the state.[282] Behind one line of storms, the development of a low-pressure area in their wake produced a swath of 50 mph (80 km/h) winds across eastern Iowa and northern Illinois, doing at least $2 million in damage.[283] A significant hail event took place in eastern Iowa on May 8, additionally affecting northern Missouri and northern Illinois. A car dealership in Fort Madison, Iowa reported damage to 400 cars in the city's largest hail event since 1993. Three schools and a golf course were heavily damaged on the south side of Burlington, Iowa;[284] classes were cancelled at those schools following rainwater intrusion via holes created by hail.[285] The hail caused $38 million in damage across eastern Iowa and $12 million in damage across northwestern Illinois.[284][286] Flash flooding that same day in Jersey County, Illinois resulted in one fatality.[287] Late on May 9, a cluster of thunderstorms produced a gravity wave that resulted in a damaging and narrow band of strong winds that downed trees and power lines, causing a power outage that affected 2,000 people primarily in Freeport, Illinois.[288] Additional storms produced similar impacts in northeastern Illinois on May 11,[289][290] leaving 30,000 people without power.[291]

On May 11, the passage of a strong cold front caused widespread wind damage across northern Ohio. Several weather stations recorded gusts in excess of 40 mph (64 km/h), resulting in scattered power outages and downed trees and utility poles throughout the region.[292] Similar effects were felt in Indiana, Michigan, and Wisconsin as a result of the frontal passage;[19] in Indiana, 12,000 households were without power during the strongest winds.[19] Several roads were closed due to vehicle accidents or obstructing debris.[293] Some overpasses in Allen Park, Michigan were flooded after a fallen light pole cut power to a storm pump station. Strong winds also indirectly caused the leakage of hydrochloric acid from a plant in Ypsilanti, Michigan after roofing knocked loosed by the wind broke a distribution pipe.[294]

South-Central Plains[edit]

Throughout the severe weather outbreak, the National Climatic Data Center documented 249 hail events and 42 thunderstorm winds in the state of Oklahoma.[295] Eastern Oklahoma was impacted by tornadoes and strong thunderstorms on May 4. Strong winds reportedly tumbled four to six rail cars near Alderson and destroyed two mobile homes 1 mi (1.6 km) north of Fairland. Blown-down trees were documented across several counties as a result of the strong winds. Choteau, Jay, and Grove sustained the brunt of power outages that affected 1,500 energy customers.[296] At Grand Lake, several boat docks were damaged and between 150 and 200 trees were blown down by winds estimated at 80 mph (130 km/h), resulting in $100,000 in damage.[297][298] The storms in central Oklahoma on May 8 cut power to 37,000 homes and businesses according to Oklahoma Gas & Electric, including half of Pawhuska, Oklahoma.[299]

Aftermath[edit]

FEMA Disaster Declarations
ID State Declared Aid approved Notes
DR-1462 Kansas May 5 $8.67 million [300]
DR-1463 Missouri May 5 $28.3 million [301]
DR-1464 Tennessee May 8 $61 million [302]
DR-1465 Oklahoma May 10 $6.67 million [303]
DR-1466 Alabama May 12 $62.6 million [304]
DR-1469 Illinois May 15 $1.64 million [305]
DR-1470 Mississippi May 23 $740,552 [306]
Photograph of a crowd of adults and children at a school gymnasium. George W. Bush is at the center of the image.
President George W. Bush visiting Pierce City, Missouri following the tornado outbreak

In the aftermath of the May 4 tornadoes, Missouri governor Bob Holden petitioned the federal government to declare a federal disaster for 39 counties while Kansas governor Kathleen Sebelius issued disaster or emergency declarations for several counties—Cherokee, Crawford, Labette, Leavenworth, Neosho, and Wyandotte;[213][307] U.S. President George W. Bush later issued federal disaster declarations for these states, authorizing the allocation of federal disaster funds through the Federal Emergency Management Agency (FEMA).[308][309] FEMA director Michael D. Brown designated Michael J. Hall as the coordinator for federal relief efforts in response to the tornadoes.[309]

Visiting the Northmoor, Missouri, Holden remarked that the damage was "the worst I've seen from a tornado in several years,"[216] later noting in during his visit of Pierce City that the May 4 storms were "the most devastating series of tornadoes we've ever had in the state of Missouri."[310] Emergency shelters were opened in Madison County, Tennessee as the county largely lost access to electricity and water following a May 4 tornado.[311] The American Red Cross of Central Oklahoma sent relief crews and emergency response trucks to Springfield, Missouri to deliver food and supplies. The Oklahoma City chapter of Feed the Children also dispatched supplies to Kansas City, Missouri.[312] The 203rd Engineer Battalion of the Missouri Army National Guard bound for deployment in the Iraq War aided relief efforts in Pierce City, Missouri.[313]

In 2004, The Storm Prediction Center and five National Weather Service Weather Forecast Offices were awarded the Department of Commerce Gold Medal—the highest award issued by the department—for "providing life-saving services during a record outbreak of tornadoes during the period of May 4–6, 2003."[314]

See also[edit]

Notes[edit]

  1. ^ a b A significant tornado is one that is rated F2 or higher on the Fujita scale.[1]
  2. ^ The Storm Prediction Center used a three-tier scale in their convective outlooks to categorize the coverage and intensity of severe weather, with slight (SLGT) risk having the lowest coverage and severity, followed my moderate (MDT) and high (HIGH) with the highest coverage and severity. All risks imply that well-organized severe thunderstorms are anticipated.[8]

References[edit]

  1. ^ Thompson, Richard L.; Smith, Bryan T.; Grams, Jeremy S.; Dean, Andrew R.; Broyles, Chris (October 2012). "Convective Modes for Significant Severe Thunderstorms in the Contiguous United States. Part II: Supercell and QLCS Tornado Environments" (PDF). Weather and Forecasting. 27 (5). American Meteorological Society: 1136–1154. Bibcode:2012WtFor..27.1136T. doi:10.1175/WAF-D-11-00116.1. S2CID 14368445. Retrieved May 15, 2019.
  2. ^ a b c d e f g Hamill, Thomas M.; Schneider, Russell S.; Brooks, Harold E.; Forbes, Gregory S.; Bluestein, Howard B.; Steinberg, Michael; Meléndez, Daniel; Dole, Randall M. (April 2005). "The May 2003 Extended Tornado Outbreak". Bulletin of the American Meteorological Society. 86 (4). American Meteorological Society: 531–542. Bibcode:2005BAMS...86..531H. doi:10.1175/BAMS-86-4-531. S2CID 122031474.
  3. ^ a b c d e f g h Record Tornado Outbreaks of May 4–10, 2003 (PDF) (Report). Service Assessment. National Oceanic and Atmospheric Administration. December 2003. Retrieved May 27, 2019.
  4. ^ Schneider, Russell S.; Brooks, Harodl E.; Schaefer, Joseph T. Tornado Outbreak Sequences: Historic Events and Climatology (1875–2003) (PDF). 22nd Conference on Severe Local Storms. Norman, Oklahoma: Storm Prediction Center. Retrieved June 5, 2019.
  5. ^ National Climatic Data Center (January 2012). State of the Climate: Tornadoes for Annual 2011. Climate Monitoring (Report). State of the Climate. National Centers for Environmental Information. Retrieved May 16, 2019.
  6. ^ National Climatic Data Center (2019). "Weather and Climate Billion-Dollar Disasters to affect the U.S. in 2003 (CPI-Adjusted)". Billion-Dollar Weather and Climate Disasters: Table of Events. National Centers for Environmental Information. Retrieved May 16, 2019.
  7. ^ Dial (May 4, 2003). May- 4-2003 2000 UTC Day 1 Convective Outlook (Report). Storm Prediction Center. Retrieved May 21, 2003.
  8. ^ "SPC Convective Outlook Guidelines" (PDF). Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021.
  9. ^ SPC Day 1 Convective outlooks for May 3, 2003:
  10. ^ a b Edwards, Roger (May 3, 2003). May- 3-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021.
  11. ^ Evans, Jeffry A. (May 3, 2003). "Severe Thunderstorm Watch Number 219". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  12. ^ Evans, Jeffry A. (May 3, 2003). "Tornado Watch 220". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  13. ^ Evans, Jeffry A. (May 3, 2003). "Tornado Watch 222". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  14. ^ Banacos, Peter C. (May 3, 2003). "Mesoscale Discussion 0706". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  15. ^ Thompson, Rich (May 3, 2003). "Tornado Watch 224". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  16. ^ Edwards, Roger (May 3, 2003). May- 4-2003 0100 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021.
  17. ^ Thompson, Rich (May 4, 2003). "Tornado Watch 227". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  18. ^ a b "20030503's Storm Reports". Norman, Oklahoma: Storm Prediction Center. May 3, 2003. Retrieved December 20, 2021.
  19. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj National Oceanic and Atmospheric Administration (May 2003). Angel, William; Hinson, Stuart; Mooring, Rhonda (eds.). "Storm Data and Unusual Weather Phenomena" (PDF). Storm Data. 45 (5). Asheville, North Carolina: National Climatic Data Center. Archived from the original (PDF) on May 15, 2019. Retrieved May 15, 2019.
  20. ^ Event Report for F0 Tornado in Scotts Bluff County, Nebraska. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved December 20, 2021.
  21. ^ Event Report for F2 Tornado in Haskell County, Texas. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved December 20, 2021.
  22. ^ "20030504's Storm Reports". Norman, Oklahoma: Storm Prediction Center. May 4, 2003. Retrieved December 21, 2021.
  23. ^ a b "NWS Nashville Tornado Database". Mississippi State University. Retrieved June 2, 2019.
  24. ^ Doswell, C. A.; Edwards, R.; Thompson, R. L.; Hart, J. A.; Crosbie, K. C. (December 1, 2006). "A Simple and Flexible Method for Ranking Severe Weather Events". Weather and Forecasting. 21 (6). American Meteorological Society: 939–951. Bibcode:2006WtFor..21..939D. doi:10.1175/WAF959.1.
  25. ^ Gilmore, William T.; Fox, Neil I. (October 28, 2005). Observations of Supercell Merger and Tornadogenesis From May 4, 2003 (PDF). 32nd Conference on Radar Meteorology. Albuquerque, New Mexico: American Meteorological Society. Retrieved December 21, 2021.
  26. ^ a b c d Bookbinder, Evan M.; Browning, Wes D. (October 7, 2004). A Mesoscale Re-analysis of Anticipated Severe Weather Threats in the Ozarks During the Week of May 4th-10th 2003 (PDF). 22nd Conference on Severe Local Storms. National Weather Service Springfield, Missouri. CiteSeerX 10.1.1.538.1317. Retrieved December 21, 2021 – via CiteSeerX.
  27. ^ Corfidi, Stephen F. (May 3, 2003). May- 3-2003 0800 UTC Day 2 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021.
  28. ^ Edwards, Roger; Naden, Richard (May 4, 2003). May- 4-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021.
  29. ^ a b Kerr, Brynn W. (May 4, 2003). "Mesoscale Discussion 0726". Norman, Oklahoma: Storm Prediction Center. Retrieved December 21, 2021 – via Iowa Environmental Mesonet.
  30. ^ Evans, Jeffry A. (May 4, 2003). "Tornado Watch 231". Norman, Oklahoma: Storm Prediction Center. Retrieved December 20, 2021 – via Iowa Environmental Mesonet.
  31. ^ Evans, Jeffry A. (May 4, 2003). "Tornado Watch 232". Norman, Oklahoma: Storm Prediction Center. Retrieved December 21, 2021 – via Iowa Environmental Mesonet.
  32. ^ Evans, Jeffry A. (May 4, 2003). "Tornado Watch 233". Norman, Oklahoma: Storm Prediction Center. Retrieved December 21, 2021 – via Iowa Environmental Mesonet.
  33. ^ Thompson, Richard (May 4, 2003). "Mesoscale Discussion 0734". Norman, Oklahoma: Storm Prediction Center. Retrieved December 21, 2021 – via Iowa Environmental Mesonet.
  34. ^ Event Report for F0 Tornado in Scott County, Nebraska. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved December 21, 2021.
  35. ^ a b c d e f g h i j k l m McCarthy, Daniel; Schaefer, Joseph T. (March 2004). "A Record May Leads the Way Tornadoes of 2003". Weatherwise. 57 (2). Philadelphia, Pennsylvania: Taylor & Francis Group: 46–55. doi:10.1080/00431670409605439. S2CID 191656468.
  36. ^ Evans, Jeffry A. (May 4, 2003). "Tornado Watch 234". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  37. ^ Thompson, Rich (May 4, 2003). "Tornado Watch 239". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  38. ^ Mead, Corey (May 5, 2003). May- 5-2003 0100 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 21, 2021.
  39. ^ Thompson, Richard A. (May 4, 2003). "Mesoscale Discussion 0743". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  40. ^ a b Howell, Jonathan L.; Garrett, Gregory R.; McNeil, Scott J.; Valle, Daniel N. (October 2004). Memphis National Weather Service Perspective of the Severe Weather Outbreak of May 2003: Focus on the F4 Madison County, Tennessee Tornado (PDF) (Report). Memphis, Tennessee: National Weather Service Memphis, TN. Retrieved December 21, 2021.
  41. ^ SPC tornado watches with expiry times during the early morning of May 5:
    • Thompson, Rich (May 5, 2003). "Tornado Watch 240". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
    • Corfidi, Stephen F. (May 5, 2003). "Tornado Watch 243". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
    • Corfidi, Stephen F. (May 5, 2003). "Tornado Watch 244". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
    • Corfidi, Stephen F. (May 5, 2003). "Tornado Watch 245". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
    • Corfidi, Stephen F. (May 5, 2003). "Tornado Watch 247". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  42. ^ Goss, Steve (May 5, 2003). "Mesoscale Discussion 0754". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  43. ^ Goss, Steve (May 5, 2003). "Mesoscale Discussion 0757". Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021 – via Iowa Environmental Mesonet.
  44. ^ Corfidi, Stephen F. (May 4, 2003). May- 4-2003 0800 UTC Day 2 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021.
  45. ^ a b c McCarthy, Daniel (May 5, 2003). May- 5-2003 1630 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 22, 2021.
  46. ^ a b Imy, David A. (May 5, 2003). May- 5-2003 2000 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021.
  47. ^ Edwards, Roger (May 5, 2003). May- 5-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021.
  48. ^ a b "20030505's Storm Reports". Norman, Oklahoma: Storm Prediction Center. May 3, 2003. Retrieved December 20, 2021.
  49. ^ Hales, John E. (May 5, 2003). "Mesoscale Discussion 0758". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  50. ^ Hales, John E. (May 5, 2003). "Mesoscale Discussion 0763". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  51. ^ Event Report for F3 Tornado in Lincoln County, Tennessee. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved December 23, 2021.
  52. ^ Jewell, Ryan (May 5, 2003). "Mesoscale Discussion 0758". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  53. ^ Event Report for F1 Tornado in Oakland County, Michigan. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved January 4, 2022.
  54. ^ "May 5, 2003 Southeast Michigan Severe Weather Episode". White Lake, Michigan: National Weather Service Detroit/Pontiac, Michigan. Retrieved December 23, 2021.
  55. ^ Hales, John E. (May 5, 2003). "Mesoscale Discussion 0758". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  56. ^ Kerr, Brynn W. (May 5, 2003). "Mesoscale Discussion 0775". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  57. ^ Kerr, Brynn W. (May 5, 2003). "Mesoscale Discussion 0777". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  58. ^ Mead, Corey (May 6, 2003). May- 5-2003 2000 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021.
  59. ^ Mead, Corey; Jewell, Ryan (May 6, 2003). May- 5-2003 2000 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021.
  60. ^ Corfidi, Stephen A. (May 6, 2003). "Tornado Watch 261". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  61. ^ Corfidi, Stephen A. (May 6, 2003). "Tornado Watch 262". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  62. ^ Edwards, Roger (May 6, 2003). "Mesoscale Discussion 0780". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  63. ^ Edwards, Roger (May 6, 2003). "Mesoscale Discussion 0781". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  64. ^ Gatlin, Patrick N.; Goodman, S. J. (October 7, 2004). Signatures in Lightning Activity during Tennessee Valley Severe Storms of 5-6 May 2003 (PDF). 22nd Conference on Severe Local Storms. American Meteorological Society. Retrieved December 24, 2021.
  65. ^ Taylor, Sarah J. (May 6, 2003). "Mesoscale Discussion 0786". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  66. ^ Edwards, Roger (May 6, 2003). "Mesoscale Discussion 0783". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  67. ^ Broyles, Chris (May 6, 2003). "Mesoscale Discussion 0784". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  68. ^ Broyles, Chris (May 6, 2003). "Mesoscale Discussion 0785". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  69. ^ Taylor, Sarah J. (May 6, 2003). "Mesoscale Discussion 0791". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  70. ^ Darrow, Mark (May 6, 2003). May- 6-2003 1630 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021.
  71. ^ Broyles, Chris (May 6, 2003). "Mesoscale Discussion 0787". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  72. ^ a b Broyles, Chris (May 6, 2003). "Mesoscale Discussion 0789". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  73. ^ a b Taylor, Sarah J. (May 6, 2003). May- 6-2003 2000 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021.
  74. ^ Evans, Jeffry A. (May 6, 2003). "Tornado Watch 273". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  75. ^ Broyles, Chris (May 6, 2003). "Mesoscale Discussion 0799". Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021 – via Iowa Environmental Mesonet.
  76. ^ Thompson, Rich (May 6, 2003). "Tornado Watch 275". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  77. ^ Kerr, Brynn W. (May 6, 2003). "Mesoscale Discussion 0801". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  78. ^ Kerr, Brynn W. (May 6, 2003). "Mesoscale Discussion 0807". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  79. ^ Kerr, Brynn W. (May 6, 2003). "Mesoscale Discussion 0810". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  80. ^ Kerr, Brynn W. (May 6, 2003). "Mesoscale Discussion 0810". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  81. ^ Event Report for F2 Tornado in Wood County, Texas. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved January 4, 2022.
  82. ^ Mead, Corey; Jewell, Ryan (May 7, 2003). May- 7-2003 0600 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 23, 2021.
  83. ^ Edwards, Roger (May 7, 2003). "Mesoscale Discussion 0811". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  84. ^ Edwards, Roger (May 7, 2003). "Mesoscale Discussion 0812". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  85. ^ Edwards, Roger (May 7, 2003). "Mesoscale Discussion 0813". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  86. ^ Edwards, Roger (May 7, 2003). "Mesoscale Discussion 0816". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  87. ^ Corfidi, Stephen F. (May 7, 2003). "Tornado Watch 282". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  88. ^ Corfidi, Stephen F. (May 7, 2003). "Tornado Watch 283". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  89. ^ Evans, Jeffry A. (May 7, 2003). "Tornado Watch 284". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  90. ^ Broyles, Chris (May 7, 2003). "Mesoscale Discussion 0817". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  91. ^ Broyles, Chris (May 7, 2003). "Mesoscale Discussion 0821". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  92. ^ Taylor, Sarah J. (May 7, 2003). "Mesoscale Discussion 0822". Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021 – via Iowa Environmental Mesonet.
  93. ^ "20030503's Storm Reports". Norman, Oklahoma: Storm Prediction Center. May 7, 2003. Retrieved December 20, 2021.
  94. ^ Peters, Jeff (May 7, 2003). "Mesoscale Discussion 0830". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  95. ^ Peters, Jeff (May 7, 2003). "Mesoscale Discussion 0834". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  96. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0837". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  97. ^ Broyles, Chris (May 7, 2003). "Mesoscale Discussion 0825". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  98. ^ Evans, Jeffry A. (May 7, 2003). "Severe Thunderstorm Watch Number 286". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  99. ^ Broyles, Chris (May 7, 2003). "Mesoscale Discussion 0826". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  100. ^ Banacos, Peter C. (May 7, 2003). "Mesoscale Discussion 0829". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  101. ^ a b Evans, Jeffry A. (May 7, 2003). "Mesoscale Discussion 0824". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  102. ^ Hales, John E. (May 7, 2003). "Tornado Watch Number 290". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  103. ^ Peters, Jeff (May 7, 2003). "Mesoscale Discussion 0828". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  104. ^ Peters, Jeff (May 7, 2003). "Mesoscale Discussion 0836". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  105. ^ Hales, John E. (May 7, 2003). "Tornado Watch Number 293". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  106. ^ a b Dial, Greg (May 8, 2003). May- 8-2003 0600 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021.
  107. ^ a b c d Goss, Steve (May 8, 2003). May- 8-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 24, 2021.
  108. ^ Edwards, Jeff (May 8, 2003). "Mesoscale Discussion 0839". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  109. ^ Edwards, Jeff (May 8, 2003). "Mesoscale Discussion 0843". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  110. ^ Corfidi, Stephen F. (May 8, 2003). "Tornado Watch Number 298". Norman, Oklahoma: Storm Prediction Center. Retrieved December 25, 2021 – via Iowa Environmental Mesonet.
  111. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0846". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  112. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0847". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  113. ^ Evans, Jeffry A. (May 8, 2003). "Tornado Watch Number 300". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  114. ^ Crosbie, Casey (May 8, 2003). "Mesoscale Discussion 0855". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  115. ^ Edwards, Jeff (May 8, 2003). "Mesoscale Discussion 0840". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  116. ^ Edwards, Jeff (May 8, 2003). "Mesoscale Discussion 0844". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  117. ^ a b Imy, David (May 8, 2003). May- 8-2003 1630 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021.
  118. ^ a b Imy, David (May 8, 2003). "Tornado Watch Number 303". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  119. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0851". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  120. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 085". Norman, Oklahoma: Storm Prediction Center. Retrieved December 26, 2021 – via Iowa Environmental Mesonet.
  121. ^ Imy, David (May 8, 2003). "Mesoscale Discussion 0856". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  122. ^ Evans, Jeffry A. (May 8, 2003). "Tornado Watch Number 304". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  123. ^ Evans, Jeffry A. (May 8, 2003). "Tornado Watch Number 305". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  124. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0857". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  125. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0861". Norman, Oklahoma: Storm Prediction Center. Retrieved December 28, 2021 – via Iowa Environmental Mesonet.
  126. ^ Event Report for F0 Tornado in Cloud County, Kansas. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved January 4, 2022.
  127. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0858". Norman, Oklahoma: Storm Prediction Center. Retrieved December 28, 2021 – via Iowa Environmental Mesonet.
  128. ^ "Event Chronology" (PDF). National Weather Service. National Weather Service Weather Forecast Office in Norman, Oklahoma. Retrieved December 24, 2021.
  129. ^ a b c d e McManus, Gary (2004). "May 8-9, 2003 Central Oklahoma Tornadoes" (PDF). Norman, Oklahoma: Oklahoma Climatological Survey. Retrieved December 27, 2021.
  130. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0865". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  131. ^ a b c "May 8, 2003 Oklahoma City Area Tornadoes". Norman, Oklahoma: National Weather Service Norman, Oklahoma. Retrieved December 27, 2021.
  132. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0863". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  133. ^ "Tornadoes strike Osage and Douglas Counties - May 8th, 2003 - NWS Topeka, KS". Topeka, Kansas: National Weather Service Topeka, Kansas. Retrieved December 27, 2021.
  134. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0867". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  135. ^ Peters, Jeff (May 8, 2003). "Mesoscale Discussion 0868". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  136. ^ Dial, David (May 9, 2003). May- 9-2003 0100 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved December 28, 2021.
  137. ^ Event Report for F0 Tornado in Johnson County, Missouri. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved January 4, 2022.
  138. ^ Crosbie, Casey (May 8, 2003). "Mesoscale Discussion 0853". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  139. ^ Crosbie, Casey (May 8, 2003). "Mesoscale Discussion 0860". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  140. ^ Darrow, Mark A. (May 8, 2003). "Mesoscale Discussion 0854". Norman, Oklahoma: Storm Prediction Center. Retrieved December 27, 2021 – via Iowa Environmental Mesonet.
  141. ^ a b Dial, Greg (May 9, 2003). May- 9-2003 0600 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022.
  142. ^ Kerr, Brynn W.; Jewell, Ryan (May 9, 2003). May- 9-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022.
  143. ^ Mead, Corey (May 9, 2003). "Mesoscale Discussion 0872". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  144. ^ Mead, Corey (May 9, 2003). "Mesoscale Discussion 0874". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  145. ^ Darrow, Mark A. (May 9, 2003). "Mesoscale Discussion 0876". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  146. ^ Hart, John (May 9, 2003). "Tornado Watch Number 317". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  147. ^ Crosbie, Casie (May 9, 2003). "Mesoscale Discussion 880". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  148. ^ Banacos, Peter C. (May 9, 2003). "Mesoscale Discussion 887". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  149. ^ a b Banacos, Peter C. (May 9, 2003). "Mesoscale Discussion 893". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  150. ^ Darrow, Mark A. (May 9, 2003). "Mesoscale Discussion 0875". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  151. ^ Darrow, Mark A. (May 9, 2003). "Mesoscale Discussion 0877". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  152. ^ Banacos, Peter C. (May 9, 2003). "Mesoscale Discussion 0882". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  153. ^ Banacos, Peter C. (May 9, 2003). "Mesoscale Discussion 0890". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  154. ^ Hart, John (May 9, 2003). "Mesoscale Discussion 0878". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  155. ^ Darrow, Mark A. (May 9, 2003). "Mesoscale Discussion 0879". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  156. ^ Peters, Mark A. (May 9, 2003). "Mesoscale Discussion 0885". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  157. ^ a b Hales, John E. (May 9, 2003). "Tornado Watch Number 321". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  158. ^ Hart, John (May 9, 2003). "Tornado Watch Number 320". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  159. ^ Hales, John E. (May 9, 2003). "Tornado Watch Number 324". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  160. ^ Peters, Mark A. (May 9, 2003). "Mesoscale Discussion 0891". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  161. ^ a b c d "The May 9, 2003 Central Oklahoma Tornadoes". Norman, Oklahoma: National Weather Service Norman, Oklahoma. Retrieved January 1, 2022.
  162. ^ "Event Chronology" (PDF). National Weather Service. National Weather Service Weather Forecast Office in Norman, Oklahoma. Retrieved January 1, 2022.
  163. ^ Peters, Mark A. (May 9, 2003). "Mesoscale Discussion 0889". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  164. ^ Peters, Mark A. (May 9, 2003). "Mesoscale Discussion 0895". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  165. ^ Hales, John E. (May 9, 2003). "Tornado Watch Number 329". Norman, Oklahoma: Storm Prediction Center. Retrieved January 1, 2022 – via Iowa Environmental Mesonet.
  166. ^ a b c d e f Glass, Fred H. (November 10, 2006). An Overview of the May 10, 2003 Tornado Outbreak (PDF). 23rd Conference on Severe Local Storms. St. Louis, Missouri: American Meteorological Society. Retrieved January 2, 2022.
  167. ^ a b c Dial, Greg (May 10, 2003). May-10-2003 0600 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022.
  168. ^ a b Kerr, Brynn W.; Jewell, Ryan (May 10, 2003). May-10-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022.
  169. ^ Mead, Corey (May 10, 2003). "Mesoscale Discussion 0897". Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022 – via Iowa Environmental Mesonet.
  170. ^ Mead, Corey (May 10, 2003). "Mesoscale Discussion 0899". Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022 – via Iowa Environmental Mesonet.
  171. ^ Mead, Corey (May 10, 2003). "Mesoscale Discussion 0901". Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022 – via Iowa Environmental Mesonet.
  172. ^ a b Mead, Corey (May 10, 2003). "Mesoscale Discussion 0898". Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022 – via Iowa Environmental Mesonet.
  173. ^ Mead, Corey (May 10, 2003). "Mesoscale Discussion 0902". Norman, Oklahoma: Storm Prediction Center. Retrieved January 2, 2022 – via Iowa Environmental Mesonet.
  174. ^ Thompson, Rich (May 10, 2003). "Severe Thunderstorm Watch Number 334". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  175. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0907". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  176. ^ Hart, John (May 10, 2003). "Tornado Watch Number 335". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  177. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0905". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  178. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0906". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  179. ^ Hart, John (May 10, 2003). "Tornado Number 336". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  180. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0910". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  181. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0914". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  182. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0921". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  183. ^ Banacos, Peter C. (May 10, 2003). "Mesoscale Discussion 0923". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  184. ^
    • Hart, John (May 10, 2003). "Tornado Number 340". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
    • Hart, John (May 10, 2003). "Tornado Number 343". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
    • Hart, John (May 10, 2003). "Tornado Number 345". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  185. ^ a b Imy, David (May 10, 2003). May-10-2003 1630 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022.
  186. ^ Darrow, Mark (May 10, 2003). "Mesoscale Discussion 0904". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  187. ^ Crosbie, Casey (May 10, 2003). "Mesoscale Discussion 0908". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  188. ^ Darrow, Mark (May 10, 2003). "Mesoscale Discussion 0909". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  189. ^ Darrow, Mark (May 10, 2003). "Mesoscale Discussion 0919". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  190. ^ Hales, John E. (May 10, 2003). "Tornado Number 346". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  191. ^ Hart, John (May 10, 2003). "Tornado Number 338". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  192. ^ Darrow, Mark (May 10, 2003). "Mesoscale Discussion 0915". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  193. ^ Darrow, Mark (May 10, 2003). "Mesoscale Discussion 0916". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  194. ^ Event Report for F0 Tornado in Linn County, Missouri. Storm Events Database (Report). Asheville, North Carolina: National Centers for Environmental Information. Retrieved January 4, 2022.
  195. ^ Dial, Greg (May 10, 2003). "Mesoscale Discussion 0922". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  196. ^ Hales, John E. (May 10, 2003). "Tornado Number 348". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  197. ^ Hales, John E. (May 10, 2003). "Tornado Number 349". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  198. ^ Hales, John E. (May 10, 2003). "Tornado Number 351". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  199. ^ Peters, Jeff (May 10, 2003). May-10-2003 0600 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022.
  200. ^ a b c d Jurewicz, Michael L Sr.; Evans, Micahel; Cempa, Michael (October 7, 2004). The May 11, 2003 severe weather null case across the Northeastern and Mid-Atlantic States (PDF). 22nd Conference on Severe Local Storms. Hyannis, Massachusetts: American Meteorological Society. Retrieved January 4, 2022.
  201. ^ Dial, Greg (May 10, 2003). "Mesoscale Discussion 0932". Norman, Oklahoma: Storm Prediction Center. Retrieved January 4, 2022 – via Iowa Environmental Mesonet.
  202. ^ Mead, Corey (May 11, 2003). "Mesoscale Discussion 0936". Norman, Oklahoma: Storm Prediction Center. Retrieved January 4, 2022 – via Iowa Environmental Mesonet.
  203. ^ "May 11, 2003 Severe Weather/Tornado Event". NWS Louisville - May 11, 2003 Severe Weather Event. Louisville, Kentucky: National Weather Service Louisville, Kentucky. Retrieved January 4, 2022.
  204. ^ a b "May 11, 2003 Tornado Outbreak". Nashville, Tennessee: National Weather Service Nashville, Tennessee. Retrieved January 4, 2022.
  205. ^ Thompson, Rich (May 11, 2003). "Severe Thunderstorm Watch Number 356". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  206. ^ Kerr, Brynn W.; Jewell, Ryan (May 11, 2003). May-11-2003 1300 UTC Day 1 Convective Outlook (Report). Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022.
  207. ^ Hart, John (May 11, 2003). "Mesoscale Discussion 0941". Norman, Oklahoma: Storm Prediction Center. Retrieved January 4, 2022 – via Iowa Environmental Mesonet.
  208. ^ Hart, John (May 11, 2003). "Mesoscale Discussion 0942". Norman, Oklahoma: Storm Prediction Center. Retrieved January 4, 2022 – via Iowa Environmental Mesonet.
  209. ^ Hart, John (May 11, 2003). "Tornado Watch Number 357". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  210. ^ Hart, John (May 11, 2003). "Tornado Watch Number 358". Norman, Oklahoma: Storm Prediction Center. Retrieved January 3, 2022 – via Iowa Environmental Mesonet.
  211. ^ a b c Stuart, Neil A. (October 7, 2004). The Anatomy of the Big Event That Never Happened – The Grand Finale of the May 2003 Tornado Outbreak (PDF). 22nd Conference on Severe Local Storms. Hyannis, Massachusetts: American Meteorological Society. Retrieved January 4, 2022.
  212. ^ National Weather Service Kansas City/Pleasant Hill, Missouri. Kansas Event Report: F2 Tornado (Report). Pleasant Hill, Missouri: National Centers for Environmental Information. Retrieved June 5, 2019.
  213. ^ a b c Scott, David (May 5, 2003). "At least 22 killed in region's twisters". Springfield News-Leader. Springfield, Missouri. Associated Press. p. 5A. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  214. ^ National Weather Service Kansas City, Missouri. Missouri Event Report: F4 Tornado (Report). Kansas City, Missouri: National Centers for Environmental Information. Retrieved June 5, 2019.
  215. ^ a b c d e f g h National Weather Service Kansas City/Pleasant Hill, Missouri (May 8, 2003). NWS Kansas City/Pleasant Hill, Missouri Public Information Statement. National Weather Service Raw Text Product (Public Information Statement). Pleasant Hill, Missouri: Iowa State University.
  216. ^ a b c d Scott, David (May 5, 2019). "Tornadoes hit Kansas, Missouri". The Hays Daily News. Hays, Kansas. Associated Press. pp. A1, A6. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  217. ^ Hudson, Michael J. (May 7, 2003). "National Weather Service Assigns Fujita Damage Ratings to May 4th Tornadoes in the Kansas City Metropolitan Area" (Press release). Southern Illinois University Edwardsville. Retrieved June 5, 2019.
  218. ^ Kansas Event Report: F1 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  219. ^ Missouri Event Report: F1 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  220. ^ Kansas Event Report: F2 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  221. ^ Kansas Event Report: F4 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  222. ^ Missouri Event Report: F4 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  223. ^ Missouri Event Report: F4 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  224. ^ National Weather Service Kansas City/Pleasant Hill, Missouri (May 9, 2003). Liberty Tornado Rated F2. National Weather Service Raw Text Product (Public Information Statement). Pleasant Hill, Missouri: Iowa State University.
  225. ^ Missouri Event Report: F2 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved May 30, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  226. ^ a b c Rao, Nina; Eckert, Eric; Fillmer, Jenny (May 5, 2003). "Rare conditions whip up multiple storms". Springfield News-Leader. Springfield, Missouri. pp. 1A, 5A. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  227. ^ Groves, Jonathan; Eckert, Eric (May 5, 2003). "Trail of devastation left in Christian County". Springfield News-Leader. Springfield, Missouri. p. 5A. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  228. ^ Fillmer, Jenny; Ledford, David (May 5, 2003). "Storm ravages Battlefield homes". Springfield News-Leader. Springfield, Missouri. p. 4A. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  229. ^ Missouri Event Report: F1 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved June 5, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  230. ^ a b "Tornado Outbreak – May 4th, 2003". National Weather Service. National Weather Service Weather Forecast Office in Springfield, Missouri. Retrieved June 5, 2019.
  231. ^ a b Missouri Event Report: F3 Tornado (Report). National Centers for Environmental Information. 2003. Retrieved June 5, 2019. {{cite report}}: Unknown parameter |agency= ignored (help)
  232. ^ "Storm Event Database 2003-05-08 16:04 CST". National Centers for Environmental Information. Retrieved October 13, 2022.
  233. ^ "Storm Event Database 2003-05-08 16:10 CST". National Centers for Environmental Information. Retrieved October 13, 2022.
  234. ^ "Storm Event Database 2003-05-08 16:15 CST". National Centers for Environmental Information. Retrieved October 13, 2022.
  235. ^ a b c "The May 8, 2003 Oklahoma City Area Tornadoes". National Weather Service – Norman, Oklahoma. National Oceanic and Atmospheric Administration. Retrieved June 2, 2008.
  236. ^ a b National Weather Service Morristown, Tennessee. "The Major to Record Flooding of May 2003 across East Tennessee". Record Flooding of May 2003 across East Tennessee. Morristown, Tennessee: National Weather Service. Retrieved May 15, 2019.
  237. ^ Dartmouth Flood Observatory. "Dartmouth Flood Observatory – Flood Analysis Report 2003-111". Space-based Measurement of Surface Water. Hanover, New Hampshire: Dartmouth College. Retrieved May 15, 2019.
  238. ^ National Weather Service Nashville, Tennessee. Tennessee Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 15, 2019.
  239. ^ National Weather Service Nashville, Tennessee. Tennessee Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 15, 2019.
  240. ^ a b National Weather Service Birmingham, Alabama (May 7, 2003). "Severe Weather & Flooding of May 7, 2003". NWS Birmingham, Alabama. Calera, Alabama: National Weather Service. Retrieved May 15, 2019.
  241. ^ National Weather Service Birmingham, Alabama. Alabama Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  242. ^ Taylor, Stephanie (May 10, 2019). "Worst flooding in decades recedes – for most". Tuscaloosa, Alabama: GateHouse Media, LLC. Retrieved June 5, 2019.
  243. ^ National Weather Service Huntsville, Alabama (May 22, 2003). The Long Stretch of Rain is Finally Over. Heavy Rainfall in May 2003: NWS Huntsville (Public Information Statement). Huntsville, Alabama: National Weather Service. Retrieved May 15, 2019.
  244. ^ National Weather Service Peachtree City, Georgia (May 2, 2003). "Late Spring Season Flooding of 2003". Storm Report – Flooding in early May 2003. Peachtree City, Georgia: National Weather Service. Retrieved May 15, 2019.
  245. ^ National Weather Service Peachtree City, Georgia. Georgia Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  246. ^ National Weather Service Peachtree City, Georgia. Georgia Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  247. ^ National Weather Service Peachtree City, Georgia (May 2, 2003). "Thunderstorms Bring Hail and Wind Damage to a Wide Area of Georgia". May 2, 2003, Thunderstorms. Peachtree City, Georgia: National Weather Service. Retrieved May 15, 2019.
  248. ^ a b "Severe weather gives area residents a scare". The Index-Journal. Greenwood, South Carolina. May 7, 2003. pp. 1A, 8A. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  249. ^ a b "Severe Thunderstorms and an F1 Tornado in Williamsburg County, SC: May 6, 2003". NWS Wilmington, NC. Wilmington, North Carolina: National Weather Service. Retrieved May 24, 2019.
  250. ^ National Weather Service Columbia, South Carolina. South Carolina Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  251. ^ "Thunderstorms sweep across state". Rocky Mount Telegram. Rocky Mount, North Carolina. Associated Press. May 10, 2003. p. 8A. Retrieved May 25, 2019 – via Newspapers.com. Open access icon
  252. ^ National Weather Service Wakefield, Virginia. North Carolina Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  253. ^ a b National Weather Service Paducah, Kentucky (2003). "May 4 Hailstorms in Western KY" (PDF). NWS Paducah. Paducah, Kentucky: National Weather Service. Retrieved May 22, 2019.
  254. ^ a b National Weather Service Paducah, Kentucky. Kentucky Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 22, 2019.
  255. ^ "Top 10 Weather Headlines of 2003". NWS Paducah. Paducah, Kentucky: National Weather Service. Retrieved May 22, 2019.
  256. ^ a b "State-by-state storm damage". The Hamilton Spectator. Hamilton, Ontario. May 6, 2003. p. D01.
  257. ^ National Weather Service Charleston, West Virginia. Kentucky Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  258. ^ National Weather Service Baltimore/Washington. Virginia Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  259. ^ "Tornado warnings issued in Southern Md". The Sun. Baltimore, Maryland. May 8, 2019. p. 2B. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  260. ^ Paust, Matthew; McCloud, Tina (May 9, 2003). "Swift storm damages homes, businesses in Gloucester". Daily Press. Newport News, Virginia. Daily Press. p. C2. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  261. ^ National Weather Service Roanoke, Virginia. Virginia Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  262. ^ National Weather Service Charleston, West Virginia. West Virginia Event Report: Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  263. ^ National Weather Service Roanoke, Virginia. West Virginia Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  264. ^ National Weather Service Hastings, Nebraska. Nebraska Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 22, 2019.
  265. ^ National Weather Service Topeka, Kansas. Kansas Event Report: High Winds. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  266. ^ National Weather Service Wichita, Kansas. Kansas Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  267. ^ National Weather Service Kansas City/Pleasant Hill, Missouri. Missouri Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  268. ^ National Weather Service St. Louis, Missouri. Missouri Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 25, 2019.
  269. ^ Jonsson, Greg (May 7, 2019). "Trailers are toppled, roofs ripped off in Jefferson County". St. Louis Post-Dispatch. St. Louis, Missouri. pp. A1, A10. Retrieved May 26, 2019.
  270. ^ Hathaway, Matthew; Holland, Elizabethe; Rowden, Tim (May 8, 2003). "Cleanup begins in storms' path". St. Louis Post-Dispatch. St. Louis, Missouri. p. A19. Retrieved May 25, 2019 – via Newspapers.com. Open access icon
  271. ^ National Weather Service St. Louis, Missouri. Missouri Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 26, 2019.
  272. ^ Wilson, Angela (May 7, 2003). "Tornadoes return, but damage little". Springfield News-Leader. Springfield, Missouri. p. 7A. Retrieved May 26, 2019 – via Newspapers.com. Open access icon
  273. ^ "Small twisters move across Missouri, Kansas". The Springfield News-Leader. Springfield, Missouri. Associated Press. May 7, 2003. p. 7B. Retrieved May 27, 2019.
  274. ^ Hathaway, Matthew; Komperada, Jack; O'Neil, Tim (May 9, 2003). "Heavy storms again pummel the bistate area". St. Louis Post-Dispatch. St. Louis, Missouri. p. A8. Retrieved May 26, 2019 – via Newspapers.com. Open access icon
  275. ^ National Weather Service Kansas City/Pleasant Hill, Missouri. Missouri Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 26, 2019.
  276. ^ National Weather Service Kansas City/Pleasant Hill, Missouri. Missouri Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 26, 2019.
  277. ^ "B-2 Bombers at Whiteman Air Force were unharmed in Thursday night storms". St. Louis Post-Dispatch. St. Louis, Missouri. Associated Press. May 11, 2003. p. D7. Retrieved May 26, 2019 – via Newspapers.com. Open access icon
  278. ^ National Weather Service St. Louis, Missouri. Missouri Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 26, 2019.
  279. ^ National Weather Service St. Louis, Missouri. Missouri Event Report: Heavy Rain. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 26, 2019.
  280. ^ Moore, Doug; Rowden, Tim (May 11, 2003). "In latest set of storms, tornado heavily damages Canton, Mo". St. Louis Post-Dispatch. St. Louis, Missouri. p. A7. Retrieved May 26, 2019 – via Newspapers.com. Open access icon
  281. ^ National Weather Service Des Moines, Iowa. Iowa Event Report: Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 22, 2019.
  282. ^ National Weather Service Des Moines, Iowa. Iowa Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 22, 2019.
  283. ^ National Weather Service Davenport, Iowa. Iowa Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 22, 2019.
  284. ^ a b National Weather Service Davenport, Iowa. Iowa Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  285. ^ Deering, Tara (May 10, 2003). "Hail, rain pummel southern Iowa". The Des Moines Register. Des Moines, Iowa. p. 1B. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  286. ^ National Weather Service Davenport, Iowa. Illinois Event Report: Hail. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  287. ^ National Weather Service St. Louis, Missouri. Illinois Event Report: Flash Flood. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  288. ^ National Weather Service Davenport, Illinois. Illinois Event Report: High Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  289. ^ National Weather Service Chicago, Illinois. Illinois Event Report: Strong Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  290. ^ National Weather Service Chicago, Illinois. Illinois Event Report: High Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  291. ^ Cross, Pamela (May 24, 2019). "Winds bring blackouts". The Pantagraph. Bloomington, Illinois. p. A5. Retrieved May 24, 2019 – via Newspapers.com. (subscription required)
  292. ^ National Weather Service Cleveland, Ohio. Ohio Event Report: Strong Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  293. ^ Smith, Erin (May 12, 2003). "High winds cause problems in area". Journal and Courier. Lafayette, Louisiana. p. B1. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  294. ^ National Weather Service Detroit, Michigan. Michigan Event Report: High Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 23, 2019.
  295. ^ "Search Results for All Counties in Oklahoma". Storm Events Database. Asheville, North Carolina: National Centers for Environmental Information. Retrieved May 24, 2019.
  296. ^ Medley, Robert (May 5, 2003). "Severe storms cause damage in parts of state". The Daily Oklahoman. Oklahoma City, Oklahoma. pp. 1–A, 2–A. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  297. ^ Stogsdill, Sheila K. (May 6, 2003). "Storms hit Grand Lake area, destroy large trees in Grove". The Daily Oklahoman. Oklahoma City, Oklahoma. p. 8-A. Retrieved May 24, 2019 – via Newspapers.com. Open access icon
  298. ^ National Weather Service Tulsa, Oklahoma. Oklahoma Event Report: Thunderstorm Wind. Storm Events Database (Report). National Centers for Environmental Information. Retrieved May 24, 2019.
  299. ^ Oklahoma Department of Emergency Management (May 8, 2003). May 8, 2003 Severe Weather Strikes Oklahoma – Situation Report #1. May 2003 Severe Weather Event (Situation Report). Oklahoma City, Oklahoma: State of Oklahoma. Retrieved May 15, 2019.
  300. ^ Federal Emergency Management Agency (January 19, 2011). "Kansas Severe Storms, Tornadoes and Flooding (DR-1462)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  301. ^ Federal Emergency Management Agency (August 14, 2013). "Missouri Severe Storms, Tornadoes and Flooding (DR-1463)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  302. ^ Federal Emergency Management Agency (April 10, 2019). "Tennessee Severe Storms, Tornadoes and Flooding (DR-1464)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  303. ^ Federal Emergency Management Agency (May 21, 2013). "Oklahoma Severe Storms and Tornadoes (DR-1465)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  304. ^ Federal Emergency Management Agency (August 25, 2014). "Alabama Severe Storms, Tornadoes and Flooding (DR-1466)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  305. ^ Federal Emergency Management Agency (February 28, 2011). "Illinois Severe Storms, Tornadoes, and Flooding (DR-1469)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  306. ^ Federal Emergency Management Agency (October 24, 2008). "Mississippi Severe Storms, Tornadoes, and High Winds (DR-1470)". Disasters. Department of Homeland Security. Retrieved May 23, 2019.
  307. ^ "FEMA to Help Victims of Midwest Tornadoes". Pierce City, Missouri. Associated Press. May 6, 2003 – via NewsBank.(subscription required)
  308. ^ Farrow, Connie (May 6, 2003). "Bush Declares Disaster Areas in Kan., Mo". Pierce City, Missouri – via NewsBank. (subscription required)
  309. ^ a b "President Orders Disaster Aid For Kansas Tornado Victims" (Press release). Washington, D.C.: Department of Homeland Security. May 6, 2003. HQ-03-109. Retrieved June 7, 2019.
  310. ^ "More Than 30 Die as Tornadoes Sweep Through Midwest". The New York Times. New York City. Associated Press. May 5, 2003. Retrieved June 7, 2019. (subscription required)
  311. ^ Linder, Melissa; Schneider, Troy (May 5, 2019). "'Whole lot worse than the '99 tornado'". The Jackson Sun. The Jackson Sun. pp. 1A, 2A. Retrieved June 5, 2019 – via Newspapers.com. Open access icon
  312. ^ Medley, Robert (May 6, 2003). "Oklahoma sends trucks, workers to stricken areas". The Oklahoman. Oklahoma City, Oklahoma. p. 1-A – via NewsBank. (subscription required)
  313. ^ Charton, Scott (May 6, 2003). "Guardsmen Return to Midwest—Many in Unit Headed to Help Rebuild Baghdad Go Back Home to Assist With Tornado Cleanup". Akron Beacon Journal. Akron, Ohio. Associated Press. p. A4 – via NewsBank. (subscription required)
  314. ^ National Centers for Environmental Prediction (2004). "Biennial Review — 2003/2004" (PDF). College Park, Maryland: National Oceanic and Atmospheric Administration. p. 4. Retrieved May 23, 2019.

External links[edit]

Overall
April 30 – May 3
May 4–5
May 6–7
May 8
May 9
May 10
May 11