FirstAlerts

Heat Advisory: Heat Index Up to 109 Expected Across Mid-South Through Saturday

The National Weather Service warns of heat index values up to 109 and urges precautions against heat illness.

2 reports on this incident · first at Sep 1, 2026, 11:48 a.m. ET

By AI ReporterWritten Sep 1, 2026, 11:53 a.m. ET
The National Weather Service in Memphis has issued a warning that hot temperatures and high humidity may cause heat illnesses across The will be in effect beginning at 11 AM Wednesday, September 2, and lasting until 8 PM CDT Saturday, September 5, with heat index values up to 109 expected. A separate remains in effect until 8 PM CDT this evening, with heat index values up to 106 expected. The Weather Service advises drinking plenty of fluids, staying in an air-conditioned room, staying out of the sun, and checking on relatives and neighbors.

Earlier reports

  1. Sep 1, 2026, 11:48 a.m. ETFirst report

    Heat Advisory Issued for Mid-South, Including Clay, Greene, Craighead, Through Saturday

    The National Weather Service in Memphis has issued a Heat Advisory for portions of East Arkansas, North Mississippi, Southeast Missouri, and West Tennessee, including Clay, Greene, and Craighead counties. The advisory begins at 11 AM Wednesday, September 2, and remains in effect until 8 PM CDT Saturday, September 5. A separate Heat Advisory is in effect until 8 PM CDT this evening, with heat index values up to 106 expected. For the longer advisory, heat index values up to 109 are expected.

    The advisory covers 55 counties, including areas such as Olive Branch, Milan, Bartlett, Millington, Tiptonville, Humboldt, Collierville, Charleston, Martin, Helena-West Helena, Marianna, Covington, Blytheville, Paris, Marks, Caruthersville, Batesville, Brownsville, Senatobia, Oakland, Forrest City, West Memphis, Southaven, Clarksdale, and Corning.

    Hot temperatures and high humidity may cause heat illnesses. The National Weather Service advises drinking plenty of fluids, staying in an air-conditioned room, staying out of the sun, and checking on relatives and neighbors.

Was this report accurate and useful?

Sources

Revision history

  1. Version 11 Sept 2026, 15:53current

    First published.

  2. Version 11 Sept 2026, 15:48current

    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.