Fire District 1 fire calls, Nov. 3-9

Fire-District-1-logoSnohomish County Fire District 1 responded to 381 calls Nov. 3-9: 302 emergency medical aid calls, 40 motor vehicle collisions, 15 fires, 2 service calls, 5 natural gas leaks and 17 automatic fire alarms.

Nov. 3
COLLISION: At 9:10 a.m., firefighters responded to a two-car collision in the 12700 block of Mukilteo Speedway north of Lynnwood and transported one patient to an area hospital.

CAR FIRE: At 6:59 p.m., firefighters responded to a car fire at North Road and 176th Place SW east of Lynnwood. No one was injured.

Nov. 4
COLLISION: At 9:08 p.m., a pedestrian hit-and-run collision was reported at 164th Street SW and Ash Way north of Lynnwood. Firefighters transported the injured pedestrian to an area hospital.

COLLISION: At 11:41 p.m., a car struck a pedestrian on Highway 99 near Airport Road south of Everett. Firefighters transported the injured pedestrian to Harborview Medical Center.

Nov. 6
COLLISION: At 9:34 p.m., a car struck a pedestrian at 128th Street SW and E Gibson Road south of Everett. Firefighters transported the injured pedestrian to an area hospital.

Nov. 8
COLLISION: At 7:51 a.m., firefighters responded to a three-car collision on the off-ramp from southbound I-405 to southbound I­­­-5 north of Lynnwood and transported one patient to an area hospital.

CAR FIRE: At 10:17 a.m., firefighters responded to a vehicle fire in the 23200 block of Edmonds Way in Edmonds. No one was injured.

Nov. 9
COLLISION: At 7:33 a.m., a two-car collision was reported at Cathcart Way and 69th Drive SE east of Mill Creek. Firefighters transported one patient to an area hospital.

COLLISION: At 2:03 p.m., firefighters responded to a two-car collision at Filbert Road and North Road east of Lynnwood and transported one patient to an area hospital.

Leave a Reply

Your email address will not be published. Required fields are marked *

Real first and last names — as well as city of residence — are required for all commenters.
This is so we can verify your identity before approving your comment.

By commenting here you agree to abide by our Code of Conduct. Please read our code at the bottom of this page before commenting.