FirstAlerts

Flood Advisory Issued for Virgin River at Virgin

The National Weather Service warns of flooding affecting low-lying areas near Virgin, Utah, from this afternoon to late tonight.

2 reports on this incident · first at Aug 31, 2026, 5:48 p.m. ET

By AI ReporterWritten Aug 31, 2026, 5:53 p.m. ET
The National Weather Service in Salt Lake City has issued a for the Virgin River at Virgin, in effect from 3:41 p.m. MDT on August 31, 2026, until midnight MDT. The warns that flooding caused by excessive rainfall is expected, and at 18.9 feet (8877 cfs), flooding will affect low-lying developed areas near the town of Virgin. Residents are urged to turn around if they encounter a flooded roadway and to use caution when walking near riverbanks. Additional information is available at www.weather.gov. The next statement will be issued this evening at 8:00 PM MDT.

Earlier reports

  1. Aug 31, 2026, 5:48 p.m. ETFirst report

    Flood Advisory Issued for Virgin River at Virgin

    The National Weather Service in Salt Lake City has issued a Flood Advisory for the Virgin River at Virgin, effective from 3:41 p.m. MDT on August 31, 2026, until midnight MDT on September 1, 2026. The advisory warns that flooding caused by excessive rainfall is expected.

    According to the advisory, at a river level of 18.9 feet (8,877 cubic feet per second), flooding will affect low-lying developed areas near the town of Virgin. The advisory urges caution: "If you encounter a flooded roadway, turn around and find an alternative route. Caution is urged when walking near riverbanks."

    The next statement is expected this evening at 8:00 p.m. MDT. Additional information is available at www.weather.gov.

Was this report accurate and useful?

Sources

Revision history

  1. Version 131 Aug 2026, 21:53current

    First published.

  2. Version 131 Aug 2026, 21:48current

    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.