Heat and Storm Alerts in Effect Across Southeast and Midwest
Conflicting reports describe heat advisories and severe thunderstorm watches across multiple states.
4 reports on this incident · first at Sep 4, 2026, 5:15 p.m. ET
Earlier reports
Sep 5, 2026, 5:18 p.m. ET
Severe Thunderstorm Watch Issued for Region
A Severe Thunderstorm Watch has been issued for the region, according to wtkr.com. The watch is in effect until either 10 p.m. EDT Friday, September 4, or 10 p.m. EDT Saturday, September 5, according to conflicting reports from wtkr.com.
Scattered thunderstorms capable of producing severe weather, particularly in North Carolina, will last through the early evening, wtkr.com reported. In a separate report, wtkr.com said strong to severe storms will continue to develop over the region this evening.
Sep 4, 2026, 5:53 p.m. ET
Severe Thunderstorm Watch Extended Through Friday, September 4, 2026
The Severe Thunderstorm Watch for the region has been extended and now runs until 10 p.m. Friday, September 4, 2026, according to wtkr.com. The watch was originally set to expire earlier Friday evening.
Strong to severe storms will continue to develop over the region this evening, wtkr.com reported.
Sep 4, 2026, 5:15 p.m. ETFirst report
Severe Thunderstorm Watch Issued for Region Through Friday Evening
A Severe Thunderstorm Watch is in effect for the region until 10 p.m. Friday, September 4, 2026, according to WTKR.com. The watch was issued as strong to severe storms are expected to continue developing over the area this evening.
The watch is scheduled to expire at 10 p.m. local time. Residents are advised to monitor weather conditions and heed any warnings that may be issued.
Was this report accurate and useful?
Sources
- First Warning Forecast: Much cooler weather arrives Labor Day weekendwtkr.com
- First Warning Forecast: Storms fade, pleasant conditions arrive in time for Labor Daywtkr.com
- First Alert: Less intense heat for the rest of Labor Day Weekendkfvs12.com
- First Alert: Labor Day with be rather hot and humid with low risk for severe stormswtok.com
Revision history
- Version 27 Sept 2026, 13:53current
Updated to reflect conflicting reports on alert level, hazard type, and end times, presenting them as sourced ranges.
- Version 25 Sept 2026, 21:18current
Updated to reflect conflicting end times and descriptions of the watch.
- Version 14 Sept 2026, 21:53current
First published.
- Version 17 Sept 2026, 13:22
First published.
- Version 14 Sept 2026, 21:15current
First published.
- Version 14 Sept 2026, 21:23
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.