Flood Warning Active for South Fork Licking River at Heath
Official weather records show a flood warning in effect for the South Fork Licking River at Heath through Monday morning.
3 reports on this incident · first at Aug 17, 2026, 12:24 a.m. ET
Hazard products are revised and cancelled as conditions change. Check the National Weather Service for the current alert before acting on this report.
Earlier reports
Aug 17, 2026, 1:24 a.m. ET
National Weather Service Outlines Flood Impacts Along South Fork Licking River at Heath
At 17.0 feet, minor flooding along the South Fork Licking River at Heath is affecting areas of Licking View Drive near Livingston Court, according to official weather records from the National Weather Service Wilmington OH. Official records also report that the soccer and baseball fields of Hobak Park are flooded, with minor flooding currently occurring and forecast to continue.
The Flood Warning takes effect at 11:57 PM on August 16, 2026, and expires at 10:00 AM on August 17, 2026. Official weather records advise motorists to turn around and not drown when encountering flooded roads, noting that most flood deaths occur in vehicles. Additional information is available at www.weather.gov/iln.
Aug 17, 2026, 12:24 a.m. ETFirst report
Flood Warning Issued for South Fork Licking River at Heath
The situation is developing as official weather alert records from the National Weather Service Wilmington OH indicate a flood warning is in effect for 1 zone at the South Fork Licking River at Heath. Minor flooding is occurring and minor flooding is forecast.
According to official records, the warning period begins at 11:57 PM on August 16, 2026, and ends at 10:00 AM on August 17, 2026. At 17.0 feet, some areas of Licking View Drive near Livingston Court are flooded, and the soccer and baseball fields of Hobak Park are also flooded.
Official records state: Turn around, don't drown when encountering flooded roads. Most flood deaths occur in vehicles. Additional information is available at www.weather.gov/iln.
Was this report accurate and useful?
Sources
Revision history
- Version 117 Aug 2026, 05:24current
First published.
- Version 117 Aug 2026, 04:24current
First published.
- Version 117 Aug 2026, 05: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.