SEATTLE (King), WASHINGTON

Photo not from this fire. Photo Credit: John Odegard

INCIDENT SUMMARY

Location

Firefighters have arrived on the scene of a working fire located in the 8500 block of 14th Avenue South.

First Due Reports

The 1st due arriving unit reported heavy black smoke coming from the 2nd floor of a two-story building. AT 2110 hours, firefighters had zero visibility on floor one. Water was put on the fire.

Assigned Resources

A14, A5, AIR10, B5, B7, DEP1, E11, E13, E26, E27, E36, L1, L12, L13, M26, M44, MAR5, R1, REHAB1, SAFT2 and STAF10.

OPERATIONS

Command

— An additional resource request for two engines (E6, E30) and a truck (L10) from Command. (2018)

— A decon line was set up on the Alpha side, off of E26.

— Continued operations. 20 minutes on the timer (2120)

— Fire under control. (2124)

— E6, E30, L10 were code greened at 2129.

— L13 was placed back in service (2135)

— M44 and M26 in service. (2142)

— City Light was discussed about needing to come out and check the overhead power lines. (2137)

— A tap fire was called out by firefighters. (2143)

Division Charlie

— E11 assigned with E36 as Fire Attack. All units were moving to the Charlie side, as the seat of the fire was located, and repositioning all units over to this area. Those on the Alpha side were told not to advance their hose lines from Command.

— Firefighters accessed the second roof inside of the interior on the Alpha side to the Charlie side to see what they had.

— All floors were checked during a secondary search, nothing was found and the building was said to be de-energized.

Bravo 1 Exposure

— The Bravo 1 Exposure was checked by members and found to be all clear, with nothing found.

Alpha/Bravo Floor 2

— Members were then sent to this area to give Command a CAN report.

Fire Building – Floor 1

— At the time of 2118 (about 18 minutes on the scene), floor one ceiling temps were at 100*F, and conditions were relayed to Command.

Check back for a new update on this Seattle Fire Incident as the information is received about additional incident details and the cause.

(c) 2023 NW Fire Blog