A HIGH avalanche warning had been in effect since 5 AM. Fifteen backcountry skiers were buried by a storm-slab avalanche near Castle Peak. Notification arrived via satellite messenger and the guide company simultaneously — not a voice 911 call. Helicopters grounded. Eight dead. The deadliest U.S. avalanche since 1981.
On Tuesday morning, a group of 15 backcountry skiers — including four guides from Blackbird Mountain Guides — were returning to the trailhead at the conclusion of a three-day trip when a massive storm-slab avalanche buried the group near Castle Peak, northwest of Lake Tahoe. A HIGH avalanche warning had been in effect since 5 AM that morning.
The 911 notification came via satellite messenger and the guide company simultaneously — not a direct voice call. Six survivors sheltered in place under a tarp for several hours while 46 first responders battled blizzard conditions and active avalanche danger to reach them. Helicopters were grounded. Roads were closed. The mission shifted from rescue to recovery by Wednesday morning. It is the deadliest avalanche in the United States since 1981.
What the comm center saw, and when. Color coding indicates the operational dimension.
For dispatch, Castle Peak is a multi-layer training case: a wilderness mass casualty incident that arrived through non-voice notification, in extreme weather that progressively eliminated standard rescue resources, with a survival window measured in minutes that had already closed by the time responders were notified, and a 36-hour operation spanning multiple shifts and agencies. Every layer is its own dispatch challenge. Together they are the kind of incident every PSAP in mountain terrain needs to be ready for, even though almost none have specific protocols for it.
Exact location is the first question — GPS coordinates if possible. A landmark name is a large area. Ask for trailhead name, any nearby reference point, or a pin from their phone. Many backcountry groups have no cell signal — this group used a Garmin inReach.
How many are buried vs. not changes resource calculation immediately. 7 buried vs. 2 buried is a very different response. Are unburied survivors doing companion rescue? Avalanche protocol: companion rescue is the fastest intervention. Are they digging?
Are there active hazards overhead? More slides possible? This protects your responders and affects approach routes. Avalanche forecasters in this incident were hesitant to send anyone on a snowmobile due to trigger risk.
Avalanche burial survival statistics are time-driven and steep: 0–15 minutes ~90% survival if located; 15–30 minutes drops to ~50%; 30–45 minutes ~30%; beyond 45 minutes most burials are fatal. Every minute of dispatch processing time compounds an already grim clock.
Non-voice notification handling needs to be in your CAD workflow before you need it. In this incident, notification came via the guide company AND a satellite beacon simultaneously — not a direct voice 911 call. Are your CAD workflows set up to handle that?
Resource degradation is the real-time problem. Helicopters grounded. Roads closed. Snowmobiles unsafe. Your role shifts from logistics coordinator to real-time problem solver: track what's still available vs. what's been pulled, find the next best option, and update IC in real time.
Dispatch carries safety information, not just logistics. If a responder is about to enter an active avalanche zone, they need to hear that from dispatch, clearly and immediately. Avalanche forecaster guidance about trigger risk is dispatch-relevant safety information.
Initial information in any mass casualty or SAR event is almost always wrong. Initial report: 16 people → revised to 15. Initially "10 missing" → revised to 9. Document every version. Brief IC on changes. Flag uncertainty in your transmissions ("Caller reports 16 — unconfirmed").
Clean shift briefings are not optional in a 36-hour incident. The incoming dispatcher needs current status, who's in command, what resources are active, and what's outstanding. Don't make them dig for it. Single source of truth — everything goes into CAD. Parallel documentation in texts and emails creates gaps.
Media calls are not yours. Route to PIO, immediately and without exception. Family calls will come — law enforcement and victim services handle notifications, not dispatch, but families will call your center. Have a clear script and warm transfer protocol before you need it.
Know your non-traditional partners before you need them. Nevada County SAR pulled ski teams from Boreal Mountain ski resort as a critical access resource. Industrial sites, ski resorts, wilderness outfitters, and event organizers can all be assets — if you know who to call.
No right answers. Tap a question to expand the analysis. Use one or all — whatever fits your time.
Exact location — GPS coordinates if possible. A landmark name is a large area. Ask for trailhead name, any nearby reference point, or a pin from their phone.
How many are buried vs. not? This changes resource calculation immediately. 7 buried vs. 2 buried is a very different response.
Are unburied survivors doing companion rescue? Avalanche protocol: companion rescue is the fastest intervention. Are they digging?
What is the callback method? Cell? Satellite messenger? Can you maintain contact? Many backcountry groups have no cell signal. This group used a Garmin inReach.
Are there active hazards overhead? More slides possible? This protects your responders and affects approach routes.
In this incident, notification came via the guide company AND a satellite beacon simultaneously — not a direct voice 911 call. Are your CAD workflows set up to handle non-voice emergency notifications?
Survival statistics are time-driven and steep: 0–15 minutes ~90% survival if located; 15–30 minutes drops to ~50%; 30–45 minutes drops to ~30%; beyond 45 minutes the majority of burials are fatal.
By the time responders received notification in this incident, most victims had already been buried well past the survival window. This became a mass casualty situation immediately. Every minute of dispatch processing time compounds an already grim clock — and every second matters when resources are far away.
This event required 46 responders across multiple agencies. Think through your notification tiers.
Immediate dispatch: County Sheriff SAR · Fire / EMS (trauma-capable) · Law Enforcement (scene control).
Specialty resources (immediate notification): HELO (weather-dependent) · Avalanche / Mountain Rescue · Regional SAR Teams · Red Cross / Mass Casualty.
Notifications (sooner = better): Emergency Management · Medical Examiner (MCI) · Hospital Alert (MCI protocol) · Incident Commander.
Nevada County SAR pulled ski teams from a nearby ski resort (Boreal Mountain) as a critical access resource. Do you know which non-traditional partners in your area could provide specialized terrain access? It's worth knowing before you need it.
This is a resource degradation scenario — your tools keep getting taken off the table. Your role shifts from logistics coordinator to real-time problem solver.
Keep tracking what's still available vs. what's been pulled. Update your IC in real time.
Find the next best option — In this case: ski teams on foot. SnoCats. Wait for a weather window. That decision lives with the IC, but the information has to flow through you.
Manage expectations upward and outward — Supervisors, IC, and responding units all need to know the timeline has changed and why.
Protect responders — Avalanche forecasters told Nevada County they were "hesitant to send anyone on a snowmobile" due to trigger risk. Dispatch carries that safety information and must pass it clearly.
Your job includes passing critical safety information to the IC — not just logistics. If a responder is about to enter an active avalanche zone, they need to hear that from dispatch, clearly and immediately.
Initial information in any mass casualty or SAR event is almost always wrong. Chaos, emotional callers, and poor communications all contribute. In this incident: initial report 16 people → revised to 15. Initially "10 missing" → revised to 9.
Document every version — CAD notes should reflect when each update was received, what changed, and who provided it.
Brief IC on changes immediately — A shift from 10 to 9 missing affects resource deployment and search grids.
Flag uncertainty in your transmissions — "Caller reports 16 — unconfirmed" is more useful and more honest than stating it as established fact.
Strong CAD documentation during a dynamic, long-duration incident protects the agency, supports the after-action review, and builds the institutional knowledge that makes the next incident go better.
Clean shift briefings — The incoming dispatcher needs the current status, who's in command, what resources are active, and what's outstanding. Don't make them dig for it.
Single source of truth — Everything goes into CAD. Parallel documentation in texts, emails, and whiteboards creates gaps and contradictions.
Know the agency spokesperson — Media will call. You do not give information to media. You route to PIO, immediately and without exception.
Family calls will come in — Law enforcement and victim services handle notifications, not dispatch. But families will call your center. Have a clear script and a warm transfer protocol before you need it.
The guide company proactively contacted the emergency contacts of all clients involved. That's a professional organization being a good partner. Does your center have a protocol for incorporating and documenting information from third parties — guide companies, resorts, outfitters, event organizers?
Think about what Nevada County had to figure out in real time:
Who are the avalanche and SAR specialty teams in my region, and how do I activate them?
What's the closest facility capable of handling multiple hypothermia and trauma patients simultaneously?
Does our CAD system have a way to log a satellite messenger callback contact?
Do I have contact information for nearby ski resorts, wilderness outfitters, or backcountry hut operators who might be callers — or critical resources?
What's the specific trigger threshold for our MCI protocol? Who is our Liaison Officer for incidents that cross jurisdictional lines?
That's the point of this exercise. The goal isn't to have every answer memorized. It's to know where to find the answer fast, under pressure, when it matters most.
Five questions. Answer, then submit for inline feedback. Progress saves locally.