Catastrophes · Alerte à la tornadeLa tempête d’Asherville a-t-elle produit une tornade ? Son issue reste inconnueRédigé 1 octobre 2026 à 05:04 UTCRegarderTranscription0:09Radar indicated rotation in a severe thunderstorm over Asherville.0:13People in east-central Mitchell County faced an immediate instruction to shelter0:16from a possible tornado.0:18The warning scheduled window has now passed, but that does not establish that0:21conditions became safe.0:23What happened to the storm after the warning, and did it leave a tornado, damage, or0:27injuries behind?0:27The storm was over Asherville, about nine miles southeast of Beloit, when the0:32warning took effect.0:33Its reported movement was northeast at 20 miles per hour.0:36The warning covered east-central Mitchell County in north-central Kansas, not the0:41entire county.0:42Both the location and the movement describe the storm at issuance.0:45They do not establish where it traveled afterward, whether its speed changed, or0:49whether it maintained its rotation.0:50The storm was described as capable of producing a tornado, but a tornado on the0:54ground was not confirmed.0:56Radar indicated rotation was the basis for the warning.0:59That distinction matters.1:00The alert identified a threat requiring protective action, not a verified touchdown.1:04Nothing established here resolves whether the rotating storm went on to produce one.1:08The warning scheduled window was just 25 minutes.1:11It was issued at 8:50 p.m.1:12Central Daylight Time on September 30th, 2026, effective immediately and scheduled1:17to end at 9:15 that evening.1:19In Coordinated Universal Time, those points were 1:50 and 2.15 a.m.1:23on October 1st.1:24That interval described the planned alert period.1:27It did not establish how long a tornado lasted or promised that dangerous conditions1:32would end at 9:15.1:34People inside the warning area were instructed to take cover immediately.1:38The protective instructions were to move into an interior room on the lowest floor1:41of a well-built building and stay away from windows.1:44The practical priority was reaching shelter during the warning rather than waiting1:47for confirmation that a tornado had touched down.1:50Those were the instructions for this alert.1:52They are not evidence that the warning remains active now.1:54A tornado reported near Milburger in Hoisington does not establish a touchdown near1:58Asherville.2:00Other September 30th storm accounts concern Ashe Valley and Rush and Barton2:04counties.2:04They include a Barton County warning scheduled until 5.15 p.m.2:08Central Daylight Time and a storm near Milburger and Hoisington moving at 30 miles2:12per hour.2:13Those locations, times, and movement differ from this warning.2:17They cannot establish what happened to the Asherville storm.2:19No verified subsequent track, touchdown report, damage assessment, or injury count2:24is established for this event.2:26Independent authentication of the full original alert payload also remains2:30unresolved.2:31No event-matched official follow-up establishes whether the warning was canceled,2:34extended, replaced, or allowed to expire unchanged.2:37The answer to what happened afterward, therefore, remains unknown.2:40The rotating storm triggered a shelter warning, but its later behavior and impacts2:44have not been verified.2:46The absence of a matching impact report does not establish that no tornado, damage,2:49or injuries occurred.2:50The elapsed scheduled warning window is not at all clear.Lire l’articleChronologie de l’histoireHeyDexLe format court ↗Couverture liéeDéveloppement ultérieur·2 oct., 8:26 UTCLe Kansas fait état de 15 signalements de tornades, mais le bilan complet de l’épisode reste inconnu
