FirstAlerts

Heat Advisory Wednesday for Columbus, Pender, New Hanover, Brunswick and Horry Counties

Heat index values up to 109 are expected from 11 AM to 8 PM EDT Wednesday across coastal areas from Wilmington to Myrtle Beach, according to the National Weather Service alert record.

By AI ReporterWritten Aug 18, 2026, 3:49 p.m. ET
A takes effect Wednesday for a stretch of the southeast North Carolina and northeast South Carolina coast, including Wilmington, Myrtle Beach, Georgetown and Whiteville. The product issued by — the raw NWS alert record posted to the agency's public text feed — was issued at 2:01 PM EDT on August 18, 2026. It carries the official headline "." The begins at 11 AM EDT on Wednesday, August 19, 2026, and expires at 8 PM EDT the same day. The record lists zones across The alert record states that heat index values up to 109 are expected under the . For the Extreme Heat Warning, the same record describes dangerously hot conditions with heat index values up to 111, in force until 8 PM EDT this evening. Hot temperatures and high humidity may cause heat illnesses, and the record notes that heat related illnesses increase significantly during extreme heat and high humidity events. The zones named in the are Columbus, Inland Pender, Coastal Pender, Inland New Hanover, Coastal New Hanover, Inland Brunswick, Coastal Brunswick, Coastal Horry, Inland Georgetown, Coastal Georgetown, Central Horry and Northern Horry. Cities listed in the alert include North Myrtle Beach, Lake Waccamaw, Wilmington, Sunset Beach, Georgetown, Masonboro, Little River, Red Hill, Long Beach, Seagate, Leland, Loris, Tabor City, Garden City, Southport, Whiteville, Socastee, Myrtle Beach, Oak Island, Ogden, Surf City, Burgaw, Myrtle Grove, Murrells Inlet and Chadbourn. The precautions in the record:

Was this report accurate and useful?

Sources

Revision history

  1. Version 118 Aug 2026, 19:49current

    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.