Two dispatchers. 435 calls in six hours. The NWS issued a flash flood warning at 1:14 AM — three hours before the river rose 22 feet. Kerr County did not use IPAWS. CodeRED reached opt-in subscribers only. 27 died at Camp Mystic. The county judge said: "We have no warning system."
Shortly after midnight on the Fourth of July, the Guadalupe River in Kerr County, Texas began rising. The National Weather Service had issued a flash flood warning at 1:14 AM. A Flood Watch had been in effect since the previous afternoon. By 2:52 AM, the first 911 call came in — a motel manager near the river reporting "a big flood coming." Two dispatchers were on duty in the Kerrville Police Department's telecommunications center. In the next six hours, they would handle 435 calls.
The river gauge in Hunt recorded a 22-foot rise in two hours before it failed entirely at 29.5 feet. The Guadalupe crested at 34 feet in Kerrville at 6:45 AM — 35 feet above flood stage. Nearly 10 inches of rain had fallen before sunrise.
Camp Mystic, a century-old all-girls camp on the banks of the river, took the worst of it. The first 911 call from the camp came at 3:57 AM — a counselor stranded on a hill, cabins flooding around her. The camp's owner and director, Dick Eastland, had already been swept away in his SUV at 3:51 AM, along with an unknown number of campers. Twenty-five girls and two counselors did not survive. One camper remains missing.
What the comm center saw, and when. Color coding indicates the operational dimension.
Kerr County did not use the federal IPAWS system — the same system used for Amber Alerts — to send warnings to all mobile phones during the critical hours. CodeRED, the county's opt-in alert system, reached only subscribers. Some received it after 10 AM. Three Kerr County officials responsible for emergency response told state lawmakers they were asleep or out of town when the flooding began. At 4 AM, a dispatcher could be heard on radio asking: "Is there any way we can get one or two more people here?"
The systems were there. IPAWS. CodeRED. Swift water teams. NWS warnings with three hours of lead time. What failed was the plan for using them at 3 AM on a holiday when the people who hold authority were asleep. Your job as a dispatcher is to know those systems and those pathways before you need them — and to advocate for a center that gives you the tools to use them.
The decision to call for backup should be protocol-driven, not a judgment call made at hour three of a mass casualty event. Does your center have a defined call volume or incident type that automatically triggers a recall? If not, who holds that authority?
You cannot triage callers you haven't answered. At some saturation point, speed of pickup becomes more important than duration of call. Quick location confirmation + "help is coming, get to high ground" may be the best you can offer — and it's still better than ringing out.
Treat callbacks as priority updates. A callback usually means the situation escalated. Floor → attic → roof is a real-time survival curve. If you can, flag these in CAD for responding units.
Give callers a self-rescue instruction and a reason to stay off the line. "Get to the highest point in the structure. Keep this line clear so I can send help to you and others. I have your location." Not a dismissal — a directive that keeps them focused and frees your line.
Track "last known" vs. "confirmed rescue" in your CAD notes during a flood. That list is your accountability record when the event is over.
WEA, IPAWS, and CodeRED are different systems with different reach. WEAs from NWS cannot include evacuation instructions — only the county can do that via IPAWS. CodeRED is opt-in. Know which system applies to which message and who is authorized to activate each.
The problem at Kerr County wasn't the absence of systems — it was the absence of a plan to use them. CodeRED had been in place since 2009. IPAWS authorization had been in place even longer. Does your center's after-action plan include who calls whom if the Emergency Management coordinator doesn't answer at 3 AM?
A leading indicator from one call can predict mass casualty at scale. Two girls swept downstream from a children's camp in a flood is not an isolated rescue. The 4:19 AM call from a downstream resident was the earliest actionable indicator that something catastrophic had happened upstream — more than two hours before the official command thread mentioned the camp.
Connect the dots in CAD. Every call from the Hunt area, the Guadalupe River corridor, and anywhere near Camp Mystic in this window should be linked. When a SAR request finally comes in, responders should be able to see the full picture going back to the first call.
Acknowledge scope and give a status, not a dead end. "I'm logging 20 to 40 missing. I'm escalating to search and rescue command right now. We have swift water teams staged. The road to you is cut off but we are working alternate access." Not a promise of immediate rescue — a meaningful update.
Do not send civilians into active floodwater. Untrained rescuers in fast-moving water become additional victims. Redirect their energy: "The best thing you can do right now is stay clear of the water and call us if you see someone who needs rescue." Document any civilian rescue activity that does happen.
Critical incident stress debriefing is not optional after a shift like this. A structured peer-and-professional debrief in the 24–72 hours following the event. The 911 community consistently undertreats the psychological impact of high-casualty events on telecommunicators — in part because dispatchers are not on scene, and therefore their trauma is treated as secondary or invisible.
No right answers. Tap a question to expand the analysis. Use one or all — whatever fits your time.
The Kerrville dispatcher asked for backup at approximately 4 AM — while already managing a flood MCI on two phones simultaneously. That timing matters.
Know your threshold before the incident — The decision to call for backup should be protocol-driven, not a judgment call made at hour three of a mass casualty event. Does your center have a defined call volume or incident type that automatically triggers a recall? If not, who holds that authority?
The supervisor or on-call lieutenant can authorize recall — A single call out of queue to reach your supervisor is less harmful than letting another 40 callers go unanswered. The sooner you ask, the sooner help arrives.
Mutual aid dispatch exists for this — Multiple centers took overflow 911 calls during Hurricane Helene. Kerr County reportedly transferred some calls to neighboring dispatch centers. Do you know which center would take yours, how that routing works, and who initiates it?
You cannot triage callers you haven't answered — At some saturation point, speed of pickup becomes more important than duration of call. Quick location confirmation + "help is coming, get to high ground" may be the best you can offer — and it's still better than ringing out.
One Kerrville dispatcher managed a 24-minute call with a mother and two young children trapped in a flooding home — while simultaneously working another line and radio. The sheriff noted it by name: "Our dispatcher did a great job during that phone call." That's real. It's also not sustainable across 435 calls. Your system needs to support your people before they break.
This is one of the hardest dispatching problems in a mass-casualty flood: every repeat caller is a person whose situation has gotten worse, and every answered call means someone else is still on hold.
Document location on first call, update on callbacks — CAD notes should capture where they were, what they reported, and what you told them. When they call back, you're not starting over.
Treat callbacks as priority updates — A callback usually means the situation escalated. Floor → attic → roof is a real-time survival curve. If you can, flag these in CAD for responding units.
Give callers a self-rescue instruction and a reason to stay off the line — "Get to the highest point in the structure. Keep this line clear so I can send help to you and others. I have your location." Not a dismissal — a directive that keeps them focused and frees your line.
Track "last known" vs. "confirmed rescue" — Your CAD notes during a flood should differentiate between people you've dispatched resources to and people you've only talked to. That list is your accountability record when the event is over.
One Kerrville caller called back asking when help was coming. The dispatcher answered: "I don't know." That's an honest answer — and a brutal one. But it's better than a false promise that keeps someone passive when they should be moving to higher ground.
This is the most consequential systems question this incident raises.
WEA (Wireless Emergency Alert) — Pushes to all phones in a geographic area automatically when NWS issues certain warning types. The 1:14 AM flash flood warning likely triggered one. But WEAs from NWS cannot include evacuation instructions — only the county can do that.
IPAWS (Integrated Public Alert & Warning System) — The federal system that lets authorized local agencies push alerts to all phones in a defined area, regardless of carrier or whether the recipient has signed up for anything. Same system as Amber Alerts. Kerr County was authorized to use it but did not during the critical overnight hours.
CodeRED — An opt-in system. Reaches only people who have registered. In Kerr County, some people received it after 10 AM. The volunteer firefighter requesting CodeRED activation at 4:22 AM was the actual trigger — it wasn't proactively pushed by officials.
For your center specifically, know: Who is authorized to activate IPAWS in your jurisdiction? Does that authority rest with dispatch, the Emergency Management coordinator, the Sheriff, or the County Judge? What is the protocol when that person is asleep or unreachable at 3 AM? Is there a pre-scripted IPAWS message template ready for flash flood events, or does someone have to write it from scratch?
The Kerr County Judge told reporters at the morning press conference: "We have no warning system." CodeRED had been in place in Kerr County since 2009. IPAWS authorization had been in place even longer. The problem wasn't the absence of systems — it was the absence of a plan to use them.
This call came in at 4:19 AM — more than two hours before Camp Mystic's co-director called requesting search and rescue. It was the earliest actionable indicator that something catastrophic had happened upstream.
Treat it as a SAR trigger, not just a welfare check — Two girls swept downstream from a children's camp in a flood is not an isolated rescue. It is a leading indicator of a mass casualty event at the camp. Ask: "Do you know how many more were at the camp? Are there other campers unaccounted for?"
Document and flag immediately — This information needs to reach your supervisor and IC, not sit in a CAD note. Dispatchers in Kerr County were managing hundreds of calls simultaneously. The mechanism for escalating critical upstream intelligence during a saturated event needs to exist before you need it.
Connect the dots in CAD — Every call from the Hunt area, the Guadalupe River corridor, and anywhere near Camp Mystic in this window should be linked in your event record. When a SAR request finally comes in from the camp at 7:22 AM, responders should be able to see the full picture going back to 3:57 AM.
This is why NWS called dispatch at 4:32 AM — NWS called Kerr County Sheriff's Office asking if roads were closed and if it was flooding. NWS was doing information triangulation. Dispatch should be doing the same in reverse — sharing field intelligence upstream to agencies that can act on it.
The command text thread didn't mention Camp Mystic until 6:34 AM. But dispatch had calls from the camp starting at 3:57 AM, and a caller reporting swept children at 4:19 AM. The information existed. The pathway to move it upward did not function fast enough.
The dispatcher's response is honest and operationally accurate. Responders had tried and were unable to reach the camp due to roads being impassable. But it lands as "we failed to reach you" when the caller is standing in a disaster asking for help.
A stronger response preserves the honesty while giving the caller something actionable.
Acknowledge the scope explicitly — "I'm logging 20 to 40 missing. I'm escalating this to search and rescue command right now."
Get the specific information you need for air and water resources — Roads are out, so the next question is access. "Is there a landing zone available at the camp? Can you give me GPS coordinates or your best landmark?" A helicopter or boat needs different location information than a ground unit.
Give a status, not a dead end — "We have swift water rescue teams staged. The road to you is cut off but we are working alternate access. Stay on your high ground, keep survivors together, and call back if your situation changes." That's not a promise of immediate rescue — it's a meaningful update that gives a frightened person something to hold onto.
Document the count immediately and flag it — "20 to 40 missing" at a children's camp is an MCI declaration. That number needs to be in your CAD record, on your supervisor's radio, and in the command text thread within 60 seconds of this call.
Multiple callers in Kerr County called to offer help. "I know you're overwhelmed, but I'm wondering if a group of us could search — and how and where we can start looking." At 6:11 AM, someone described actively trying to rescue a man caught on a fence in the river using a rope.
Do not send civilians into active floodwater — Kerr County dispatchers told callers they were not accepting outside volunteer searches because it was too dangerous. That's the right call. Untrained rescuers in fast-moving water become additional victims. Swift water rescue is a specialty for a reason.
Redirect their energy to something useful — "The best thing you can do right now is stay clear of the water and call us if you see someone who needs rescue." Give them a role that doesn't put them at risk.
Log civilian rescue activity in CAD — When people do attempt rescues regardless of your direction, document it. The person described helping two girls at 4:19 AM is now part of your incident record. It protects them legally and helps you piece together where victims came from.
Know your formal volunteer activation pathway — Many counties have citizen emergency response teams (CERT) or established volunteer SAR assets. If those exist in your jurisdiction, you need to know who activates them and when — not figure it out during the event.
One man — a security guard at Camp Mystic named Glenn Juenke — is credited with saving dozens of people. He called 911 himself requesting search and rescue. Not all civilian initiative is harmful. The question is how dispatch channels it: toward safety and documentation, or into dangerous improvisation.
The Kerrville chief commended his dispatchers publicly. That matters. But recognition is not a wellness plan. The 911 community consistently undertreats the psychological impact of high-casualty events on telecommunicators — in part because dispatchers are not on scene, and therefore their trauma is treated as secondary or invisible.
Critical incident stress debriefing (CISD) — A structured peer-and-professional debrief in the 24–72 hours following the event. Not a check-in. An actual facilitated process with someone trained to run it.
Peer support access — Does your center have a peer support program? If not, APCO and NENA both have frameworks. A dispatcher who experienced a similar event is often more useful than a counselor who hasn't.
Know your own early warning signs — Sleep disturbance, hypervigilance on shift, intrusive memories of specific calls, numbness, irritability, avoidance of certain call types. These are normal responses to abnormal events. They become a problem when untreated.
EAP is not a substitute — Employee assistance programs offer counseling, but generic therapy is not the same as trauma-informed care for first responders. Know whether your center can refer you to a provider who understands the work.
The Kerrville Police Department noted that all members participated in peer support meetings after the event. That's the right model. A dispatcher who took 20 hours of calls from people who died deserves the same structured support as any other first responder at that incident. The dispatching community is still fighting for that recognition.
Five questions. Answer, then submit for inline feedback. Progress saves locally.