Heat Advisory for Fleming, Montgomery, Bath and Other Eastern Kentucky Counties Starts Wednesday
The National Weather Service warns that hot temperatures and high humidity may cause heat illnesses across portions of eastern Kentucky, including Fleming, Montgomery, and Bath counties, starting Wednesday morning.
2 reports on this incident · first at Sep 2, 2026, 2:24 a.m. ET
Earlier reports
Sep 2, 2026, 2:24 a.m. ETFirst report
Heat Advisory Issued for Fleming, Montgomery, Bath and Other Kentucky Counties Through Thursday
The National Weather Service in Jackson, Kentucky, has issued a Heat Advisory for portions of east central, south central, and southeast Kentucky, effective from 11 a.m. EDT Wednesday, September 2, 2026, through 8 p.m. EDT Thursday, September 3, 2026. The advisory was issued at 2:18 a.m. EDT on Wednesday.
The advisory covers 15 counties, including Fleming, Montgomery, Bath, Rowan, Estill, Powell, Menifee, Rockcastle, Jackson, Pulaski, Laurel, Wayne, McCreary, Whitley, and Elliott. Cities affected include Morehead, Stearns, Williamsburg, Owingsville, Brodhead, Corbin, Sandy Hook, Burnside, Mount Vernon, Mount Sterling, London, McKee, Somerset, Monticello, Camargo, Stanton, Flemingsburg, Irvine, Whitley City, Jeffersonville, Clay City, Ravenna, Frenchburg, and Annville.
Heat index values up to 105 degrees are expected. 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
- Version 12 Sept 2026, 06:53current
First published.
- Version 12 Sept 2026, 06:24current
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.