Tornado outbreak of May 2019

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
The Tornado outbreak sequence of May 2019
File:May 2019 tornado outbreak warnings and reports.png
Map of tornado warnings and confirmed tornadoes from the outbreak sequence.
Type Tornado outbreak
Formed May 17, 2019 (2019-05-17)
Tornadoes confirmed 236
Max rating1 EF4 tornado
Highest winds Tornadic – 170 mph (260 km/h) in Linwood, Kansas on May 28
Non-tornadic – 94 mph (151 km/h) near Marshall, Oklahoma on May 20
Areas affected Great Plains, Midwestern United States, Eastern United States
1Most severe tornado damage; see Enhanced Fujita scale Part of the Tornadoes of 2019

The tornado outbreak sequence of May 2019 is an ongoing record-breaking tornado outbreak affecting the United States and Canada, which has so far produced at least 230 tornadoes, including 39 significant events (EF2+). 16 of these were EF3 tornadoes, spanning over multiple states, including Nebraska, Kansas, Texas, Missouri, Oklahoma, Colorado, Indiana, Iowa, and Ohio, with additional tornadoes being confirmed in Illinois and Minnesota. One EF4 tornado struck Linwood, Kansas.

Overview

On May 28, the U.S. had its 12th straight day with at least eight tornadoes, which broke the previous record of 11 days straight set in 1980.[1] During this period, the U.S. had an average of 27.5 tornadoes per day.[2] Only three days during this period did not see an EF3 tornado or stronger.

Tornadoes during this period have been reported in half of all U.S. states. As of May 24, Pennsylvania has exceeded its annual average number of tornadoes. [3]

A pattern of increased clustering of U.S. tornadoes had been previously documented.[4]

The May storms also included frequent heavy rainfall, sometimes at record levels, on previously-saturated ground across the U.S. and eastern Canada.[5] This resulted in widespread riverine and lakeshore flooding and flash flooding, which frequently interfered with emergency efforts relating to tornado damage. The new precipitation also extended existing flooding along the Mississippi River system to record durations.

Meteorological synopsis

May 17

File:2019-05-17 Minneola tornado.jpg
An EF3 tornado near Minneola, Kansas, on May 17

The threat for organized severe weather on May 17 was first outlined five days prior, when the Storm Prediction Center (SPC) outlined the Texas and Oklahoma panhandles, as well as western Kansas, in a 15% probability contour.[6] On the morning of May 14, this risk area was expanded and 30% severe probabilities were introduced as the SPC gained confidence in a widespread and prolonged severe weather outbreak.[7] For the first time in the organization's history, a threat of severe weather was introduced for their entire day 4–8 period.[8] By May 17, a dual Enhanced risk existed across the Central Plains, one across much of Nebraska and the second across southwestern Texas. As a large scale upper-level trough ejected into the region, dew points in the low to mid-60s °F surged north in front of a dryline. A cap across the region allowed the atmosphere to become extremely unstable, while an eastward-moving dryline was expected to become the focus for severe thunderstorms later in the day. The SPC noted uncertainty regarding convective development farther south across southwestern Kansas into Oklahoma but mentioned that any thunderstorms would be capable of significant severe weather if they came to fruition.[9]

By late afternoon, several discrete supercell thunderstorms formed across northwestern Kansas and progressed into western and central Nebraska. While weak and largely uniform wind shear caused several splitting storms that destructively interfered with one another,[10] one supercell later in the evening formed within a strongly sheared environment, becoming intense and long-lived as it progressed northeastward.[11] It produced seven tornadoes in total, five of which were weak. One EF2 tornado northeast of Stockville rolled 1,400 lb (640 kg) hay bales and snapped twelve power poles. The strongest was a high-end EF3 that extensively damaged or destroyed structures at a farmstead.[12] Later in the evening, a long-lived supercell formed in southwestern Kansas where SPC had previously highlighted uncertainty in convective development. This supercell produced four tornadoes in areas southeast of Dodge City, including an EF3 and two EF2s.[13]

May 18

Into the morning hours of May 18, the large scale upper-level trough continued to shift eastward. Strong mid- and upper-level winds associated with this feature spread across much of Oklahoma and Texas, accompanied by dewpoints in the upper 60s to lower 70s °F and mid-level CAPE values on the order of 2,500–3,500 J/kg.[14] While the prominent threat was expected to be damaging winds along an eastward-moving mesoscale convective system, the SPC noted the potential for embedded and brief tornadoes.[15] Throughout the pre-dawn and early morning hours, a mixture of semi-discrete and linear thunderstorms developed across central and eastern Oklahoma down into northern Texas.[16] Strong southeasterly surface winds ahead of this convection in Texas provided the impetus for prolific tornado production over subsequent hours as it moved toward the northeast.[17] A long-lived supercell produced seven tornadoes as it progressed from near San Angelo, Texas, to northwest of Coleman. All seven were significant tornadoes, including three that reached EF3 intensity. Three people were injured as trees were snapped and debarked, roofs were ripped off structures, exterior walls of buildings were collapsed, and power poles were snapped or leaned.[18][19] Farther to the north, a brief but strong tornado occurred east of Geronimo, Oklahoma, ripping the roofs of two homes and injuring one individual.[20] Through the late morning and afternoon hours, a squall line progressed across eastern Oklahoma and northwestern Arkansas. In the presence of strong instability and very strong low-level shear, numerous tornadoes were confirmed across the region, all rated EF0 or EF1. Widespread damaging winds were also observed, reaching 100 mph (155 km/h) in some places.[21]

May 20

On the morning of May 20, 2019, the Storm Prediction Center in Norman, Oklahoma issued a high risk for severe weather across western and central Oklahoma and northwest Texas.[22] As a precaution, many public school districts, private schools and colleges (including the University of Oklahoma) throughout Oklahoma announced during the afternoon and evening of May 19 that they would cancel all classes and extracurricular activities for the following day, if not hold classes during the morning only. Ironically, in response to the deaths of seven students at Plaza Towers Elementary School in Moore after the May 20, 2013 tornado hit that school and nearby Briarwood Elementary, several of the public primary and secondary schools that cancelled classes had since installed underground storm shelters for student and faculty use in the event that a tornado approached during school hours. The El Reno, Oklahoma school district – which has storm shelters at seven of its schools (six underground and one above-ground shelter) – was one of the few in sections of central and western Oklahoma under highest threat of significant severe weather that decided to hold regular classes that day; El Reno Superintendent Craig McVay defended the decision on safety grounds, acknowledging that between 75% and 90% of students in the district do not have shelters in their home. Businesses, churches and other venues also decided to cancel events and activities, while some city government offices (including in Oklahoma City) and Tinker Air Force Base instituted liberal leave policies to allow employees to arrive home prior to the onset of severe thunderstorm activity.[23][24] By midday, the SPC increased the risk of significant tornadoes in northern portions of the Texas Panhandle, southwestern and central Oklahoma (including Oklahoma City) from 30% to 45%.[25]

The Storm Prediction Center issued a Particularly Dangerous Situation Tornado Watch (the 197th severe weather watch issued in 2019) at 1:35 p.m. CDT for portions of the eastern Texas Panhandle and the Texas High Plains. A second PDS Tornado Watch (watch #199) was issued at 2:45 p.m. CDT for much of Oklahoma and western portions of north Texas, indicating >95% probabilities for all severe hazards (including probabilities of at least two tornadoes and one or more strong tornadoes [rated EF2 or higher], ten or more cases of straight-line thunderstorm winds of at least 58 miles per hour [93 km/h] and at least one case of 75 miles per hour [121 km/h] winds, and ten or more cases of hail of at least one inch [2.5 cm] in diameter and at least one case of hail larger than two inches [5.1 cm] in diameter); this was the second PDS watch with such high probabilities of significant severe weather to be issued by the SPC, after one issued for much of Alabama and portions of southeast Mississippi, southern middle Tennessee and northwest Georgia during the historic Super Outbreak of April 27, 2011.[26]

An EF-2[27] wedge tornado passed just north of Mangum, Oklahoma, damaging several homes and completely sweeping one home off its foundation. Moderate ground scouring occurred near Mangum with this tornado. Rare and highly visible twin tornadoes caused light damage in Canadian County, Oklahoma and Kingfisher, Oklahoma counties Northeast of El Reno, Oklahoma and Southwest of Piedmont, Oklahoma in Central Oklahoma. They were captured live on air by KFOR-TV's Chopper 4 Helicopter.[28] Several other tornadoes were reported across Texas, as well as damage from a reported tornado in Missouri. After dark, an embedded supercell produced a 1.5 mile wide EF2 tornado east of Tulsa, Oklahoma. Radar confirmation along with a nearly 3-mile-wide debris ball as well as a very intense velocity signature from this tornado prompted the National Weather Service office in Tulsa to issue a rare tornado emergency at 10:49 p.m. CDT for portions of Cherokee and Delaware counties; the storm directly impacted Leach, Oklahoma and adjacent communities. A subsequent squall line that moved through the southern half of Oklahoma during the early morning hours of May 21 produced three tornadoes in Cleveland and Pottawatomie counties, including two EF1s in Norman and Noble, which caused mostly tree damage, and an EF2 in Dale. Damage surveys are still ongoing, but 35 tornadoes were reported on May 20.[29]

May 21

The following day, a large and likely intense tornado developed from an embedded supercell west of the St. Louis, Missouri metro area, near Augusta, Missouri. Damage was reported, but the extent of it is unknown. Despite a tornado warning being issued for the St. Louis metro area, the city escaped any major damage. Several tornadoes were also reported in Kansas and Nebraska.[30] An EF-1 tornado tracked over Tulsa International Airport, injuring a man. The Airport was left unscathed; meanwhile, damage was reported across town. 37 tornadoes were reported on May 21. This day, severe weather resulted in a fatal car crash, which killed two people, as well as the drowning of another driver in Perkins, Oklahoma.

May 22

On May 22, the Storm Prediction Center issued a moderate risk for severe weather for Oklahoma, Kansas and Missouri. The potential for powerful tornadoes would linger from Tulsa, Oklahoma to Columbia, Missouri.

An early-morning EF-2 tornado struck Adair, Iowa with 1 fatality and 1 injury reported in addition to damage of 3 buildings and destruction of another on a farm.[31]

By 4:30 PM CDT, three Tornado Watches, stretching from north-central Texas to northwest and west-central Illinois were in effect, with two of them classified as PDS watches.[2]

A Tornado Emergency was issued at 8:19 PM CDT for a large and destructive tornado near Oronogo, MO. 4 tornadoes occurred with this dangerous supercell, 3 of them being rated at EF3 strength. One EF3 near Golden City, MO killed 3 people.[32]

A large and violent tornado prompted a tornado emergency to be issued at 11:44 PM CDT by the National Weather Service for Jefferson City, Missouri.[33] Surveys found that this was a long-track high-end EF3 that was on the ground for 32 miles and was almost a mile wide at its peak intensity, but did not cause any deaths.

May 23

At 8:11 AM CDT on Thursday, May 23, 2019, The National Weather Service in Lincoln issued a Tornado Warning for Lawrence County and Eastern Richland County in southeastern Illinois. [34] [35] [36] [37] A wedge tornado passed North of Canadian, Texas, completely leveling 2 homes.

An early morning squall line also caused widespread wind damage across central Illinois and Indiana, with the worst effected area seeming to be west central Indiana. [38][39][40]

May 24

On the morning of May 24, the Storm Prediction Center issued a slight risk of convective activity stretching from southwest Texas to the lower peninsula of Michigan, with a 5% risk of tornadoes for northern Illinois, far southern Wisconsin, and far eastern Iowa.[41] By the afternoon, this was upgraded to an enhanced risk for a portion of northwest Texas, with a 5% risk of tornadoes from there to Illinois.[42] Two EF1 tornadoes had already touched down in Kansas in the early morning hours, and in the afternoon tornado activity began again for the 8th day in a row. Just after 12:30 local time, two EF1 tornadoes touched down near Industry, Illinois, destroying outbuildings. [43] An EF1 tornado in Iowa City, Iowa destroyed outbuildings and large trailers,[44] and a series of EF0 tornadoes touched down in Missouri and Wisconsin.

May 25

As persistent southwesterly mid-level flow continued to engulf the Central Plains, the SPC once again warned of the potential for widespread severe weather, outlining the Texas Panhandle, western Oklahoma, and southern Kansas in an Enhanced risk. An area of low pressure was expected to progress over the southern High Plains, supporting a southward-extending dryline and a northeast-extending cold front to the Iowa–Missouri border. Within the warm sector, mid-level CAPE values were forecast to rise upwards of 2,000–3000 J/kg,[45] with dewpoints in the mid-60s °F as far west as eastern New Mexico.[46] Thunderstorms began developing along the dryline in eastern New Mexico and western Texas around noon local time, though these storms were not tornadic in nature in the absence of strong low-level shear.[47] By the late afternoon hours, more transient supercell structures had become apparent,[48] leading to a few tornadoes across the Texas Panhandle. One such tornado was rated an EF2 as it destroyed outbuildings, a mobile home, and a trussed cell phone tower among other impacts.[49] Several weak tornadoes also occurred across the Ohio Valley, where a well-defined shortwave trough combined with abundant moisture and sufficient instability to produce thunderstorms.[45] Hundreds of damaging wind reports were received.[50] Through the evening hours, earlier discrete activity across Texas and Oklahoma congealed into an organized mesoscale convective system. Weak mid-level winds were expected to mitigate the tornado risk,[51] owing to a severe thunderstorm watch across central Kansas down into central Oklahoma.[52] At 10:28 p.m. CDT, however, a narrow but significant tornado moved through southern sections of El Reno, Oklahoma, causing severe damage, killing 2 people, and injuring 19 others.[53]

May 26

Into the morning hours of May 26, the mesoscale convective system continued to push across eastern Oklahoma, leading to simultaneous, large EF1 tornadoes near Sapulpa.[54] Into the afternoon hours, a concentrated risk for severe weather was once again expected to exist across the Central and South Plains. Several days of convection had eroded the elevated mixed layer throughout the region, but broad and intensifying southwesterly flow across northern Mexico was expected to reinvigorate this plume. Underneath the potent mid-level flow, rich low-level moisture was forecast to surge into western Kansas and eastern Colorado while mid-level CAPE values were projected to top 3,000 J/kg.[55] While initiation of thunderstorms was expected in the early afternoon hours (with the threat for large hail being the primary threat initially in the presence of weak low-level wind shear), more expansive cloud cover and a stronger cap delayed initiation.[56][57] Later in the day, a cluster of storms formed across portions of Nebraska and Kansas,[58] with a severe squall line taking shape farther south across the Texas and Oklahoma panhandles as stronger upper-level winds arrived.[59] Numerous brief and weak tornadoes were reported throughout the area, in addition to widespread damaging wind and dozens of hail reports.[60]

Confirmed tornadoes

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: List of tornadoes in the tornado outbreak of May 2019
Daily statistics of tornadoes during the tornado outbreak of May 2019
Date Total Enhanced Fujita scale rating
 EFU   EF0   EF1   EF2   EF3   EF4   EF5 
May 17 17 2 6 3 4 2 0 0
May 18 19 0 3 8 5 3 0 0
May 19 20 0 5 15 0 0 0 0
May 20 11 0 2 5 3 1 0 0
May 21 25 1 8 13 2 1 0 0
May 22 18 0 3 10 2 3 0 0
May 23 13 0 4 7 1 1 0 0
May 24 16 0 9 7 0 0 0 0
May 25 8 3 1 2 1 1 0 0
May 26 22 11 1 9 1 0 0 0
May 27 50 10 19 10 5 6 0 0
May 28 13 0 3 5 4 0 1 0
May 29 3 3 0 0 0 0 0 0
Total 235 30 64 94 28 18 1 0

Notable tornadoes

Eldon – Jefferson City, Missouri

File:Jefferson City, MO tornado damage May 22, 2019.jpg
Numerous homes sustained major roof damage across Jefferson City

A tornado spawned near the town of Eldon, Missouri and travelled through the town at EF1 strength,[61] damaging a few homes and impacting cars along U.S. Route 54 before approaching Jefferson City.[62] In Jefferson City, many homes and businesses were damaged or destroyed at high-end EF3 intensity. Approximately 500 cars at a single dealership were damaged or destroyed, with losses estimated at $15–30 million.[63] The downtown area received substantial damage, with the tornado missing the State Capitol by less than half a mile.[64] The majority of damage occurred along a 3 mi (4.8 km) swath through the city. Twenty people required rescue from collapsed structures.[65] The tornado then crossed the Missouri River and dissipated in an open field shortly after.[64]

Jefferson City residents had at least 30 minutes advance warning before the tornado hit. The American Red Cross opened one shelter in Jefferson City and two in Eldon. Spokeswoman Sharon Watson says 50 people were at the Jefferson City shelter as of late morning.[66] On May 27, Governor Mike Parson activated the Missouri National Guard to assist with clean up efforts.[67]

El Reno, Oklahoma

At 10:28 p.m. CDT on May 25th, a small but strong QLCS tornado touched down just north of Interstate 40 on the south side of El Reno, Oklahoma. The tornado tore a 75 yard wide path through a motel and a trailer park. Damage at these sites was rated EF3. The tornado would continue on for 2.2 miles before lifting at 10:32 p.m. east of town. Residents in El Reno had less than 5 minutes of lead time before the tornado touched down. 2 deaths were confirmed along with 29 injuries.[68]

Brookville – Dayton – Beavercreek, Ohio

Lua error in package.lua at line 80: module 'strict' not found.

File:Dayton Ohio Tornado Damage.jpg
Damage to roofs and homes caused by an EF3 tornado in Dayton, Ohio

Around 1:47 UTC on May 28 (10:47 p.m. on May 27 local time), a tornado struck Brookville, Ohio. Numerous houses sustained major damage, with some being shifted off their foundation. Trees were uprooted in this area. With a large and destructive tornado confirmed on the ground, the NWS issued a rare Tornado Emergency for Greene and Montgomery counties, including the city of Dayton.[69] Traveling east-southeast, the tornado reached northern neighborhoods of the city around 2:07 UTC (11:07 p.m. local time). By 2:20 UTC (11:20 p.m. local time) the tornado impacted communities near Beavercreek. Multiple homes also had their second floors destroyed.[70] The National Weather Service's preliminary survey classified this tornado to be of EF3 strength with estimated wind speeds of 140mph, although this number could change.[71] Around 11:50 local time a second tornado tore through the Dayton area and has a preliminary rating of EF3 strength.

Lawrence - Linwood - Bonner Springs, Kansas

File:Linwood, Kansas, tornado damage May 28, 2019.jpg
A home near Linwood, Kansas, that was leveled by an EF4 tornado on May 28.

A massive wedge tornado, up to a mile wide, spawned ENE of Overbrook at 6:05 PM CDT, moving northeast the tornado moved into Douglas County, Kansas where it intensified hitting the city of Lawrence as an EF3 tornado, causing major damage on the south and east sides of town. [72] After hitting Lawrence, the tornado crossed the Kansas River and hit Linwood, leveling a well-built home at EF4 intensity with peak winds estimated to be 170 MPH.[73] Many other buildings were damaged at EF2 and EF3 intensity, including multiple other homes and an industrial greenhouse north of town. The tornado continued northeast, gradually weakening and causing minor damage, before dissipating just to the west of Bonner Springs in Leavenworth County, Kansas after traveling 31.82 miles for 55 minutes, and injuring 18 people.

Homeowner Brian Perry told KSHB that his camper was “gone” and his garage “didn’t hold up up too well” through the tornado. “Sucked the basement window right out, clear through the basement. Blew doors out of the inside of the basement,” Perry told the station. “Pretty wild. Never been through anything like it in my life.”[74]

Roads into Linwood were blocked off on Tuesday night after power lines and trees were left downed by the tornado.[75][76] The Kansas City International Airport, over 40 miles away from the area affected by the twister, reported debris on the runway, leading to flight cancellations.

Non-tornadic effects

Flooding

This storm system prolonged an ongoing heavy precipitation event across much of the southern Plains, Midwest, and eastern Canada, which included an unusually late heavy snow event in the Midwest.[77] In eastern Canada, the previous flooding was already being described as 100-year events.[78] Most of this region had received between 5 and 10 inches of rain during April.[79][80]

Several localities had broken April precipitation records before the additional rainfall from the May 2019 outbreak.[77] The Quad Cities of Iowa and Illinois had just ended a record-breaking 51-day record for most days above major flood stage on May 12 before the new set of storms hit; many of the upstream cities along the Mississippi and Ohio were in a similar position.[81] Much of the northeastern U.S. as well as eastern Canada had been dealing with continual rain since snowmelt, which had been causing previous extensive flooding.[82][80] The addition of the wide-reaching heavy rainfall from the May series of storms to the already-saturated ground intensified river flooding and flash flooding effects.

Flash flooding

Many locations in the Great Plains set new May rainfall records. Bartlesville, Oklahoma broke its previous May record of 10.31 inches by more than 4 inches of rain. Wichita, Kansas and Enid, Oklahoma recorded their second-highest May rainfall with nearly 13 inches of rain.[5][83] The torrential rain resulted in frequent flash flooding.

One-third of all flash flooding reports during April and May came from Kansas, Oklahoma, and Missouri.[84] A rare high risk outlook for excessive rainfall was issued for the region surrounding Oklahoma City on May 20.[85] By May 28, every single county in Oklahoma was under a state of emergency due to tornadoes or flooding.[86]

In at least one case, the NWS assessment team was unable to determine tornado-specific damage due to continuing flooding.[87]

On May 8, a man drowned in Austin, Texas after he was swept away by a flash flood.[88] A woman drowned in her vehicle on May 21 after driving around barricades northeast of Oklahoma City.[89] A 4-year-boy was swept away in a flooded creek in Indiana.[90] One person drowned in his van near Fort Chaffee, Arkansas.[91]

Riverine and lakeshore flooding

Large parts of the Mississippi River system were already in the midst of the longest-lasting flood fight since 1927 before the current severe storm exacerbated the situation. On May 21, Baton Rouge, Louisiana broke the previous record for its longest ever flood event, at 136 days. Vicksburg, Mississippi has been in continuous flood stage since February 17.[81] The Missouri River at Jefferson City reached its highest level since 1995. The Mississippi River at St. Louis is reaching a second crest in less than a month, surpassed only by the Great Flood of 1993.[5] The Morganza Spillway upriver from Baton Rouge, Louisiana, will be opened on June 2 for the third time in its history; it is opened when river flows at the Red River Landing are predicted to reach 1.5 million cf.[92][93] The Bonnet Carré Spillway has been opened twice in the same year for the first time since it was built in 1931.[93] The flood flight is currently in its 216th day, and is expected to surpass the 1973 record of 225 days.[93]

The Arkansas River and much of its associated watershed broke record flooding levels on May 26 and continued to rise during the following week.[2][94] However, water management systems have protected Little Rock from record-level flooding.[5]

Flooding in Canada broke records after the new round of storms. Several cities in Ontario, Quebec, and the Maritimes declared states of emergency, including Montreal, Quebec, Huntsville, Ontario, Fredericton, New Brunswick, and the twin cities of Ottawa, Ontario and Gatineau, Quebec. The new flooding blocked the Trans-Canada Highway near Fredericton.[95][96]

Lake Ontario reached flood levels due to record inflow of water it is receiving from Lake Erie.[97] On May 27, lakeshore flood warnings were issued along the New York shoreline between Munroe County and the Canadian border.[98]

On May 14, two people drowned on a flooded rural road 40 miles north of St. Louis.[90] One man died in Kay County, Oklahoma, on May 23 after being surrounded by floodwater from the Chikaskia River.[99]

Other non-tornadic effects

These storms were characterized by heavy rainfall which frequently wrapped around the tornado. Zeniolople, Pennsylvania received more than 4 inches of rain in 24 hours during May 28 and 29.[100] On May 21, two people were killed in a traffic accident in Missouri when their vehicle lost traction in heavy rain.[101]

Most of the tornadic storms were accompanied by severe hail. Baseball-sized hail was reported in Colorado and Nebraska.[1] On May 28 and 29, softball-sized hail caused considerable damage in Armstrong and Venango counties, Pennsylvania.[100]

Severe thunderstorms with widespread straight-line wind damage were reported in both the United States and Canada.

Several high-use areas not directly struck by tornadoes were covered by extensive blown or falling debris. In Ohio, highway snowplows were used to clear Interstate 75 on May 28.[102][103]

Although the May 28 tornado warning for Kansas City International Airport expired without a tornado after an hour, it had to stay closed to remove debris from its runways. Much of the debris came from the Linwood tornado, which had struck 47 miles away. The airport was not in operation again until after midnight. Flights were still being cancelled as late as 7:30 am May 29.[104]

Aftermath

States of emergency were declared in every county in Oklahoma.[86] Pre-existing states of emergency were extended in Iowa and Nebraska.[105] States of emergency were also declared by the governor in Arkansas,[106] Ohio,[107] Mississippi,[108] and Missouri[109] because of the flooding and tornadoes. Texas extended a previous state of emergency due to Hurricane Harvey, but did not post any new declarations.[110] The mayor declared a state of emergency in Zeniolople, Pennsylvania, after it received more than 4 inches of rain in 24 hours.[100]

Transportation interruptions

Road, rail, and air transportation was seriously affected by the flooding and tornadoes.

Jefferson City Memorial Airport has been closed due to flooding.[109] Kansas City International Airport was closed for half a day while debris was being removed from its runways.[104]

More than 500 roads were closed across Missouri, including Interstate 29 near the Iowa border.[111] Interstate 75 near Dayton was closed for a day while snowplows removed debris.

Amtrak experienced major disruptions across the Midwest and eastern U.S. All Amtrak service between Kansas City and St. Louis has been suspended due to flooding from the Missouri River.[111] Amtrak service between Kansas City and Hutchinson, Kansas, was also halted.[109] Both routes were served by buses until the flooding abates. An Amtrak train was stopped between New York City and Pittsburgh on May 29 due to fallen trees.[112]

Electricity outages

In the Dayton region, 80,000 people were without power on May 28 and 29.[113] People using generators in confined spaces led to an increase in hospital admissions due to carbon monoxide poisoning.[113]

In eastern Canada, electricity outages were minor, mostly caused by windstorms associated with the greater storm systems. Although they affected thousands of people at different times throughout the day, all power was restored by the end of the day.

Boil water advisories

Dayton, Trotwood, Montgomery County and parts of Greene County were placed under a boil water advisory on May 28.[114]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ https://www.accuweather.com/en/weather-news/live-intense-thunderstorms-erupt-over-oklahoma-as-new-round-of-severe-weather-unfolds/70008345
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ 64.0 64.1 Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ 77.0 77.1 Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ 80.0 80.1 Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ 81.0 81.1 Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ 86.0 86.1 Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ 90.0 90.1 Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ 93.0 93.1 93.2 Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ [1][dead link]
  95. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  96. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  97. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  98. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  99. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  100. ↑ 100.0 100.1 100.2 Lua error in package.lua at line 80: module 'strict' not found.
  101. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  102. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  103. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  104. ↑ 104.0 104.1 Lua error in package.lua at line 80: module 'strict' not found.
  105. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  106. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  107. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  108. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  109. ↑ 109.0 109.1 109.2 Lua error in package.lua at line 80: module 'strict' not found.
  110. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  111. ↑ 111.0 111.1 Lua error in package.lua at line 80: module 'strict' not found.
  112. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  113. ↑ 113.0 113.1 Lua error in package.lua at line 80: module 'strict' not found.
  114. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Tornado_outbreak_of_May_2019&oldid=725943341"