🌊 Fort Smith Flash Flood Drowning

Flood rescues break the normal relationship between an address and a scene. Your job is to stop thinking in a single point and start building a searchable box that gets tighter with every minute. The call succeeds when you can give responders a bounded area they can safely access and systematically clear.

• Establish a last-known anchor. Get the best available starting point: any stated address, intersection, complex name, roadway, or landmark—then immediately validate it with whatever location tools you have (ALI/Phase II, mapping layers, prior calls in the same area). Treat the first anchor as provisional and keep updating it.
• Run a structured "flood location script." Don't free-chat. Ask for: nearest cross street / business sign / apartment complex name, direction of travel before stopping, what they can see (streetlights, bridge, culvert, creek), and what they can hear (traffic, running water, sirens). If the vehicle may drift, ask what direction the current is pushing them.
• Translate to responder terms. Convert caller language ("I'm by the apartments") into a response plan ("Search the west edge of the complex near the drainage channel; start at the highest ground access point"). Give field units a search pattern, not just a guess.
• Keep the caller contributing. Calm = data. Coach the caller to conserve energy, keep the phone high, use flashlight/hazards if possible, and describe any change in surroundings. Even tiny updates can re-vector responders.

Surge conditions are where triage becomes a safety system. When everything feels urgent, the center must force clarity: which calls are immediately survivable with rapid action, which are stable-but-stuck, and which are information-only road hazards.

• Separate "in-water" from "near-water." A vehicle stalled near standing water is not the same as a vehicle being entered by moving water. Create a triage split early and route life-risk water entry calls to a supervisor-aware track.
• Escalate with a trigger, not a vibe. Define dispatch triggers: water entering the passenger compartment, inability to self-extricate, caller non-swimmer, vehicle moving/drifting, loss of visibility, or caller becoming hypoxic/panicked. Those triggers should drive priority and resource escalation automatically.
• Use a surge board for resource visibility. In floods, the limiting factor is often access and rescue capability. Keep a live view of boat/swift-water assets, barricade units, and the safest ingress routes so you're not re-learning the same blockage on every call.
• Assign an incident manager function. When call volume spikes, one person must own cross-call pattern recognition (same complex, same drainage channel, same blocked bridge). That reduces duplicate dispatching and speeds up accurate routing.

Scolding isn't just "unprofessional." It degrades performance. A panicked caller is your only sensor inside the scene—your only way to tighten location, track changes, and maintain survivability actions. If you break rapport, you break the data stream.

• It increases cognitive noise. A dysregulated caller talks more, repeats, and stops processing instructions. That burns time, blocks new information, and makes it harder to run a structured location script.
• It reduces compliance. A caller who feels judged is less likely to follow survivability coaching (stay belted/unbelted appropriately, keep phone high, conserve energy, report changes). Compliance is the difference between "still searchable" and "lost."
• It can cause disengagement. On long, high-stress calls, callers sometimes stop answering, hang up, or shift to calling family—especially if the dispatcher feels adversarial. That destroys continuity when continuity is what keeps the rescue coordinated.
• It erodes shared reality with responders. When the caller can't be kept calm enough to provide updates, responders lose the only live feed that tells them whether the vehicle is stationary, drifting, submerging, or changing orientation.

Dispatch has to hold two truths at once: the caller needs urgency, and responders need survivable tactics. Your language must communicate action and intent while acknowledging safety limits that are real, not optional.

• Communicate actions, not debates. Say what is happening: "Units are en route," "They are trying to reach you," "A boat is being moved to your area," instead of explaining why something is hard in a way that feels dismissive.
• Coach survivability while resources move. If entry is delayed, the call must shift to survivability instructions: keep the phone above water, conserve breath, avoid opening doors against pressure, move to the highest point in the vehicle if safe, and keep visual cues active.
• Keep the field loop tight. When units report blocked roads or "can't locate," immediately convert that into updated caller questions and updated routing. The goal is to shorten the feedback loop between caller, dispatch, and field.
• Use plain language about risk. "The current is too fast for them to enter safely right now" is clearer than "we can't," and it frames the delay as a tactical constraint, not abandonment.