
Below are the latest Whatcom News stories that affect people who live and/or work in and around Bellingham Washington.

Recreational shellfish harvesting closure in all Whatcom beaches due to biotoxin
High levels of biotoxins have been detected in shellfish such as clams, mussels, oysters and scallops.
Share this with friends/family via:

Sedro Woolley woman finds herself in jail after reportedly waving her gun at neighbors, again
Between the March incident and the delayed report to 911 in May, the woman had been arrested in April for waving her weapon at another neighbor.
Share this with friends/family via:

UPDATED: Fatal motorcycle crash closes Lakeway Drive at I-5 overpass
Motorists are advised to expect a long closure.
Share this with friends/family via:

Bellingham fires in Sunnyland neighborhood appear to be arson
The 2 shed fires were 2 blocks apart.
Share this with friends/family via:

Updated: Victim transported to hospital after early morning fire in Bellingham
Initial reports from the scene were that someone was trapped inside.
Share this with friends/family via:

UPDATED: Rollover injury crash snarls northbound I-5 lanes during morning commute
Initial reports from the scene told of 1 vehicle off the roadway in the median and another off the roadway in the grass on the east side.
Share this with friends/family via:

Whatcom County Library System reports email and phone systems “have been compromised”
“Patron data in the online catalog is secure.”
Share this with friends/family via:

WSDOT seeks public opinion on rest area safety
The Safety Rest Area Strategic Plan was last updated in 2008.
Share this with friends/family via:

Over 7,000 lose power around Bellingham
7,247 addresses were without power when the outage began around 6:50pm.
Share this with friends/family via:

1 taken to the hospital after chlorine “burp” escapes Sudden Valley Water Treatment Plant
First responders were dispatched to a report of chlorine odor in the area.
Share this with friends/family via:
Loading…
Something went wrong. Please refresh the page and/or try again.