Beach Hazards Statement Issued for Five Michigan Counties Through Sunday Evening
The National Weather Service warns of strong currents and high waves along Lake Michigan beaches from late Saturday night through Sunday evening.
3 reports on this incident · first at Aug 29, 2026, 1:40 p.m. ET
Earlier reports
Aug 29, 2026, 1:46 p.m. ET
Beach Hazards Statement for Mason, Oceana, Muskegon, Ottawa and Allegan Counties Until 11 p.m. Sunday
The National Weather Service in Grand Rapids has issued a Beach Hazards Statement for Mason, Oceana, Muskegon, Ottawa and Allegan counties, warning that strong currents can pull swimmers into deeper water and high waves can sweep people off piers along Lake Michigan beaches.
The statement is in effect from 2 a.m. to 11 p.m. EDT on Sunday, August 30, 2026, and expires at 11 p.m. EDT that evening. The Weather Service advises people to remain out of the water to avoid hazardous swimming conditions, not to venture out on piers, and to check with local authorities about potential beach closures.
The warning covers five counties and was issued at 1:30 p.m. EDT on Saturday, August 29.
Aug 29, 2026, 1:40 p.m. ETFirst report
Beach Hazards Statement Issued for Mason, Oceana, Muskegon Counties
The National Weather Service in Grand Rapids has issued a Beach Hazards Statement for Mason, Oceana, Muskegon, Ottawa, and Allegan counties, effective from 2 a.m. to 11 p.m. EDT on Sunday, August 30, 2026. The statement was issued at 1:30 p.m. EDT on Saturday, August 29.
The warning cites high wave action, strong currents, and dangerous swimming conditions expected along the lakeshore. Strong currents can pull swimmers into deeper water, and high waves can sweep people off piers, which may be swamped by waves.
The NWS advises residents to remain out of the water to avoid hazardous swimming conditions and to avoid venturing out on piers. It also recommends checking with local authorities for potential beach closures.
The Beach Hazards Statement remains in effect until 11 p.m. EDT on Sunday, August 30, 2026.
Was this report accurate and useful?
Sources
Revision history
- Version 129 Aug 2026, 17:53
First published.
- Version 129 Aug 2026, 17:46current
First published.
- Version 129 Aug 2026, 17:40current
First published.
- Version 129 Aug 2026, 17:51current
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.