FirstAlerts
Severe Weather

Flood Watch in Effect for Athens, Perry, Morgan and 10 More Counties in Ohio and West Virginia

Flash flooding from excessive rainfall is possible from 4 PM EDT Aug. 19 through 2 PM EDT Aug. 20 across 13 zones stretching from McArthur and Marietta to Parkersburg and Clarksburg, according to the National Weather Service Charleston WV.

By AI ReporterWritten Aug 19, 2026, 5:29 p.m. ET
A is in force for zones across portions of southeast Ohio and West Virginia, where flash flooding caused by excessive rainfall is possible, according to the product issued by the and carried on the NOAA raw text data feed at . The product was issued at 12:35 PM EDT on August 19, 2026. The begins at 4:00 PM EDT on August 19, 2026, and runs to 2:00 PM EDT on August 20, 2026; the record states the timing as "" The area, as listed in the record, covers the Ohio counties of Athens, Meigs, Morgan, Perry, Vinton and Washington, and the West Virginia counties of Doddridge, Harrison, Pleasants, Ritchie, Taylor, Tyler and Wood — zones in all. Cities named in the record are McArthur, Pomeroy, Harrisville, Hamden, Vienna, Middlebourne, Parkersburg, Sistersville, Grafton, St. Marys, Marietta, Clarksburg, Belmont, Belpre, McConnelsville, New Lexington, Athens, Stockport, Somerset, West Union, Pennsboro, Crooksville, Paden City and Bridgeport. On expected impacts, the record states that excessive runoff may result in flooding of rivers, creeks, streams, and other low-lying and flood-prone locations, and that creeks and streams may rise out of their banks. The weather service's instruction to residents in the area is to monitor later forecasts and be prepared to take action should Flash Flood Warnings be issued. The record directs the public to https://www.weather.gov/rlx, as well as the office's X and Facebook pages, for additional information.

Was this report accurate and useful?

Sources

Revision history

  1. Version 119 Aug 2026, 21: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.