High Surf Advisory Warns of Flooding and Dangerous Conditions for San Diego and Orange County Coasts
The National Weather Service warns of coastal flooding, dangerous surf, and beach erosion from Saturday through Tuesday.
2 reports on this incident · first at Sep 3, 2026, 4:42 p.m. ET
Earlier reports
Sep 3, 2026, 4:42 p.m. ETFirst report
High Surf Advisory Issued for San Diego and Orange County Coastal Areas
The National Weather Service in San Diego has issued a High Surf Advisory for San Diego County and Orange County coastal areas, effective from 6 AM Saturday, September 5, 2026, to 11 PM PDT Tuesday, September 8, 2026. The advisory was issued at 1:32 PM PDT on September 3.
The advisory warns of large breaking waves of 6 to 10 feet for south and southwestern-facing beaches and 4 to 7 feet for west-facing beaches, along with strong and dangerous rip and longshore currents. Minor coastal flooding is possible from a combination of high surf and high astronomical tides, which could lead to flooding of lots, parks, and roads with only isolated road closures expected. Dangerous swimming and surfing conditions and beach erosion are also anticipated.
Residents and visitors are advised to take precautions: if travel is required, allow extra time as some roads may be closed; do not drive around barricades or through water of unknown depth; take necessary actions to protect flood-prone property. Inexperienced swimmers should remain out of the water due to dangerous surf conditions, and everyone should always swim near a lifeguard. Stay off sea walls and jetties, and be aware that waves will occasionally run farther up the beach than expected, especially during high and rising tides; set up farther back from the ocean and do not turn your back on the ocean.
Was this report accurate and useful?
Sources
Revision history
- Version 13 Sept 2026, 20:54current
First published.
- Version 13 Sept 2026, 20:42current
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.