Five days of ambiguous notifications. Then 188,000 people told to run. The dispatch center was in the inundation zone. They kept answering 911 anyway.
For five days before 188,000 people were told to run, dispatchers at Butte County's communications center were receiving information from a dam operator, a sheriff's command staff, a public watching on social media, and a news cycle — and the signals didn't agree. This exercise is about those five days. The mass evacuation phase gets most of the attention. The dispatch challenge that made it harder was everything that happened before the order was given.
Oroville Dam sits on the Feather River in Butte County, California. At 770 feet, it is the tallest dam in the United States. The reservoir holds up to 3.54 million acre-feet of water. The dam has two spillways: a main concrete flood control spillway and an emergency spillway — an unlined concrete weir designed to allow water to flow over a bare hillside into the Feather River below. The emergency spillway had never been used in the dam's nearly 50-year history.
The Butte County Sheriff's Office and CAL FIRE Butte County share a joint Emergency Command Center handling law enforcement and fire/EMS dispatch for Butte County. Their dispatch center itself sits within the potential inundation zone. Downstream communities in Yuba and Sutter counties have their own PSAPs — any evacuation order for Oroville immediately becomes a multi-county, multi-PSAP event.
What the comm center saw, and when. Color coding indicates the operational dimension.
On February 7, the EAP required DWR (the dam operator) to notify the PSAP using clear, classification-based language. The notification DWR sent used language that did not convey the severity of a 250-foot crater in the main spillway. The Sheriff learned about the damage informally — from a text message from a local media contact, not through the formal EAP notification chain. There was no protocol for the PSAP to escalate an ambiguous dam operator notification to command-level review. The system worked as designed. The design had a gap.
When the evacuation order arrived at 4:21 PM on February 12, the Butte County dispatch center had ~23 minutes before the potential arrival of flood water if the weir collapsed. They were still taking 911 calls. They were in the inundation zone. There was no pre-established protocol for dispatch center relocation. Approximately 400 calls came in during the first 30 minutes of the evacuation — many from callers who were angry because they had been told for five days there was "no danger to public safety."
The lesson the 2017 incident produced was structural: distributing an EAP to a PSAP is not the same as the PSAP being trained and prepared to execute it. The Cal OES Dam Safety Planning Division exists because that gap was real, costly, and national in scope.
Dam operator notifications must use plain-language classification terms. The 2017 Oroville notification used language that didn't convey severity. The Sheriff learned through informal channels. There was no protocol for the PSAP to escalate an ambiguous notification to command-level review. Whatever your jurisdiction's dam EAP says, verify the notification language is classification-based and the PSAP has authority to escalate ambiguous notifications.
The PSAP that doesn't question an ambiguous notification is the PSAP that gets caught. If the dam operator's message doesn't fit the EAP severity classes, the PSAP's job is to escalate it to command — not to log it as routine. Build that escalation authority into the protocol so a dispatcher doesn't have to invent it at 0300.
If your dispatch center is in an inundation zone, that's a COOP problem, not a footnote. Butte County's dispatch center sat in the potential inundation zone with no pre-established relocation protocol. The dam EAP needs a continuity of operations component: alternate facility, transition authority, timing triggers, what stays operational during the move. Find your center's answer before you need it.
Multi-county dam corridors need pre-established information-sharing protocols. Feather River corridor events are three-county events by definition. During 2017, coordination between the three county PSAPs during the escalation phase was inconsistent. Pre-established protocols and joint exercises so all three centers are working from the same playbook before the event are the structural fix.
Caller frustration during a mass evacuation is partly informational, not emotional. Callers told for five days "no danger to public safety" who then receive a mandatory evacuation order have legitimate confusion about who to trust. Acknowledge the frustration briefly, provide the specific safety information they need, and move to the next call. Don't explain the five-day history; you don't have time and they don't need it.
The first call is not always to 911. The Sheriff learned via text from a media contact. Social media saw the spillway damage before the formal EAP chain delivered it. Dispatch can be the last node in the formal chain to receive what the public already knows. That's a real gap; treating informal reports as worth verifying — not dismissing — is the corrective.
Distributing an EAP is not the same as being prepared to execute one. Most PSAPs near high-hazard dams have the EAP somewhere. Far fewer have practiced it, can locate it under pressure, or know whether their facility is in the inundation zone. The 2017 incident exists in part because that gap is national. Closing it for your own jurisdiction is your work, not someone else's.
Sheriff Honea's evacuation decision is a model worth studying. He recapped his understanding, asked the room of engineers and state officials if he was missing anything, and when the silence answered him, he gave the order. That decision-making structure — explicit recap, named question, time-bounded silence — is replicable in any complex multi-stakeholder decision dispatch supports.
No right answers. Tap a question to expand the analysis. Use one or all — whatever fits your time.
This is exactly the gap the 2017 incident revealed. The formal notification chain delivered ambiguous information. Informal reports — from media, social media, public observers — delivered specifics. Dispatch sat between the two streams with no protocol for reconciling them.
Does your center have a protocol for escalating ambiguous dam operator notifications? If the dam operator's language doesn't match an EAP severity class — "spillway operations" vs. "spillway emergency" — what's the next step? In 2017 there was no defined next step.
Who has the authority to treat an informal public report as a trigger for EAP-level action? A 911 caller reporting a "massive hole" near a dam is not a verified incident report. But it's not nothing either. Whose decision is it to escalate based on that, and how fast can that decision be made?
The reconciliation move is to call back the operator. Verify what the formal notification meant. Get an updated classification on the line. Document the inconsistency. The protocol you want is one where the dispatcher has authority to make that call without first finding a supervisor — because at 0300 with a skeleton crew, the supervisor may not be available fast enough.
Dispatch centers that don't question ambiguous notifications are the ones that get caught. The lesson Oroville produced was that verifying a notification — politely, professionally, on the record — is part of the dispatcher's job, not above their pay grade.
Multi-source notification management is the operational reality of an active dam EAP. Each call has different time urgency, different information value, and different consequences if delayed.
Your center's current protocol for multi-source simultaneous notification. Is there a dedicated position for dam event coordination, or does this fall on the primary dispatcher? In 2017, the answer for most jurisdictions was "primary dispatcher" — and the cognitive load was real.
The dam operator update is the highest-information call. Whatever they're calling about — flow rate change, classification update, structural status — is the input that drives every other decision. Take it first if at all possible.
The downstream county PSAP request becomes information-sharing. Once you have the operator update, you can give downstream PSAPs the same picture. That call is a multiplier — answering it once propagates information to multiple jurisdictions.
The field unit and the 911 caller compete for the same cognitive resource. The field unit needs operational guidance; the 911 caller needs reassurance and accurate evacuation information. Both are legitimate. The risk in deprioritizing either is real.
The structural answer is staffing-up before you're underwater. Spinning up additional dispatchers when EAP activation occurs — not after the calls begin overwhelming the primary — is the supervisor function. Waiting until the primary is visibly drowning is the failure mode.
The Butte County dispatch center sat in the potential inundation zone in 2017. There was no pre-established protocol for dispatch center relocation. They worked through it because they had to. That's not a plan; that's improvisation under pressure.
Pull out your center's dam EAP right now. Does it reference your facility's location relative to the inundation zone? Does it include a continuity of operations component? In 2017, most facility EAPs did not.
The COOP component should answer: Where is the alternate facility? Who has authority to order the transition? What triggers the move (a specific water elevation, a classification level, an evacuation order)? What happens to active calls during the transition? Who stays at the primary facility, and for how long?
The 23-minute window is not the time to figure this out. If your center has 23 minutes before water arrives, the time to plan was last year. The dispatchers who get caught are the ones for whom the COOP question is theoretical.
The Cal OES Dam Safety Planning Division exists because this gap was national. Most PSAPs near high-hazard dams in 2017 did not have a COOP component in their dam EAP. Many still don't. Closing that gap for your jurisdiction is the actionable lesson Oroville produced.
Caller anger during a mass evacuation that contradicts prior public messaging is a real phenomenon. The callers aren't wrong to be confused. They were told for five days that there was no danger. Now they're being told to leave their homes immediately. The dispatcher fielding those calls did not write the messaging — and the dispatcher cannot fix it on the call.
Acknowledge the frustration briefly, provide the specific safety information they need, and move to the next call. The acknowledgment matters; the explanation does not. "I understand this is frustrating — the situation has changed and you need to leave now" is enough. "Let me explain the five days of public messaging" is too much.
Don't explain the five-day history. You don't have time. They don't need it. The information that matters is the evacuation route, the timing, and what to bring — not the chronology of how the situation got here.
Call handling protocols during high-volume events. Does your center's training include managing callers whose distress is partly driven by perceived official misinformation? It's a specific skill: validate the emotion, deliver the operational information, end the call respectfully, take the next one.
The structural correction lives upstream from dispatch. The five days of "no danger to public safety" messaging came from officials whose risk assessment did not match the speed of the situation. Dispatch can't fix that. What dispatch can do is be the calm, accurate, respectful voice when the messaging finally catches up to reality.
The point of this question is not to embarrass anyone. The point is that if you had to answer it from memory right now, at 0300, with a skeleton crew, you should be able to. If you can't, that is the training gap this exercise is designed to address.
EAP distribution is not EAP readiness. Most PSAPs near high-hazard dams have the document somewhere. Far fewer have practiced it, can locate it under pressure, or have walked through the notification chain in real time.
The notification chain typically runs: Dam operator → PSAP → County OES / Sheriff command → Downstream PSAPs → State OES warning center → NWS → Law enforcement traffic control → Hospitals → Mass care. Each step has a contact, a phone number, and an expected response window.
The questions worth answering before the next event: Are those phone numbers current? When were they last verified? Is the chain documented in a way the on-shift dispatcher can find without help? What does the chain take in actual elapsed time at your normal staffing level?
The training gap is not the EAP — it's the rehearsal. Tabletop exercises, walked-through notification chains, time-tested scenarios. Centers that have done this work execute the EAP. Centers that haven't are dispatchers reading a binder under pressure.
Five questions. Answer, then submit for inline feedback. Progress saves locally.