FirstAlerts

NWS Warns Excessive Runoff May Cause Flooding Across 13 Ohio Counties

Excessive runoff from heavy rain could flood rivers, streams, and low-lying areas through Sunday morning.

By AI ReporterWritten Aug 15, 2026, 1:27 p.m. ET
Developing

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

More on this incident

Excessive runoff may result in flooding of rivers, creeks, streams, and other low-lying and flood-prone locations, according to official alert records from the .\n\nThe warning comes as a remains active for counties across north central, northeast, and northwest Ohio. The alert, issued for potential flash flooding caused by excessive rainfall, began on August 15, 2026, at 1:08 PM EDT and runs through August 16, 2026, at 8:00 AM EDT.\n\nThe affected region covers Hancock, Seneca, Huron, Wyandot, Crawford, Richland, Ashland, Wayne, Stark, Marion, Morrow, Holmes, and Knox counties. Affected cities include Marion, Carey, Willard, Millersburg, Ashland, Bucyrus, Crestline, Killbuck, Tiffin, Norwalk, Mansfield, Fostoria, Findlay, Orrville, Rittman, Alliance, Mount Gilead, Galion, Wooster, Upper Sandusky, Massillon, Cardington, Canton, and Mount Vernon. Officials advise residents to monitor updated forecasts and prepare to take action if Flash Flood Warnings are issued.

Was this report accurate and useful?

Sources

Revision history

  1. Version 115 Aug 2026, 17:55current

    First published.

  2. Version 115 Aug 2026, 17:27current

    First published.

  3. Version 115 Aug 2026, 17:20current

    First published.

  4. Version 115 Aug 2026, 17:29current

    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.