There are outstanding incident commanders throughout this country who effectively manage the calls they encounter on a regular basis, but how do they measure up with the low-frequency, high-risk calls?

One such scenario typically seen in Arizona's Valley of the Sun during the July and August monsoon season is the flash flood, where water fills the washes and floods frequently traveled roads. Add to this mix citizens in a hurry, and you have a recipe for swiftwater rescue.

Water can be running across the road 2 to 3 feet high, signs can be posted, roads can be barricaded, but the determined public of the Phoenix metropolitan area finds it necessary to try and make it through. Sooner or later one of these individuals stalls a vehicle in the middle of the flowing water or gets washed off the road.

This high-risk situation requires a strong commander who can effectively size-up the situation and initiate a plan of action with adequate backup options, as well as craft an emergency plan for when the proverbial you-know-what hits the fan.

Automatic aid

While flash floods aren't a new phenomenon, they have — along with other low-frequency dangers — become a larger source of trouble. More than a decade ago, the rescue incidents in Peoria, Ariz., began to grow along with its population.

For example, new construction brought an increase in trench rescue incidents, and the potential for confined-space rescues grew as families moved to the north end of Peoria, which has abandoned mine shafts. The area also saw an increase in individuals getting washed off roads from flowing washes that were swollen from monsoon rains.

It goes without saying that the management of the Peoria Fire Department saw a need to have specially trained individuals ready to respond to low-frequency, high-risk calls such as trench rescue, confined-space rescue, swiftwater rescue, building collapse, helicopter operations and rope rescue.

Ladder 193, in the center of Peoria, was chosen as the technical rescue vehicle, and the shift captains attended the 160-hour training course at the Phoenix Regional Fire Training Academy to become technical rescue technicians. (The program is now 200 hours.) Three engineers and six firefighters were chosen by seniority to attend the next class, and Ladder 193 was logged into the system as a technical rescue unit.

The dispatch center dispatches calls for over 1,500 pieces of equipment for 22 different fire departments in the valley. It's not unusual to have vehicles from three or four cities responding to an emergency. This is especially true for technical rescue calls where only nine engines, six ladder trucks and eight support trucks from six different cities have technical rescue capabilities in the system.

Over the last seven years these teams have been dispatched to 657 water-related incidents alone. The minimum personnel dispatched for a water rescue is three technical rescue companies plus two support trucks.

Because teams from different cities always end up working together on these calls, they train together, too. Every Tuesday, 15 different companies from agencies across the valley attend two separate training sessions in the morning and two in the afternoon. The three-hour sessions cover a variety of skills dealing with the disciplines mentioned earlier.

Swiftwater dynamics

Swiftwater is powerful and relentless, but predictable as well. It's the predictability of the moving water that gives rescuers the upper hand when attempting to save a victim.

To understand that predictability, one must be familiar with the terminology used in swiftwater rescue. (See sidebar, opposite.) Of course, a glossary is no match for a raging river that wasn't there a half-hour ago. The speed, or velocity, of water is measured in feet per second. The velocity of swift water can be determined by measuring the time it takes for an object to float a specified distance down the river, and then dividing that time into the distance. For example, if it takes this object 20 seconds to travel 100 feet, the velocity would be 5 ft/sec, which is equal to 3.4mph.

Velocity is important for the technical rescue team to determine the volume of water flowing. To do that, they multiply the width by the depth by the velocity in ft/sec. For example, if a wash is 100 feet wide and 4 feet deep flowing at 5 ft/sec, then 100 × 4 × 5 = 2,000 cubic feet of water per second. One cfs is equal to about 450gpm.

As with any incident, size-up plays a key role. Part of that size-up should include defining the hazards that are likely to injure or kill the rescuers and/or the victim. In the swiftwater arena some of the hazards would be low head dams, strainers, the amount of water flowing and stationary objects. Hypothermia also plays a role, as water conducts heat away from the body 25 times faster than air at the same temperature. In addition, everyone on scene needs to be on the lookout for top loads and suspended loads that could create problems for the victim and rescuers.

If command decides to send rescuers into the water after the victim, a plan needs to be in place in case the victim is swept downstream. There even may be problems unrelated to water. For example, the victim may be so panicked that rescuers can't easily do their job — they need to be prepared for the worst. Rescuers can't anticipate that a victim will assist in his or her own rescue.

Rescue plans

In the end, it's every member's responsibility to size-up the scene and identify factors that could affect rescue.

Any member who is, or potentially will be, within 10 feet of the water should have on PPE that is conducive to survival if that member purposely or accidentally enters the water.

This equipment should include a water rescue helmet that is low profile and without a rim or bill, as well as a U.S. Coast Guard — approved personal flotation device, preferably with a rescue knife and whistle. With water temperatures lower than 70°F, a wet or dry suit should be considered. Footwear with ankle support and solid soles, as well a throw bag with 50 feet of spectra rope, should be available to the rescuers.

Non-technical rescue personnel should be deployed upstream as lookouts and downstream with throw bags in case a rescuer or the victim is swept away. They should never be in the water. Safety officers who are knowledgeable about swiftwater rescue should be in place on both banks to identify unsafe situations or practices.

The first unit on scene needs to size-up the situation, give an on-scene report and assume command. A command checklist is an excellent resource to have, especially for these low-frequency calls. (See sidebar at left.) As quickly as possible, command needs to determine the number and condition of victims. If a rescue is deemed necessary, consider the need for additional personnel and equipment.

A plan of action now needs to be formed. From lowest to highest risk, the options are reach, throw, row, go and helo. Reaching and throwing are considered non-technical rescue actions. Only technical rescue technicians with proper training should attempt row, go and helo.

• Reach

  If possible, a first responder should extend a hand or a pike pole to the victim.

• Throw

  If the victim is too far to reach, a rescuer should attempt to toss a throw bag or rescue ring. Downstream personnel should be in position to haul the victim to the nearest bank.

• Row

  Boat-based operations require a company on the opposite bank to help establish an anchor for a rope system.

• Go

  This high-risk operation places a rescuer in the water. That rescuer needs to know specific objectives, hazards and alternate plans.

• Helo

  A professional helicopter crew may be the most reasonable method of reaching the victim, but rescuers should attempt all other options first while the helicopter is en route, rather than depending on the helicopter.

The objective of the rescue operation is to make contact with the victim, apply protective equipment and remove the victim to a safe area. That sounds easy enough in theory. This is obviously the most hazardous time for the rescuers. Command must continually monitor the situations that could adversely affect the rescue, such as a rise in water, top loads, suspended loads or shifting of the vehicle. Once the victim has been removed to a safe area, medical personnel should be on scene to evaluate and transport to the hospital if necessary.

Today's incident commander is tasked with more and more responsibilities. Some incidents can become overwhelming, especially if personnel aren't sure what to do or where to go with the call. However, firefighters and incident commanders need to know where to find the answers, be they in SOPS, a command checklist or an individual with specialized training.

---

A 14-year veteran of the fire service, Gary Bernard has been with the Peoria (Ariz.) Fire Department for 12 years and now serves as an engine captain/paramedic/technical rescue technician. He also manages the department's mentoring, Red Shirt and wildland fire programs. He has a master's degree in education with an emphasis in counseling and is an adjunct faculty member at Glendale Community College, where he teaches fire operations.

Terms to know

Upstream

Direction from where the water is flowing.

Downstream

Direction where the water is going.

River left

Left bank when facing downstream.

River right

Right bank when facing downstream.

Eddy

Horizontal reversal of water caused by water flowing around an object. An eddy will be on the downstream side and is a safe place for rescuers to exit the water.

Eddy fence

Distinct line where current flows in opposite direction. A rescuer needs to get over the eddy fence to enter the eddy.

Laminar flow

Layered flow of water that is slower on the bottom and faster toward the top.

Helical flow

Circular action of water at the banks caused by friction that forces water midstream.

Hole / Stopper / Keeper

Life-threatening vertical reversal of water caused by water flowing over an object, such as a low head dam. Water is forced down and then circulates back up. Some water continues downstream while some recirculates. Rescuers should exit water immediately.

Downstream V

Convergence of water flowing to the path of least resistance creates a V pointing downstream, as in a bottleneck. The main channel, which isn't always midstream, can be identified by the largest series of Vs.

Upstream V

Water going around an object above or slightly below the water's surface creates a V pointing upstream. The objects below can be hazardous.

Top load

Object that is positively buoyant and floats on surface.

Suspended load

Neutrally buoyant object that moves with the current but is too heavy to float. It can be dangerous and hard to see.

Bottom load

Object on the bottom stuck in the mud or too heavy to be moved by the current. It can cause foot entrapments.

Swiftwater rescue command checklist

Phase I: Size up

Primary assessment

• Secure witness
• Determine locations and conditions of victims
• Identify immediate hazards
• Check if water level is rising
• Consided surface loads, hydraulics and hypothermia

Secondary assessment

• Assess need for additional personnel and equipment
• Choose rescue or recovery

Phase II: Pre-rescue

• Control traffic and crowds
• Make rescue area safe
• Assign safety officer
• Ensure team response to opposite bank
• Dress all personnel within 10 feet of water in PPE
• Assign upstream spotters
• Form primary action and backup plans
• Pre-rescue briefing

Phase III: Rescue

• Implement primary plan
• Make contact with subject
• Apply protective equipment
• Remove subject to safety
• Transfer to ALS

Phase IV: Termination

• Personnel accountability report
• Collect water samples to assess contamination
• Consider decontamination