Coordinating on Navigable Waterways: The Corps of Engineers, Dams, and the Coast Guard Auxiliary

Why waterways need a comms plan before the emergency

Most mutual aid works because everyone already shares a common backbone. Neighboring fire departments are on the same regional radio system or at least have each other's frequencies loaded. Law enforcement has statewide interoperability channels. EMS talks to hospitals on a known path. Water changes that picture. The partners who own and operate the water infrastructure in your area are frequently federal, they do not answer to your county, and they were never automatically wired into your radio plan. They are neighbors on the map who may be strangers on the air.

That gap does not matter on a quiet Tuesday. It matters the moment a barge grounds, a swimmer goes missing below a low-head dam, floodwater tops a road, or an operator upstream changes a release that affects everyone downstream. In those minutes you do not want to be discovering that the federal facility a mile from your station monitors a channel your radios cannot reach. A communications plan built ahead of time turns a scramble into a phone call and a talkgroup you already know how to select.

The reason to do this early is simple. Interoperability is not a switch you flip during the incident. It is a set of arrangements, loaded channels, shared contact lists, and agreed procedures that either exist before the tones drop or do not exist when you need them. Waterway partners are one of the most commonly overlooked pieces because they are not on your daily net and it is easy to assume someone else has it handled.

What the Corps of Engineers actually runs

The US Army Corps of Engineers operates and maintains a large portfolio of dams, locks, and navigable waterways across the country. On many rivers and reservoirs, the Corps is the entity that controls water levels, manages the locks that let vessels pass, maintains navigation channels, and runs the recreation areas that surround the water. If there is a federal dam or lock in your response area, there is a good chance the Corps is the operator or has a major role in it.

What that means for you operationally is that the Corps often has its own personnel on or near the water, its own facilities with their own access and hazards, and its own communications. Their people may be the first to notice a problem with the structure, a rising pool, or a vessel in distress. They may also be the ones who need to reach you, because a dam or lock emergency almost always spills into the surrounding community that your agency protects.

This is not a one-way relationship. In a serious event you may need information only the operator has, such as current gate settings, planned releases, or the status of a lock. They may need your resources, such as fire suppression, EMS, water rescue, evacuation support, or traffic control. Neither side gets what it needs if the only connection is a general phone line discovered after the fact.

Why dam and water-control incidents are high-consequence

Dam and water-control incidents belong in the same category as hazmat and large structural events. They are low-frequency and high-consequence. Most directors will go years without a serious one, which is exactly why the planning slips. But when they happen, the population at risk and the geographic footprint dwarf a routine call.

Consider what a water-control event can involve. A change in releases upstream can raise a river downstream faster than people expect, and that water moves through areas your agency covers. A structural concern at a dam can put a large downstream population in a potential inundation zone, which drives evacuation, shelter, and mass-notification decisions that sit squarely in emergency management. Low-head dams and spillways create dangerous hydraulics that trap and kill swimmers and boaters, and those rescues are technical, time-critical, and often need water rescue teams working alongside the operator who controls the flow.

The common thread is that in each case the person who controls the water is not the person running the emergency response, and the two absolutely have to talk. A gate change decided by the operator changes the tactical picture for your crews on the bank. A downstream evacuation decision by your EMA depends on information only the operator has. If that conversation happens over a slow chain of phone calls routed through duty officers, you lose the minutes that matter most.

The Coast Guard Auxiliary as a partner

The Coast Guard Auxiliary is the volunteer component of the United States Coast Guard. Its members are civilian volunteers who support Coast Guard missions, and on many inland and coastal waters the Auxiliary is a real, present, and willing partner. They conduct safety patrols, support search operations, provide vessels and trained crews, and often know local water conditions intimately because they are on it regularly.

For a local director, the Auxiliary can be a genuine force multiplier on the water, especially in areas where your own agency has limited marine capability. They may be able to put a boat and a trained crew on a search, provide on-water eyes during a flood, or help cover a large body of water that your ground units cannot reach. Because they are volunteers, availability varies, but the capability is real and worth mapping.

The catch is the same as with the Corps. A resource you cannot communicate with is a resource you cannot coordinate. If the Auxiliary operates where you have responsibility, you want to know in advance how they organize locally, who your point of contact is, and how you would talk to them during a joint operation. That last part, the actual radio path, is where waterway coordination gets genuinely messy, and it deserves its own section.

The radio reality: talkgroup, VHF, or both

Here is the single most important operational fact in this guide. The way you communicate with waterway partners varies a great deal from one area to another, and you cannot assume the arrangement one county uses is the arrangement your county uses.

The modern trend is that these partners increasingly ride a talkgroup on the local jurisdiction's radio system. Where that has been set up, coordination is clean. The Corps facility or the Auxiliary crew selects an agreed talkgroup on your trunked system, everyone is on the same infrastructure, and it works the way any other interoperability talkgroup works. This is the direction many areas are heading, and it is the arrangement to aim for where it does not yet exist.

Historically, though, these partners operated on their own frequency, typically in the VHF band and analog. That path was often simplex, meaning radio to radio with no repeater, and sometimes used a repeater depending on the size of the water body. A small reservoir might be covered fine by simplex. A long river or a large lake might need a repeater to bridge the distance. The point is that the older model was a separate VHF path that your trunked portables might not even have loaded, and in a lot of places that older model is still how it works today.

So the reality on the ground is a patchwork. Some areas have a clean talkgroup. Some still rely on a legacy VHF analog frequency, simplex or repeated. Many are somewhere in between or in transition. None of this is a criticism of anyone. It reflects the fact that these are federal and volunteer partners layered onto local systems that all evolved differently. Your job is not to guess which model you have. Your job is to find out.

Find out in advance, then build the capability

Finding out is step one. Building the capability is step two, and it usually follows directly from what you learn. If the partner is already on a talkgroup on your system, your work is mostly confirming it is programmed in the right radios, documented, and included in your training. If the partner is on a separate VHF path, you have a decision to make about how to bridge to it.

Bridging options generally come down to a few approaches. You can program the partner's VHF frequency into radios that are capable of it, so designated units can talk directly on that path. You can stage caches of compatible radios for the crews likely to work a waterway incident. You can use a gateway or patch, where dispatch or a comms unit ties the VHF path to a talkgroup on your system so both sides can hear each other. Or you can work with the partner to establish a shared interoperability channel or talkgroup that becomes the standing arrangement going forward. Which one fits depends on your equipment, your partner's equipment, and the size and shape of the water.

Whatever the path, the two things that make it real are documentation and testing. A frequency written on a card that nobody has ever keyed up in the field is a hope, not a plan. Put the arrangement into your written communications plan, program it where it needs to be, and exercise it. A simple annual radio check with the Corps facility or a coordinated drill with the Auxiliary tells you far more than any assumption. It also builds the relationship, so that when a real event happens the voices on the radio already know each other.

Do not let perfect be the enemy of workable. If the ideal is a shared talkgroup and you are not there yet, a documented and tested VHF path is a solid interim answer. The failure mode to avoid is having nothing at all and finding that out during the incident.

Whose job this is: the EMA and radio-admin hybrid

Waterway coordination sits in an awkward organizational spot, which is part of why it gets dropped. It is partly an emergency management responsibility, because dam failures, floods, and inundation zones drive evacuation, sheltering, and public warning, which are core EMA functions. It is also partly a radio administration responsibility, because the whole thing hinges on frequencies, talkgroups, programming, and interoperability agreements. This is a hybrid problem, and it needs an owner who spans both worlds.

In a great many jurisdictions that owner already exists, because the roles are dual-hatted. Dual-hatted simply means one senior official wears two hats at once. It is common for the same person to serve as both the 911 or communications director and the emergency management agency director, with the emergency management function sitting inside the 911 communications command structure. Where that is the case, waterway coordination has a natural home, because the person responsible for the radio system is also the person responsible for the emergency plan.

If your structure separates those roles, the fix is to name the owner explicitly and make sure the EMA side and the radio side are talking. The worst outcome is the silent assumption, where emergency management assumes the radio shop has the Corps loaded and the radio shop assumes emergency management coordinated it, and neither actually did. Assign it, write it down, and review it, the same way you would any other interoperability responsibility.

A starter checklist for mapping waterway partners

Use this as a starting point, not a finish line. Adapt it to the water bodies and partners in your area.

• Inventory the water. List every dam, lock, reservoir, spillway, low-head dam, and stretch of navigable water inside your response area, and mark which are inside your borders and which sit on shared boundaries.
• Identify each operator. For every structure, name who actually controls it. Is it the Corps of Engineers, another federal agency, a state authority, a utility, or a private owner? Do not assume.
• Map the volunteer resource. Determine whether the Coast Guard Auxiliary operates on your waters, how they organize locally, and what capability they can bring.
• Get real contacts. Collect names, titles, duty-officer lines, and after-hours numbers for each partner, and confirm who has authority to make water-control and resource decisions.
• Answer the radio question for each partner. Talkgroup on your system, VHF analog frequency, or both? Simplex or repeated? Write down the specific answer for each one.
• Close the gaps. Where there is no workable path, decide how to bridge it: program the frequency, cache compatible radios, set up a gateway or patch, or establish a shared talkgroup.
• Document it in the plan. Put the arrangements, contacts, and procedures into your written communications and emergency plans so they survive staff turnover.
• Test and exercise. Run an annual radio check with each partner and work at least one joint drill. Confirm the path actually works in the field, not just on paper.
• Assign an owner. Name the title responsible for waterway comms coordination, and make sure the EMA and radio-administration sides are connected, especially if the roles are not already dual-hatted.
• Review on a schedule. Revisit the whole map at least yearly, because talkgroups get built, frequencies change, and partners reorganize.