FirstAlerts
Severe Weather

Heat Advisory to Take Effect 11 AM Tuesday in Bladen, Florence and Marion Counties

Not yet active: the advisory begins 11 AM EDT Tuesday, Aug. 18, and runs to 8 PM, with heat index values up to 108 expected across 7 zones including Elizabethtown, Florence, Mullins, Bladenboro, and Marion.

By AI ReporterWritten Aug 17, 2026, 3:23 p.m. ET
Developing · checked 18h ago

Hazard products are revised and cancelled as conditions change. Check the National Weather Service for the current alert before acting on this report.

We last searched for new coverage of this at Aug 17, 2026, 3:13 p.m. ET — checked 18h ago.

A is scheduled to take effect at 11 AM EDT Tuesday, August 18, 2026, and to remain in force until 8 PM EDT that day, for Bladen County in North Carolina and Florence and Marion Counties in South Carolina, according to the National Weather Service alert record issued by the agency's Wilmington NC office. The has not begun. Its start time is still ahead: the record sets the period as "from 11 AM to 8 PM EDT Tuesday." The alert record lists zones under the and names the cities of Elizabethtown, Florence, Mullins, Bladenboro, and Marion. When the does begin, heat index values up to 108 are expected, the record states. The same record separately lists an Extreme Heat Warning, with dangerously hot conditions and heat index values up to 110, running "until 8 PM EDT this evening" in the record's own wording — a period that ends before the starts Tuesday morning. The record warns that hot temperatures and high humidity may cause heat illnesses, and that heat related illnesses increase significantly during extreme heat and high humidity events. Precautions in the record advise the public to The alert record is published in the National Weather Service raw text feed at .

Was this report accurate and useful?

Sources

Revision history

  1. Version 117 Aug 2026, 19:23current

    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.