Common Communications Failures in Real Incidents (and What They Teach Us)

When agencies cannot talk to each other

The most common finding in multi-agency reviews is also the most predictable: units from different organizations arrived, went to work, and could not reach each other by radio. A fire company could not talk to the ambulance from the neighboring service. Law enforcement was on a system the fire units could not monitor. Mutual aid rolled in on equipment that did not share a channel with the units already committed.

This is rarely a technology mystery. It is usually a planning gap. Agencies buy radios and build systems for their own daily work, and the shared talk path is treated as something to figure out on the day it is needed. When the day comes, the incident is already moving too fast to sort it out.

The lesson is that interoperability is a decision you make in advance or not at all. You cannot invent a common channel while a building is burning. The fix is to know, before the tones drop, exactly how you will talk to every agency you can reasonably expect to work beside. That means shared or designated mutual aid channels programmed into every radio, a written crosswalk of which agency uses which resource, and a habit of confirming the shared talk path in the first minutes of any joint response.

• Identify every agency you routinely operate with and confirm at least one common talk path exists for each.
• Make sure the shared channels are actually programmed into the field radios, not just listed on paper somewhere.
• Rehearse it. A shared channel that no one has ever keyed up under stress is a shared channel in name only.

Radio congestion at the peak of the incident

A radio channel can only carry one transmission at a time. That fact does not change when the incident gets bigger. What changes is how many people want to talk. The exact moment when clear communication matters most, when crews are committing, conditions are shifting, and command is trying to account for everyone, is the same moment the channel jams with traffic.

Reviews describe it the same way over and over. Urgent messages held for long stretches because the channel was busy. A crew trying to report a change in conditions and being unable to key up. Command missing a request because three routine transmissions were stacked ahead of it. Nobody did anything wrong in isolation. Collectively, the traffic overwhelmed the pipe.

The lesson is that channel capacity is a resource you have to manage like any other. When you outrun the capacity of one channel, you split the traffic. The fix is to move tactical groups onto their own channels early, before the main channel saturates, not after. A single operations channel works for a small incident. A larger incident needs separate channels for divisions, for a rapid intervention assignment, for command, and so on. Assigning them late is almost as bad as not assigning them, because by then the confusion is already baked in.

• Plan channel splits by incident size, and make the trigger points explicit in your guidelines so command is not inventing the structure under pressure.
• Keep at least one channel deliberately clear for emergency traffic. Routine reports do not belong on the same path as a mayday.
• Teach crews to shorten routine transmissions during peak activity and to hold non-urgent traffic when they can hear the channel is busy.

Dead zones inside structures and terrain

Radios that work fine in the parking lot stop working reliably inside large or heavily built structures. Below grade, deep in a big-box footprint, inside a stairwell of a tall building, or behind thick concrete and steel, portable signals fade or drop entirely. The same happens in terrain: a crew working the bottom of a drainage or the back side of a ridge can be invisible to everyone else even though they are a short distance away as the crow flies.

The dangerous part is that the failure is silent and uneven. A crew can hear command but command cannot hear the crew. Or the signal works on the way in and fails once they push deeper. People assume that no answer means no problem, when it may mean a portable is transmitting into a wall.

The lesson is that coverage is location-dependent and cannot be assumed from a single test. The fix combines hardware and habit. Where structures are known to defeat portables, plan for it: pre-identify the problem buildings in your response area, know which ones have systems intended to extend coverage inside, and know that those in-building systems can be out of service without anyone knowing. On the habit side, build in confirmation. If a crew goes somewhere coverage is doubtful, command should expect and require periodic contact, and treat a lost radio the way you would treat any other loss of accountability.

When the infrastructure itself fails

Most day-to-day radio traffic leans on infrastructure: a repeater or a network of sites that receives a weak portable signal and rebroadcasts it with power. That infrastructure works quietly and reliably almost all the time, which is exactly why its failure is so disruptive. Crews are conditioned to expect a certain range and clarity, and when the supporting site goes down, the range collapses without warning.

The failure modes are familiar. A single site loses power in the same storm that generated the call volume. A site is knocked offline by the very incident you are responding to. Backup power runs out during a long event because nobody planned for an incident that would last that long. A site is saturated by the number of radios trying to use it at once. In each case, portables that reached across the region a moment ago now reach only as far as they can shout.

The lesson is that infrastructure is a convenience, not a guarantee, and the incidents most likely to knock it out are the incidents where you need it most. The fix is a fallback plan that does not depend on the thing that failed, and crews who have practiced switching to it. That leads directly into the simplex discussion later in this guide, but the mindset starts here: never build your entire communications plan on a single point of failure, and never let the first time a crew operates without infrastructure be a real emergency.

• Know how long your infrastructure runs on backup power, and plan long incidents against that number honestly.
• Have a defined, rehearsed answer to the question "what do we do when the system is down," and make sure it is not "wait for it to come back."
• Assume that a disaster large enough to generate a big response is also large enough to damage the infrastructure that response depends on.

Unclear talkgroup and channel assignments

Even when the radios work and the capacity exists, communications fail when nobody is sure which channel to use. A crew is told to go to a tactical channel but the name they were given does not match the label on the radio. Two divisions end up on the same channel by accident. A resource assigned to a group never gets told which group it is, so it monitors the wrong path and misses every instruction meant for it. The infrastructure is fine. The map is missing.

This gets worse as the incident grows and as more agencies arrive, because different organizations use different names for the same resources and the same names for different resources. What one agency calls a common channel, another calls something else entirely. Verbal assignments passed through several people mutate along the way.

The lesson is that a channel assignment is only useful if the receiving crew can act on it without guessing. The fix is a clear, written communications plan for anything beyond the smallest incident, standard channel names that every crew recognizes, and a discipline of confirming assignments rather than assuming they landed. When you assign a crew to a channel, they should read it back, and command should hear the readback before considering that crew reachable there.

• Standardize channel and talkgroup naming so a name means the same thing to everyone who might hear it.
• For anything larger than a routine call, put the communications plan in writing and distribute it before crews go to work.
• Require readback of channel assignments. A crew that has not confirmed its channel is not yet accounted for on that channel.

Discipline breakdown: everyone talking at once

Some communications failures are not about equipment at all. They are about behavior. When stress rises, people talk more, talk longer, and talk over each other. Transmissions collide and cancel out. Command gets buried in reports it did not ask for while the one report it needs is stepped on. A crowded channel and poor discipline feed each other, and the channel becomes noise at exactly the wrong time.

The pattern in reviews is remarkably consistent. Long, narrative transmissions when a short one would do. Crews keying up to acknowledge things that did not need acknowledgment. Multiple people trying to move the same information at the same moment. Emotion in the voice traffic that made an already tense channel harder to work. None of it malicious. All of it avoidable.

The lesson is that radio discipline is a skill, and skills decay without practice. The fix is culture plus repetition. Teach a standard structure for transmissions: who you are calling, who you are, then your message, kept short. Teach crews to listen before they key up. Reinforce that command sets the tempo and that not every thought needs to go over the air. Most importantly, practice it on routine calls, because the discipline you have on the small runs is the discipline you will have on the big one. You do not rise to the occasion; you fall back on your training.

Over-reliance on cell networks

Cell phones have quietly become part of many departments' communications plan, often without anyone deciding that on purpose. Command calls a chief officer's phone to pass sensitive traffic. Crews text logistics. A key coordination conversation happens on a phone call because the radio channel is busy. On an ordinary day, it works, and because it works, it spreads.

Then comes the incident that overwhelms the commercial network. A large event drives every civilian in the area to call and text at once, and the network saturates. A widespread emergency damages the same commercial infrastructure the phones depend on. Suddenly the calls do not connect, the texts sit undelivered, and the coordination that had quietly migrated to phones has nowhere to go. Worse, information moved by phone never reached the people monitoring the radio, so there is no shared record and no common picture.

The lesson is that the commercial cell network is not built for public safety command traffic and will fail you in precisely the conditions that generate large incidents. The fix is not to ban phones; they are useful for one-to-one detail that does not belong on a busy channel. The fix is to keep the radio as the backbone and the phone as a supplement, never the reverse. Critical command and tactical traffic belongs on the radio, where the whole team can hear it and where you control the infrastructure, not on a network you share with every civilian in the impact zone.

• Decide deliberately what belongs on the phone and what belongs on the radio, and keep command and safety traffic on the radio.
• Assume the cell network will be degraded or gone during any large-scale event, and build no essential function on it.
• Remember that phone traffic is invisible to everyone not on the call, which breaks shared situational awareness.

The simplex fallback nobody practiced

Most of the failures above share a single antidote: the ability to talk radio to radio, directly, with no infrastructure in the middle. Simplex, or direct, operation takes the repeater, the network, and the tower out of the equation entirely. Two portables talk to each other over the air. The range is shorter and the coverage is less forgiving, but it works when everything else has failed, and it works when you are close together, which on the fireground you usually are.

The recurring failure is not the absence of a simplex capability. Most radios have it. The failure is that crews never practiced it, do not know which channel to switch to, and do not understand how its range differs from what they are used to. When the infrastructure drops, they keep transmitting into a dead repeater path instead of switching to direct, because switching to direct was never a trained reflex. A capability you own but never use is not a fallback. It is a footnote in the radio manual.

The lesson ties the whole guide together: every communications plan needs a mode that survives the loss of everything else, and that mode has to be practiced until it is automatic. The fix is straightforward and cheap. Make the direct channel a known, standard part of your plan. Train crews to recognize when to switch, whether it is a lost repeater, a deep interior assignment, or a coverage hole. Drill the switch on ordinary days so it is muscle memory on the worst one. And teach the honest limits of simplex range so nobody is surprised when it does not reach as far as the system did.

• Designate standard direct channels and make sure every field radio has them and every crew knows them by name.
• Train the trigger: crews should switch to direct the moment infrastructure fails or coverage becomes doubtful, without waiting for permission.
• Understand and teach the reduced range of direct operation so expectations match reality on scene.

None of these failures are new, and none of them are unsolvable. They recur because the fixes live in planning and training, and planning and training are the first things a busy department lets slide. The pattern is the point. When you can name the failure mode in advance, you can drill against it, write it into your guidelines, and turn a recurring surprise into a handled contingency. That is the whole value of studying how communications break down: not to assign blame after the fact, but to make sure your people already know the answer before the question arrives.