Fire Engineering Training Community

Where firefighters come to talk training

"BOX ALARM"- Going "3rd Due" in Prince George's County, Maryland

Every department in the United States, or even the world for that matter, operates in its own unique fashion. In Prince George's County, Maryland a box alarm is dispatched for any reported structural fire. This assignment is comprised of four engine companies, two truck companies, a third special service (third closest truck or squad company), two Battalion Chiefs and a BLS transport unit. Through departmental Standard Operating Procedures (SOPs), each respective unit has a specific responsibility. This ensures all areas of the structure are covered.

The third due engine company on the alarm is responsible to secure a secondary water supply/source (yes, every time, without fail, even with NOTHING evident), position to cover the rear ("Charlie" side), advance a handline, report (size-up) conditions found, check the lowest level (ie; the basement) and position the attack line (normally) above the fire area.

Although each unit has very specific map books of the areas responded to, it is a must that Wagon Drivers (Technicians/Chauffeurs/Driver Operators) are familiar with their immediate and surrounding response area(s). This photograph shows Engine Company No. 33 of the Kentland VFD, Inc. in the rear alley of a reported "vacant house on fire" (this past week) that ended-up being an outside rubbish fire with slight extension. The Driver and Officer In-Charge had intimate knowledge of the area to include hydrants, accessibility into the alley with the rig, etc. When dispatched as the third due engine company on this alarm, they put their knowledge to the test. Executing a rear position that enabled the crew to be within reach of a 150-foot pre-connected attack line.

Views: 1153

Comment

You need to be a member of Fire Engineering Training Community to add comments!

Join Fire Engineering Training Community

Policy Page

PLEASE NOTE

The login above DOES NOT provide access to Fire Engineering magazine archives. Please go here for our archives.

CONTRIBUTORS NOTE

Our contributors' posts are not vetted by the Fire Engineering technical board, and reflect the views and opinions of the individual authors. Anyone is welcome to participate.

For vetted content, please go to www.fireengineering.com/issues.

We are excited to have you participate in our discussions and interactive forums. Before you begin posting, please take a moment to read our community policy page.  

Be Alert for Spam
We actively monitor the community for spam, however some does slip through. Please use common sense and caution when clicking links. If you suspect you've been hit by spam, e-mail peter.prochilo@clarionevents.com.

FE Podcasts


Check out the most recent episode and schedule of
UPCOMING PODCASTS

Groups

© 2024   Created by fireeng.   Powered by

Badges  |  Report an Issue  |  Terms of Service