May 26–31, 2013 tornado outbreak

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
May 26–31, 2013 tornado outbreak
The storm system on May 31
The storm system responsible for the tornado outbreak at 6:10 p.m. CDT May 31
Type Tornado outbreak
Duration May 26–31, 2013
Tornadoes confirmed 115
Max rating1 EF3 tornado
Duration of tornado outbreak2 5 days, 10 hours, 43 minutes
Highest winds >295 mph (475 km/h) (El Reno, OK EF3 tornado on May 31)[1](The winds were not used in the survey; thus, the tornado was rated EF3 instead of EF5.)
87 mph (140 km/h) (Tinker Air Force Base, OK non-tornadic on May 31)[2]
Largest hail 5.25 inches (13.3 cm) in diameter NW of Montrose, Kansas on May 27[3][4]
Damage Unknown
Casualties 9 fatalities confirmed (+18 non-tornadic), 172 injuries
1Most severe tornado damage; see Enhanced Fujita scale 2Time from first tornado to last tornado

The May 26–31, 2013 tornado outbreak was a prolonged and widespread tornadic event that affected a large portion of the United States. The outbreak was the result of a slow-moving but powerful storm system that produced several strong tornadoes across the Great Plains states, especially in Kansas and Oklahoma. Other strong tornadoes caused severe damage in Nebraska, Missouri, Illinois, and Michigan. The outbreak extended as far as New York. 27 fatalities were reported in total, with nine resulting from tornadoes (eight in Oklahoma and one in Arkansas).

Meteorological synopsis

On May 22, an upper-level low moved eastward over the Western United States, with forward progression limited by a blocking high around the Northern Plains and Great Lakes.[5] With ample low-level moisture streaming north ahead of the low into an area of moderate instability, scattered severe weather was anticipated over parts of Colorado, Kansas, and Nebraska starting on May 24.[6]

The first tornado associated with the system was a small landspout tornado that touched down in rural Idaho on May 26.[7] The tornadic activity became more intense the following day. On May 27, while only scattered tornadoes touched down, four of them were strong and caused considerable damage in parts of Kansas and Nebraska.[8] One tornado near Lebanon, Kansas reached EF3 intensity, and an EF2 near Marysville caused major damage to several structures. In Nebraska, the town of Edgar took a direct hit from an EF2.[9][10]

Vigorous tornado activity continued on May 28. While the Storm Prediction Center only issued a slight risk that day, widespread tornadoes touched down in several states, some strong to violent.[11] Several powerful supercell thunderstorms developed in central Kansas that afternoon, and large tornadoes were reported. Near the town of Corning, a strong EF3 carved an unusual V-shaped path through rural areas west of town, and completely destroyed two homes.[12] An even larger tornado, an EF3 wedge that was over a quarter mile wide, touched down just west of Bennington, and remained nearly stationary in a field for over an hour. This tornado resulted in relatively moderate damage, but killed over 100 head of livestock.[13] The tornado was originally rated EF4 based on mobile radar readings, but ground surveys did not reveal damage indicative of EF4 wind speeds, and the tornado was downgraded to an EF3 as a result.[14] Later that evening, large tornadoes were sighted in southern Michigan, prompting several tornado emergencies. A total of six tornadoes were confirmed to have touched down in areas near Flint, two of which reached EF2 intensity and caused significant damage.[15] Numerous weak tornadoes were documented in other states.[11]

On May 29, the Storm Prediction Center issued a moderate risk for parts of Texas, Oklahoma, and Kansas. The outlook included a 10% hatched risk for tornadoes. A separate slight risk was issued for parts of New England.[16] In the main risk area, only scattered weak tornadoes touched down, though a mile-wide EF2 wedge tornado touched down in upstate New York near Schenectady.[17][18] On May 30, for the second day in a row, the Storm Prediction Center issued a moderate risk with a 10% hatched risk of tornadoes, this time for eastern Oklahoma and a small part of Kansas. Numerous tornadoes touched down in Oklahoma and Arkansas, including a few that were strong.[19][20] An EF2 ripped through the Tulsa suburb of Broken Arrow, resulting in severe damage to homes and businesses.[21] A brief EF1 near Tull, Arkansas unfortunately caused a fatality due to a falling tree.[22]

On the morning of May 31, a strong cap was in place over much of central Oklahoma into eastern Oklahoma. With dewpoints creeping into the low 70s, the Storm Prediction Center early on considered upgrading part of the moderate risk forecast zone to a high risk forecast zone. As the day went on, there was no upgrade, but it became evident the atmosphere was ripe with CAPE values in excess of 4000 J/kg. With the presence of an extremely unstable air mass over central Oklahoma, the Storm Prediction Center issued a Particularly Dangerous Situation Tornado Watch for much of the state during the afternoon of May 31 and lasting into the night. Later that evening, severe storms rapidly developed, and an extremely large and violent multiple-vortex tornado devastated areas near El Reno, Oklahoma, and killed eight people including three men from the storm chasing crew, TWISTEX. The tornado had been rated EF5 based on mobile radar readings,[23] [24] Other weak tornadoes and major flooding devastated parts of the Oklahoma City metro that evening.[25] Further north, a powerful squall line of severe storms with several embedded strong tornadoes developed in Missouri. One of the tornadoes, a large and rain-wrapped EF3, caused major damage in several St. Louis suburbs. Weak tornadoes touched down in several other states.[26][27][28]

Notable tornadoes

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

See also: List of tornadoes in the May 26–31, 2013 tornado outbreak
Confirmed tornadoes by Enhanced Fujita rating
EF0 EF1 EF2 EF3 EF4 EF5 Total
56 41 12 6 0 0 115

Bennington, Kansas

File:May 28, 2013 Bennington, Kansas tornado radar.gif
Animated radar loop (left, storm-relative velocity; right, reflectivity) of the nearly stationary supercell thunderstorm that spawned the EF3 tornado from 5:36–7:33 p.m. CDT (2236–0033 UTC).

A large, very slow-moving, and highly unusual EF3 wedge tornado remained on the ground for just over an hour as it executed a cyclonic loop in Ottawa County south of the town of Minneapolis and west of Bennington. It initially touched down several miles west of Bennington on May 28 at 5:39 p.m. CDT (2239 UTC). Upon formation, it snapped power poles and moved southeast before turning north as it approached U.S. Route 81. As the tornado reached the northern end of the track (its strongest point), it destroyed numerous outbuildings, downed trees and power poles, damaged farm equipment, and tipped over a large semi-like truck (while also moving the truck several feet). About 100 cattle were killed in this area as well. The tornado then moved to the southwest and destroyed the roof of a well constructed shed (while throwing the heavy metal shed door into a field), blew a trailer 40 yards (37 m), snapped many more power poles, and downed numerous trees. A home that was under construction lost all four exterior walls and a fifth-wheel camper was blown 200 yards (180 m). A second home suffered minor shingle damage and impact dents in the siding from flying debris, a few more sheds/outbuildings were either damaged or destroyed, and a third home had siding and chimney damage (mostly from debris impact) and was slightly moved off of the foundation. The tornado lifted around 6:45 p.m. CDT (2345 UTC), just to the south-southwest of where it touched down.[29][30]

File:May 28, 2013 Bennington, Kansas tornado.jpeg
The May 28 EF3 Bennington, Kansas tornado

Initially, the tornado was rated as an EF4, with the rating based on Doppler on Wheels surface wind measurements, which indicated a far larger and stronger tornado. Gusts were measured far into the EF5 intensity range, with a peak value of 247 mph (398 km/h); however, those winds were measured 300 ft (91 m) above the surface. Based on damage indicators and the surface wind measurements, the highest winds that translated to the ground were around 150 mph (240 km/h).[14][29][31] Because mobile doppler radar data is not a method by which tornadoes are rated, it was later officially downgraded to an EF3. Despite the downgrade, the National Climatic Data Center maintains that the Bennington tornado was violent, and likely reached EF4 intensity at some point in its life.[14] The wind gusts above the surface were among the highest ever measured/estimated on record, comparable to the highest non-tornadic gust of 253 mph (407 km/h) measured during Cyclone Olivia in 1996.[32] Some damage was observed from areas that were not directly in the path of the tornado, suggesting a very large wind field as well.[29][30] Winds of 150 mph (240 km/h) were also measured over an area approximately 0.5 mi (0.80 km) wide while 100 mph (160 km/h) winds covered an area 1.5 mi (2.4 km) in diameter. Due to the tornado's slow motion, several areas in its path were likely exposed to winds well in excess of 100 mph (160 km/h) for at least 45 minutes.[31]

El Reno, Oklahoma

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

Main article: 2013 El Reno tornado

The tornado initially touched down at 6:03 p.m. CDT (2303 UTC) about 8.3 miles (13.4 km) west-southwest of El Reno. The storm rapidly grew and became violent. Remaining over mostly open terrain, the tornado did not impact many structures; however, measurements from mobile Doppler radars revealed extreme winds in excess of 295 mph (475 km/h) within the tornado. As it crossed Highway 81, it had grown to a record-breaking width of 2.6 miles (4.2 km). Turning northeastward, the tornado soon weakened. After crossing Interstate 40, the tornado dissipated around 6:43 p.m. CDT (2343 UTC) after tracking for 16.2 miles (26.1 km).[33][34][35] A satellite tornado also occurred and such companion tornadoes tend to be observed with especially large and intense tornadoes.[36]

Although the tornado remained over mostly open terrain, dozens of storm chasers unaware of its immense size were caught off-guard. Along Highway 81, renowned chaser and researcher Tim Samaras, along with his son Paul and research partner Carl Young, were killed when their vehicle was tossed by the tornado or a sub-vortex associated with it.[35][37] Another amateur storm chaser was killed in the area.[38] Other storm chasers, including The Weather Channel's Mike Bettes and Reed Timmer, were either injured or had their vehicles damaged. Overall, the tornado was responsible for eight fatalities and an unknown number of injuries.[39][40][41]

Weldon Spring–Northern St. Louis County, Missouri

EF3 damage to a home west-southwest of Harvester, Missouri

The tornado touched down at 7:50 p.m. CDT (0050 UTC) on May 31, southwest of Weldon Spring in St. Charles County, Missouri. It downed trees, blew over empty trailers, and caused minor damage to construction equipment. It moved generally east-northeast into Weldon Spring Heights (on the south side of Weldon Spring) and caused roof, window, and solar panel damage to a few structures as well as downing more trees before crossing Interstate 64. The tornado continued moving east-northeast through densely populated residential areas of southern St. Charles County. Roofing was torn off of a middle school and blown 100 yards (91 m), many houses suffered varying degrees of roof (from minor damage to removal of entire roof), wall (from minor damage to total collapse), and overall structural damage, and hundreds of trees were downed. A shed was destroyed, a garage door was compromised and the roof was removed and blown away, another garage had a wall collapsed, and two more garages were completely destroyed. Only the interior walls were left standing at three homes when the tornado reached its strongest point east-northeast of Weldon Spring, west-southwest of St. Charles and Harvester, and south of St. Peters. The tornado continued causing damage in residential areas before crossing the Missouri River into St. Louis County and Earth City, Bridgeton, and the northern side of Maryland Heights as it moved along Interstate 70 near its intersection with Interstate 270.[42][43]

A casino on the east bank of the river had roof and siding damage and a tree limb was thrown into one of the walls. Many trees, power poles, and highway signs were downed in the area, a hotel sustained shingle and window damage, and the canopy was damaged at a Mobil gas station. The roof was damaged and windows were broken at an ITT Technical Institute building and a vehicle was flipped in the parking lot. Nearby, large doors were blown in at a warehouse-type building and three delivery trucks were blown over. Trees and power lines were downed and several homes and commercial buildings were damaged in Bridgeton to the east of SSM DePaul Health Center. Debris fell onto vehicles and trees fell onto houses in the area as well. The tornado continued damage as it moved just north of the St. Louis base of the Missouri Air National Guard at Lambert–St. Louis International Airport in Berkeley (which had previously taken a direct hit from an EF4 tornado on April 22, 2011). It then moved into residential areas on the northern side of Ferguson as a weaker tornado, only downing trees and power poles, a few of which landed on homes and cars. More trees were downed and one home suffered minor roof damage in the Dellwood area. The tornado downed even more trees as it crossed Interstate 270 again east of Florissant. Several trees landed on houses in the area and seven power poles were snapped along the interstate. The tornado moved north of Bellefontaine Neighbors, then northeast of town as it moved along Interstate 270. 2-foot (61 cm) in diameter trees were downed, one of which fell onto a house. It moved due east, causing widespread tree damage as it moved into the Riverview area in the extreme northeastern sections of the City of St. Louis. The tornado downed many trees on the banks of the Mississippi River, where it lifted at 8:25 p.m. (0125 UTC) just northeast of exit 34 on Interstate 270. The tornado was rated a mid-grade EF3, with winds up to 150 mph (240 km/h). It was on the ground for 35 minutes, traveled 32.5 miles (52.3 km), and had a maximum path width of 1 mile (1.6 km). Two minor injuries occurred in St. Charles County.[42][43]

Non-tornadic events

On May 28, Amarillo, Texas was battered by a major hailstorm. An estimated 35,000 vehicles and thousands of homes were damaged in the storm, with insured losses expected to reach $400 million.[44]

In addition to the tornadoes, the Oklahoma City metro area was subjected to severe flash flooding on May 31 and into the early morning hours of June 1, with initial estimates of 7 to 12 inches of rain having fallen as storms continued to train across the area during the evening and overnight hours. The flooding combined with damage from the tornadoes complicated efforts of emergency services personnel to render aid to areas impacted by the storm.[45] With the flooding and tornadoes occurring simultaneously, a family of seven sought refuge from a tornado in a drainage ditch in southern Oklahoma City. They were soon overwhelmed by flood waters and a four-year-old boy was swept away and died. An infant was also swept away but was rescued and hospitalized in critical condition.[46] At least nine people were killed as a result of the floods.[41][47][48] One person remained missing as of June 3.[49]

On May 29, a man was killed by a falling tree in Verona, New York during a severe thunderstorm.[50] Flash flooding in Scott County, Arkansas killed four people, including a sheriff.[51][52] Missouri authorities confirmed three deaths as a result of high water that occurred in the counties of Lawrence, Miller and Reynolds.[53]

Aftermath

More than 210,000 customers were left without power: 89,000 in Missouri, 86,000 in Oklahoma, 31,000 in Illinois, 3,000 in Arkansas, 1,000 in Kansas, and 500 in Indiana. According to the state transportation department, portions of more than 200 roads in Oklahoma were closed due to flooding.[54] On May 31, the National Oceanic and Atmospheric Administration (NOAA) announced it would no longer furlough employees under sequestration due to the outbreak of tornadoes.[55]

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 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. ↑ 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. ↑ 11.0 11.1 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. ↑ 14.0 14.1 14.2 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. ↑ 29.0 29.1 29.2 Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ 31.0 31.1 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ 35.0 35.1 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. ↑ 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ 43.0 43.1 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. ↑ 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.
Retrieved from "https://infogalactic.com/w/index.php?title=May_26–31,_2013_tornado_outbreak&oldid=719362626"