🎶
Exercise #034 · Mass Casualty Event · Special Events Dispatch · Radio Saturation · Multi-Agency Coordination
Route 91 Harvest Festival — Las Vegas, Nevada
October 1, 2017 · 22,000 attendees · 60 killed · 867 injured · Mandalay Bay, Las Vegas Strip
Mass Casualty Event Special Events Dispatch Radio Saturation 911 System Capacity Multi-Agency Coordination CAD Degradation 🎗️ Anniversary
Key Facts
Date and time
October 1, 2017 · Shooting began ≈10:05 PM PDT
Venue
Route 91 Harvest Festival — Las Vegas Village, 3901 Las Vegas Blvd S — adjacent to Mandalay Bay
Shooter location
32nd floor, Mandalay Bay Hotel and Casino — Rooms 32-135 and 32-134
Attendees
Approximately 22,000 at the outdoor venue when shooting began
Casualties
60 killed · 867 injured (413 gunshot, 454 other) — deadliest mass shooting in U.S. history at the time
Simultaneous 911 calls
62 simultaneous 911 calls at peak; 600+ calls in first hour
CAD system
CAD system froze during the incident due to call volume and data load
Radio saturation
638 radio transmissions in first 72 minutes; 151 emergency button activations consuming ≈25 minutes of channel time
Channel switch
Mid-incident attempt to move operations to a secondary channel largely failed — personnel did not hear the switch
No dedicated dispatcher
No dispatcher was pre-assigned to the special event; CCFD was not briefed on the venue layout
LVMPD AAR
93 recommendations issued in the official after-action report
⏱ Incident and Response Timeline
10:05 PM
Shooting begins. Stephen Paddock opens fire from the 32nd floor of Mandalay Bay onto the Route 91 Harvest Festival crowd below. Jason Aldean is performing on stage. 22,000 attendees are in the Las Vegas Village outdoor venue. WARNING
10:05–10:06 PM
62 simultaneous 911 calls. The LVMPD dispatch center receives a flood of calls. Callers describe shooting, explosions, fireworks — many do not immediately recognize what they are hearing as gunfire. The system is immediately saturated. CAD data entry begins falling behind real-time events. DISPATCH
10:06 PM
CAD system freezes. The volume of simultaneous calls and data entry causes the CAD system to freeze. Dispatchers lose real-time situational tracking. The system recovers but the degradation affects the initial information picture available to responding units. GAP
10:05–10:15 PM
Radio channel saturation. 638 radio transmissions occur in the first 72 minutes. 151 emergency button activations — each consuming approximately 10 seconds of channel time — account for an estimated 25 minutes of blocked transmissions during the critical response window. DISPATCH
10:12 PM
LVMPD identifies shooter location. Officers at the venue and Mandalay Bay security transmit information triangulating the fire to the 32nd floor. Dispatch relays. The information loop between field units and dispatch is compressed but functioning — though competing with hundreds of other transmissions. DISPATCH
≈10:17 PM
Secondary channel switch attempted. Operations attempts to move to a secondary radio channel to relieve saturation on the primary. The switch largely fails — the majority of personnel in the field do not hear or cannot execute the transition mid-incident. Most units remain on the saturated primary channel. GAP
10:17 PM
Shooter neutralized. LVMPD breaches Room 32-135. Paddock is found dead from a self-inflicted gunshot wound. The shooting lasted approximately 11 minutes. 1,100 rounds fired. DISPATCH
10:05 PM–post
CCFD not briefed on venue layout. Clark County Fire Department units responding to the mass casualty had not been pre-briefed on the Las Vegas Village venue layout, access points, or staging areas. No dedicated fire dispatcher had been assigned to the event. The AAR identifies this as a significant pre-incident planning failure. WARNING
Post-incident
93 recommendations issued. The LVMPD/CCFD joint after-action report issues 93 recommendations covering special event pre-planning, 911 system capacity, radio infrastructure, channel management, dispatcher pre-assignment, and inter-agency coordination protocols. WARNING

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.

"The communications system was not designed or prepared for an event of this magnitude occurring at this venue." — LVMPD/CCFD Route 91 After-Action Report, 2018

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.

Discussion Questions — 4 Groups
📋 Special Event Pre-Planning — What Dispatch Needs Before the First Call
1
The Route 91 Harvest Festival had 22,000 attendees, was a recurring annual event on the Las Vegas Strip, and had no dedicated dispatcher assigned. CCFD had not been briefed on venue layout or access points. The AAR identifies pre-incident planning failures as the root cause of most communications breakdowns. What does an adequate special event dispatch pre-plan look like, and who owns it?

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.
📡 911 System Capacity — When the Infrastructure Wasn't Built for This
2
62 simultaneous 911 calls caused the CAD system to freeze. 600+ calls arrived in the first hour. The communications infrastructure for Las Vegas was built and provisioned for a baseline of routine call volume — not for the simultaneous reporting of a mass casualty event by thousands of witnesses. What are the capacity planning implications for communications centers near large-venue entertainment, sports, or event districts?

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. CAD systems serving high-event-density jurisdictions should have load testing and overflow protocols.
  • 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.
📡 The CAD freeze at Route 91 was not a surprise — it was a predictable consequence of provisioning infrastructure for baseline load in a jurisdiction with extreme event-driven load spikes. The lesson is that "it's never happened before" is not the same as "it can't happen."
📻 Radio Saturation — 151 Emergency Buttons and 25 Lost Minutes
3
151 emergency button activations, each consuming approximately 10 seconds of channel time, blocked the primary radio channel for an estimated 25 minutes during a critical response window. A mid-incident channel switch to relieve saturation largely failed because personnel in the field didn't hear it. What does Route 91 teach about radio channel management in a mass casualty event — and what should be in place before it happens?

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 — Building the System Before It's Needed
4
Route 91 involved LVMPD, CCFD, EMS, hospital systems, the FBI, and venue security — none of whom had a pre-established joint communications plan for an event at this venue. The AAR's 93 recommendations are largely about building the system that should have existed before October 1. What is the communications center's role in multi-agency special event planning, and what does the minimum viable joint plan look like?

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.
📋 The 93 recommendations in the LVMPD/CCFD AAR are largely a construction manual for the pre-incident planning infrastructure that Route 91 was missing. The document is publicly available and is one of the most comprehensive special event communications planning resources in existence — worth reading as a primary source.

Your Notes

Record your dispatcher name, center, and any notes from today's discussion. Your entries are saved locally and print with the exercise.
Saved

Answer all five questions, then tap Submit to see your score and feedback. Five bonus questions unlock after completing the base quiz.

Question 1 of 10
No dispatcher was pre-assigned to the Route 91 Harvest Festival despite it being a recurring 22,000-person event on the Las Vegas Strip. What is the most direct consequence of this failure?
Question 2 of 10
The CAD system froze during the Route 91 response due to simultaneous call volume. What is the most significant operational consequence of a CAD freeze in a mass casualty event?
Question 3 of 10
151 emergency button activations consumed an estimated 25 minutes of primary channel time during Route 91. A mid-incident channel switch to relieve saturation largely failed. What is the correct lesson?
Question 4 of 10
CCFD units arrived at Route 91 without pre-briefing on the venue layout or access points. What should have happened before the event opened?
Question 5 of 10
The Route 91 AAR issued 93 recommendations. Exercise #035 covers the Boston Marathon bombing — a similar event type four years earlier with radically better communications outcomes. What is the single most important variable that distinguishes the two?
+5 bonus questions unlock after submitting
The LVMPD/CCFD Route 91 After-Action Report is a publicly available primary source and the foundation for this exercise. NENA's 1 October communications analysis, Las Vegas Review-Journal timeline documentation, and CBS News 60 Minutes reporting provide supplementary context.
🔗
This exercise pairs directly with Exercise #035 — Boston Marathon Bombing — the same event category, four years earlier, with pre-planned infrastructure that produced radically different communications outcomes. Return to the full exercise hub.