Taum Sauk Upper Reservoir Failure

This is a cascading information problem. Call #1 describes a structural collapse and missing persons — it warrants immediate dispatch of whatever resources Reynolds County has available, including notifying state patrol. The challenge is that without knowing a dam has failed, you're treating a flood event. With that context, everything changes: the scope of hazard to responders, the potential for the flood to continue downstream, the need to notify NWS and downstream agencies immediately.

Key dispatch competency: holding the call type loosely until information firms up, while not delaying the initial response. Dispatch the resources. But also ask: what else just happened? When callers describe something that doesn't fit the weather or context you know about, the anomaly is the signal. A family's house doesn't just disappear in a "flood" at 5 AM in December.

This is a structural gap that exists in many jurisdictions. FERC, EPA, and state agencies require EAPs for dams, chemical facilities, and industrial infrastructure — but those plans are written between the facility and the regulatory body. Your PSAP may or may not be in the notification chain, and even if it is, the practical question is: does your dispatcher on the 3 AM shift know who calls them and what that call means?

Discussion starter for supervisors: pull your county's dam inventory and ask who holds the EAPs. Are any of those EAPs current? Does any notification procedure route to your center in a way a dispatcher would actually recognize? This is a pre-incident planning gap, not an ops failure — but it becomes an ops failure the morning the dam breaks.

In many jurisdictions, NWS warnings flow to Emergency Management, not to the 911 center directly. Your PSAP may be downstream of a chain that runs: event → NWS → county EM → public alert → 911 calls start coming in. That's backwards from a dispatch perspective. By the time you're receiving 911 calls about a flash flood, the event is already happening to someone.

In the Taum Sauk case, NWS was the functional public notification mechanism — but they also weren't notified until after the failure was underway. Explore: does your county EM have a direct line to your PSAP for NWS-level events? Do you receive Wireless Emergency Alerts simultaneously with the public, or after? Who in your county is the first call for the NWS warning coordination officer at 3 AM?

Without knowing the source of the flooding, dispatchers can't effectively brief responding units on the hazard they're entering. A flash flood from rain runoff is a different responder risk profile than a dam-breach wave that's already emptied. The peak flow had passed by the time responders arrived — but dispatchers at the time of dispatch didn't know that.

This is a common limitation: you can only brief on what you know. The training point is what questions to ask that would accelerate your understanding of the hazard type. "Is the water still rising?" "What was the water level before it hit?" "Did anyone see where it came from?" These aren't just good customer service — they're responder safety questions.

When a dam fails and you don't know downstream containment status, the conservative approach is to treat every downstream community as threatened until you have information otherwise. That means coordinating voluntary evacuation advisories, notifying downstream PSAPs, and getting someone on the phone with whoever can tell you what the lower reservoir's status is.

The challenge: Reynolds County dispatchers had the most immediate victim situation (the Toops family rescue) plus a potential catastrophic downstream threat — simultaneously. How do you triage? This is a supervisor decision as much as a dispatcher decision. This exercise is worth exploring: when do you call in off-duty staff, when do you call for mutual aid dispatch support, and who makes that call at 5:30 AM?

This is normalization of deviance — the same concept explored in the Staten Island Ferry Barberi exercise (#031). AmerenUE knew the sensors were unreliable. They created a workaround. The system kept running. Nothing bad happened. So the workaround became the norm. Then one morning at 5 AM, the workaround failed at the worst possible moment.

In comm centers, this shows up as: procedures that haven't been reviewed because "we've always done it this way," CAD notes that get ignored because "that caller always calls," systems running on deferred maintenance because "it works fine," and training gaps that persist because "nothing's gone wrong yet." The question isn't whether your center has a Taum Sauk — it's which one it is.

This is a county emergency management coordination question. Most centers don't have this list — and that's the gap. Your state dam safety office maintains an inventory of regulated dams. Your state emergency management agency may have contacts at facilities with FERC or EPA-required EAPs. The question to ask EM: if facility X calls to report a dam failure at 3 AM, what is the EAP notification chain to our center, and does our dispatcher know what to do with that call?

In many counties, the flow is: NWS issues warning → IPAWS/WEA broadcast to phones → public calls 911. Your dispatchers are often in a reactive position. Some centers have direct NWS feeds, EAS receivers on console, or county EM liaison protocols that push warnings directly. If your center doesn't have that, a conversation with your county EM director about creating a direct notification protocol is a low-cost improvement with high potential value.

Many centers don't have one, because it's impossible to protocol-ize every low-frequency high-consequence event. What centers can do is train the underlying skill: recognizing when a call's presentation is inconsistent with the known context, escalating quickly, and buying time for information to develop while not waiting on information before dispatching. "We don't wait to respond — we respond and gather information simultaneously" is a trainable disposition, not just a policy statement.