Fire Engineering Training Community

Where firefighters come to talk training

For members of organizations that has or contributes to a technical rescue response on any level,

What is your response to a confirmed, sustained technical rescue incident such as a trench rescue, structural collapse or confined space rescue?

And...

What does your organization consider the minimum number of Level I and Level II technical rescuers needed to safely perform the operations above?

Views: 376

Reply to This

Replies to This Discussion

We have 4-Heavy Rescue Companies that have a Technical Rescue function. They are staffed with a total of 4; 1-LT, 1-Apparatus Technician, and 2-Tech Rescue Technicians in the back. Three of the four stations maintain staffing on the engine with Tech Rescue personnel. Usually, OIC, DRV, and 1 of 2 FFs are TROT.

On an optimal day, you could get 4-LTs and 8-TECHS from the Rescues
3-Captains and 8 or 9 FF/TECHs from the three engines thsat are used to drive support trucks.

A basic algrorythm consists, of 2-TROT Rescues, 2-Support Units, and the Technical Rescue Battalion Chief. You can always ask for more resources anytime.

For Tech Rescue ICS, we require:
1 - Technical Rescue Branch Director (Officer)
1 - Technical Rescue Safety Officer (Officer)
1 - Technical Rescue Staging (Officer)
1 - Technical Rescue Logistics (non-Officer)
Our initial dispatch has two ALS ambulances, one truck company, one engine company and two squad companies plus two chiefs. We may or may not have and Tecnical Rescue Technicians as part of the 16 members responding. On confimation of entrapment requiring technical rescue techs our regional team is dispatched. The tech rescue squad with approxiamtely 20 techs (all one duty personnel from the region) then respond and will be on scene in 20-30 minutes. As the initial techs arrive, equipment from the first two squads can be used. Generally, the tech rescue squad is only needed for trench and structural incidents. We will our rescue branch with:
1 TRT Branch Director
1 TRT Assistant Safety Officer
As many 6-member "squads" as we can assemble
1-2 logistics members

Accountability and staging outside the hot zone is handled by the IC.
Rex,

From what I have seen Fairfax is the model for technical rescue. We are in the process of merging two technical rescue teams as part of a larger merger of two fire departments. This merger has given us the ability to have 8-12 technical rescuers responding immediately with two rescues and two collapse apparatus if needed. Our biggest challenge right now is helping the officers of both departments understand the need of technical rescue response and, more importantly the safety ramifications of NOT calling for technical rescue resources when appropriate.

Thanks for the input!

BE SAFE!

Scott
Drew,

As you can see from my reply to Rex below, we are merging two technical rescue teams right now. I would be grateful for any policies and procedures you have regarding regional responses. As it stands now we respond as follows:

1st alarm response of confirmed technical rescue incident: 2 Rescues (cross staffed), 1 Ladder, 3 engines, 2 medics (Fire based ALS ambulances), 1 Shift Training Officer, 1 EMS Supervisor, 1 Battalion Chief. if the incident is a collapse (structural or trench) we add 2 collapse trailers.

Currently the Level I and Level II technical rescuers are scattered across both districts. Once the staffing part of the merger kicks in (January 09) we plan to have 9 technical rescuers at the primary station with a ladder, rescue (initially cross staffed) and medic unit. The secondary station will have the second rescue (cross staffed) and a collapse trailer.

Any guidance you can provide would be most appreciated, we have a long way to go.

Thanks, BE SAFE!
Scott

Technical rescue is important and is done by trench rescue technicians for saving life of employees. Apart from this, trench rescue consulting is also very mandatory so that quick rescue can be made in emergency situations.

Reply to Discussion

RSS

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