22,000 attendees. 62 simultaneous 911 calls. CAD froze. The radio channel choked on its own emergency buttons. The largest mass casualty event in American dispatch history by call volume — at an event nobody had treated as one.
The Route 91 Harvest Festival shooting is the largest mass casualty event in American dispatch history by call volume. In the first seconds after 10:05 PM on October 1, 2017, 62 simultaneous 911 calls hit the Las Vegas Metropolitan Police Department communications center. Within minutes, the CAD system froze. The primary radio channel became so saturated that 151 emergency button activations — each one blocking all other traffic for approximately ten seconds — consumed an estimated 25 minutes of channel time during the most critical window of the response.
The dispatch lessons from Route 91 are not primarily about what went wrong in the moment. They are about what was not built before the moment.
The Route 91 Harvest Festival was a major annual ticketed event with 22,000 attendees on the Las Vegas Strip. It had occurred before. It was on the calendar. The failure was not that dispatch couldn't handle an unexpected catastrophe — it was that the catastrophe arrived at an event that had not been treated as a high-risk venue requiring dedicated communications infrastructure.
What the comm center saw, and when. Color coding indicates the operational dimension.
No dispatcher had been pre-assigned to the event. Clark County Fire Department units responding to the mass casualty had not been briefed on the venue layout, the access points, or the staging areas. When operations attempted to shift to a secondary radio channel mid-incident to relieve saturation on the primary, most field personnel didn't hear the switch and stayed on the overloaded channel. The CAD system — designed for a baseline of normal Las Vegas call volume — had no additional capacity provisioned for a multi-thousand-person outdoor venue on the Strip.
This exercise pairs directly with Exercise #035 — the Boston Marathon bombing, four years earlier. Boston was a pre-planned event that had been engineered for mass casualty response. Route 91 was a pre-planned event that had not. The contrast is instructive: same category of incident, radically different communications outcomes, traceable almost entirely to decisions made before the first call came in.
Pre-incident planning is the single largest variable. The Route 91 failures were not failures of individual dispatchers in the moment. They were failures of the planning process in the weeks and months before October 1. Boston Marathon (Exercise #035), four years earlier — same event category, radically different communications outcome — had every component Route 91 was missing.
Dedicated dispatcher assignment is non-negotiable for large events. A dispatcher assigned specifically to the event knows the venue layout, access points, staging areas, agency contacts, and channel plan before anything happens. At Route 91, no one had that knowledge embedded when the shooting started. That gap cost time that couldn't be recovered.
Channel switches under fire don't work — channel plans made at a calm table do. The failed mid-incident channel switch is the direct result of having no pre-established channel plan. With 638 competing transmissions in 72 minutes, a switch isn't executable. The channel architecture has to be pre-assigned, pre-briefed, and pre-rehearsed.
Emergency button activations in mass-casualty events require specific training. The 151 activations weren't misuse — they were officers transmitting exactly as trained. But in a mass casualty event with hundreds of officers on scene, widespread emergency activations block the channel for everyone. Pre-incident training should address when the emergency button is appropriate vs. when it amplifies the problem.
"It's never happened before" is not the same as "it can't happen." A venue with 22,000 attendees, if 1% call 911, generates 220 simultaneous calls. The CAD freeze was a predictable consequence of provisioning infrastructure for baseline load in a jurisdiction with extreme event-driven load spikes. Capacity planning is a known variable.
Call overflow routing should be pre-planned, not improvised. Most callers in a mass casualty event are providing duplicate information. A pre-planned overflow protocol — secondary PSAP routing or recorded acknowledgment for callers beyond a threshold — reduces dispatcher cognitive load without abandoning callers.
The communications center must be a participant in pre-event planning, not a recipient of the plan. Dispatch knows what its channel capacity is, what the CAD can handle, what mutual aid looks like, what information field units will need. That knowledge must be at the planning table — not added after the fact.
The minimum viable joint plan has six components. Agency assignments by function. Channel architecture with named channels for each function. Designated dispatcher per agency. Venue layout shared with all agencies. Patient distribution protocol with hospital contacts. A single tabletop exercise before the event opens. Route 91 had none. Boston had all of them.
No right answers. Tap a question to expand the analysis. Use one or all — whatever fits your time.
Special event dispatch pre-planning is not optional for large-venue events — it is the difference between a communications system that can absorb an emergency and one that collapses under it. The Route 91 failures were not failures of individual dispatchers in the moment; they were failures of the planning process in the weeks and months before October 1.
Dedicated dispatcher assignment is non-negotiable for large events. A dispatcher assigned specifically to the event knows the venue layout, the access points, the staging areas, the agency contacts, and the channel plan before anything happens. At Route 91, no one had that knowledge embedded in the communications center when the shooting started. That gap cost time that couldn't be recovered.
Pre-briefing all responding agencies on venue layout. CCFD units arriving to one of the largest mass casualty events in U.S. history did not know where the access points were or where to stage. That information should have been in every agency's pre-plan for the event — shared in advance, not discovered at arrival.
Channel architecture planned before the event, not improvised during it. The failed mid-incident channel switch is the direct result of not having a pre-established channel plan with clear assignments for LVMPD, CCFD, EMS, and security — assigned before the event opens. Channel switches under fire, at night, with 638 competing transmissions, don't work. Channel plans made at a table with calm voices do.
Venue walk-through with communications staff. The dispatcher assigned to a major event should have physically walked the venue — or reviewed a detailed layout — before opening night. Knowing that the Las Vegas Village has specific access gates on specific streets, that the stage is at the south end, that medical staging should be at a particular gate — this is pre-incident knowledge that accelerates every decision once an emergency begins.
Ownership: event organizer + hosting jurisdiction + communications center jointly. The pre-plan is not something dispatch receives passively. The communications supervisor should be at the table with the event organizer and the responding agency commanders, contributing to and approving the plan. Route 91 had no evidence this conversation happened.
Las Vegas is not a typical city. The Strip hosts tens of thousands of visitors every night, with major events drawing crowds that dwarf most cities' entire populations. The CAD system and 911 infrastructure serving Las Vegas were not sized for a scenario where 22,000 people in one place simultaneously called 911. That is a planning failure, not a technology failure — the technology did exactly what it was provisioned to do.
Call volume capacity is a known planning variable. A venue with 22,000 attendees, if 10% call 911 simultaneously, generates 2,200 calls. If 1% call, that's 220. The communications center should know what its simultaneous call handling capacity is, and it should be compared against the realistic call volume any major event in its jurisdiction could generate. If there is a gap, that gap is a known risk.
CAD system freeze is a catastrophic failure mode. When CAD freezes, dispatchers lose the shared situational picture — unit locations, assignments, event log. The response devolves to voice coordination with no persistent record. For Route 91, this meant the information picture available to responding units was degraded at exactly the moment it needed to be most accurate.
Call overflow routing should be pre-planned. When a mass casualty event generates 62 simultaneous calls, most of those callers are providing duplicate information. A pre-planned overflow protocol — routing additional calls to a secondary PSAP, or using a recorded message acknowledging the emergency for callers beyond a threshold — reduces dispatcher cognitive load without abandoning callers.
The CAD system is critical infrastructure — treat it accordingly. Route 91's CAD freeze exposed a single point of failure in the communications system. Redundancy planning, load balancing, and disaster recovery protocols for CAD are infrastructure investments that pay off in exactly these moments.
Radio channel saturation in a mass casualty event is a predictable consequence of a large number of units, high urgency, and no pre-established traffic management protocol. The emergency button activations at Route 91 were not misuse — they were officers transmitting exactly as they had been trained. The problem was that the channel had no capacity to absorb that traffic volume, and no protocol existed to manage it.
Emergency button discipline in mass casualty events requires specific training. An emergency button activation is designed for an officer in immediate peril who needs to transmit without keying up. In a mass casualty event with hundreds of officers on scene, widespread emergency activations block the channel for everyone. Pre-incident training should address when the emergency button is appropriate in a multi-unit mass casualty response versus when it amplifies the problem.
Channel switches must be pre-planned and rehearsed, not improvised. The failed channel switch at Route 91 happened because there was no pre-established secondary channel assignment for this event, no rehearsal of the switch protocol, and no way to ensure all units received and executed the transition simultaneously. A channel switch mid-incident in a noise environment with 638 competing transmissions is nearly impossible without prior rehearsal. The switch itself should be a line item in the pre-plan.
Tactical channel architecture for mass casualty events. The standard approach is a command channel for command-level traffic, separate tactical channels for each functional branch (law enforcement, fire, EMS), and a common channel for inter-agency coordination. None of that architecture existed for Route 91 because no one had built it before the event. It cannot be built during the event.
Dispatcher role in channel management. The dispatcher is the only participant with a view of the whole channel — who is transmitting, what the queue is, where the saturation is occurring. Dispatch should have authority and protocol to manage channel traffic in a mass casualty event: directing units to tactical channels, issuing channel change orders, managing the emergency button queue. That authority requires pre-planning and training.
Multi-agency coordination at a mass casualty event is not improvised — it is the execution of plans that were made in advance. Where those plans don't exist, the coordination that should be seamless becomes ad hoc, slow, and inconsistent. Route 91 demonstrated what happens when a large-scale event occurs in the absence of a joint plan.
The communications center must be a participant in the pre-event planning table. Not a recipient of the plan — a participant in building it. The communications center knows what its channel capacity is, what the CAD system can handle, what the mutual aid protocols are, and what information field units will need from dispatch. That knowledge must be represented in the planning conversation, not added after the fact.
Every agency needs to know its channel and its dispatcher before the event opens. LVMPD, CCFD, EMS, and venue security should each have a designated channel, a designated dispatcher contact, and a pre-briefed understanding of who is doing what. The moment an emergency starts is not the time to establish that architecture.
Hospital notification and patient distribution should be pre-planned. In a mass casualty event, the question of which hospital receives which patients, in what order, with what notification lead time, is a decision that takes time and coordination under pressure. A pre-planned patient distribution protocol — agreed to by all receiving hospitals and the EMS coordinator before the event — converts a chaotic real-time decision into an execution of a known plan.
The minimum viable joint plan has six components. (1) Agency assignments by function. (2) Channel architecture with named channels for each function. (3) Designated dispatcher per agency. (4) Venue layout shared with all agencies. (5) Patient distribution protocol with hospital contacts. (6) A single tabletop exercise before the event opens. Route 91 had none of these. The Boston Marathon, four years earlier, had all of them.
Five questions. Answer, then submit for inline feedback. Progress saves locally.