Heat Advisory for Warren, Halifax, Orange and Other NC Counties from 11 AM to 8 PM EDT Wednesday
The National Weather Service warns that hot temperatures and high humidity may cause heat illnesses Wednesday from 11 AM to 8 PM EDT in central and eastern North Carolina.
2 reports on this incident · first at Sep 1, 2026, 1:53 p.m. ET
Earlier reports
Sep 1, 2026, 1:53 p.m. ETFirst report
Heat Advisory Issued for Warren, Halifax, Orange and Other North Carolina Counties
The National Weather Service in Raleigh has issued a Heat Advisory for Wednesday, September 2, from 11 a.m. to 8 p.m. EDT. The advisory covers the Coastal Plain and a majority of the eastern Piedmont and Sandhills, including Warren, Halifax, Orange, Durham, Franklin, Nash, Edgecombe, Chatham, Wake, Johnston, Wilson, Moore, Lee, Harnett, Wayne, Richmond, Scotland, Hoke, Cumberland, and Sampson counties. Cities affected include Spring Hope, Norlina, Wilson, Aberdeen, Rockingham, Scotland Neck, Louisburg, Cary, Angier, Fayetteville, Rocky Mount, Chapel Hill, Wake Forest, Sanford, Apex, Raeford, Durham, Pittsboro, Clinton, Dunn, Tarboro, Spring Lake, Princeville, Siler City, and Clayton.
Heat index values up to 107 degrees are expected. The advisory warns that hot temperatures and high humidity may cause heat illnesses. The NWS advises drinking plenty of fluids, staying in an air-conditioned room, staying out of the sun, and checking on relatives and neighbors. It also recommends wearing lightweight and loose-fitting clothing, limiting strenuous activities to early morning or evening, and taking action when symptoms of heat exhaustion or heat stroke appear.
The advisory was issued at 1:46 p.m. EDT on Tuesday, September 1, and remains in effect until 8 p.m. EDT Wednesday.
Was this report accurate and useful?
Sources
Revision history
- Version 11 Sept 2026, 17:53current
First published.
- Version 11 Sept 2026, 17:53current
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.