Coastal Flood Statement Issued for Dorchester, Wicomico, Somerset Counties
The National Weather Service has issued a Coastal Flood Statement for parts of Maryland's Eastern Shore, effective from 7 p.m. Monday to 5 a.m. Tuesday.
3 reports on this incident · first at Sep 7, 2026, 2:15 a.m. ET
Earlier reports
Sep 7, 2026, 2:20 a.m. ET
Coastal Flood Statement Warns of Shallow Flooding in Dorchester, Wicomico, Somerset
The National Weather Service in Wakefield, Virginia, has issued a Coastal Flood Statement for Dorchester, Wicomico, and Somerset Counties, warning that shallow flooding is possible in the most vulnerable locations near the waterfront and shoreline. The statement, issued at 2:08 a.m. on September 7, 2026, is in effect from 7:00 p.m. that evening until 5:00 a.m. on September 8.
Up to one half foot of inundation above ground level is expected in low-lying areas near shorelines and tidal waterways, according to the Weather Service. The agency advises residents not to drive through flooded roadways.
Sep 7, 2026, 2:15 a.m. ETFirst report
Coastal Flood Statement Issued for Dorchester, Wicomico, Somerset Counties
The National Weather Service in Wakefield, Virginia, has issued a Coastal Flood Statement for Dorchester, Wicomico, and Somerset Counties, effective from 7:00 p.m. EDT on September 7, 2026, through 5:00 a.m. EDT on September 8, 2026. The statement was issued at 2:08 a.m. EDT on September 7.
The advisory warns of up to one half foot of inundation above ground level in low-lying areas near shorelines and tidal waterways. Shallow flooding is possible in the most vulnerable locations near the waterfront and shoreline. The public is advised not to drive through flooded roadways.
Was this report accurate and useful?
Sources
Revision history
- Version 17 Sept 2026, 06:20current
First published.
- Version 17 Sept 2026, 06:15current
First published.
- Version 17 Sept 2026, 06:23current
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.