Flood Watch Covers Tuscarawas, Carroll and Coshocton Counties, 16 Others in Ohio, Pennsylvania and West Virginia
A National Weather Service Pittsburgh PA flood watch, issued 12:36 PM EDT Aug. 19, 2026, runs from 4 PM EDT that afternoon through 2 PM EDT Thursday across 19 zones.
2 reports on this incident · first at Aug 19, 2026, 5:28 p.m. ET
Earlier reports
Aug 19, 2026, 5:28 p.m. ETFirst report
National Weather Service Issues Flood Watch for 19 Zones Across Three States
In a developing situation on August 19, 2026, the National Weather Service Pittsburgh PA issued an official Flood Watch at 12:36 PM EDT covering 19 zones across portions of east central Ohio, southwest Pennsylvania, and West Virginia. Official records state that flash flooding caused by excessive rainfall is possible across the region. According to the official record, the watch starts at 4:00 PM EDT on August 19, 2026, and expires at 2:00 PM EDT on August 20, 2026. Excessive runoff may result in flooding of rivers, creeks, streams, and other low-lying and flood-prone locations. The watch includes Belmont, Carroll, Coshocton, Guernsey, Harrison, Jefferson OH, Monroe, Muskingum, Noble, and Tuscarawas in Ohio; Greene and Washington in Pennsylvania; and Brooke, Hancock, Marion, Marshall, Monongalia, Ohio, and Wetzel in West Virginia. Cities in the affected areas include Steubenville, Cadiz, Cambridge, Weirton, St. Clairsville, Canonsburg, Morgantown, Washington, Waynesburg, Follansbee, Carrollton, Dover, New Philadelphia, Martins Ferry, Woodsfield, Fairmont, New Martinsville, Caldwell, Moundsville, Coshocton, Wellsburg, Wheeling, Zanesville, and Malvern. The agency advises residents to monitor later forecasts and be prepared to take action should Flash Flood Warnings be issued.
Was this report accurate and useful?
Sources
Revision history
- Version 119 Aug 2026, 21:29current
First published.
- Version 119 Aug 2026, 21:28current
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.