Before the Call — Nisqually Earthquake — 25th Anniversary

The first 90 seconds of earthquake dispatch is fundamentally different from any other incident type because there is no single incident. There are hundreds — or thousands — of simultaneous, unconfirmed reports from callers who are also in shock and also don't know what just happened. The instinct is to treat each call as its own emergency. The correct posture is to recognize that a pattern is emerging, begin building situational awareness at the systemic level, and resist the pull of any single call until priorities can be established.

• The first caller is not the incident — the first caller is the first data point. Northridge hit at 4:30 a.m. The first calls came from people who had no lights, no context, no way to know if their building was structurally sound. Loma Prieta hit at 5:04 p.m. during the World Series — callers at Candlestick Park were describing the stadium shaking before anyone knew the Cypress Viaduct had just killed 42 people. In both cases, and at Nisqually, the dispatcher's job in the first 90 seconds is pattern recognition, not incident management. What geography are these calls coming from? Are there any structural collapse reports yet? Any fire? Any infrastructure reports?
• The 30-to-40-second duration is operationally significant. Nisqually shook for up to 40 seconds. Loma Prieta lasted 15 seconds. A Cascadia Subduction Zone megathrust event could shake for 4–6 minutes. Duration affects damage, duration affects how many people are calling, and duration is something callers will describe. "It just stopped" is as important a data point as "it started." Documenting time of shaking onset and cessation, where available, anchors the incident timeline.
• CAD failure is a real possibility, not a theoretical one. At Northridge, CAD was down for 7 hours. Seven hours of no computer-aided dispatch in a major urban center following the most damaging earthquake in U.S. history at that time. Manual logging, manual resource tracking, radio as the primary information channel. Most centers have not practiced this since the system was installed. The question isn't whether your CAD can survive an earthquake — it's what your center does in the first 30 minutes if it can't.
• Aftershocks are operationally real, not just a geologic footnote. Following Nisqually, the region experienced two confirmed aftershocks. Following Northridge, seismic observatories recorded 3,000 aftershocks greater than M1.5 in three weeks, including an M5.9 one minute after the mainshock. Units in the field, search teams in structures, and responders on damaged infrastructure all face ongoing risk. Dispatch maintaining situational awareness about aftershock activity — through USGS or state seismic network feeds, where available — is part of scene safety support that doesn't exist in any other incident type.

Time of occurrence is one of the most significant variables in earthquake outcomes — and it's one dispatch centers almost never factor into their pre-incident thinking. Where people are when the shaking starts determines where the casualties are. Where the casualties are determines where the calls come from. And the character of those calls changes completely depending on whether people are asleep, commuting, working, or gathered in large venues.

• Pre-dawn (Northridge scenario): City is asleep. Initial calls are disoriented, dark, no visual reference to structural damage. People don't know if their building is sound. Medical calls — heart attacks, fall injuries, trauma from falling objects — dominate the first wave. Gas leaks and fires are harder to detect because fewer people are awake to see them. Fewer vehicles on roads means better access but also fewer witnesses to infrastructure failures. Your center may be short-staffed on a graveyard shift at exactly the moment the call volume explodes.
• Commute hours (worst-case scenario): Maximum exposure on infrastructure. Freeways, bridges, tunnels, trains. Loma Prieta hit just as evening rush was building — and the Cypress Viaduct collapse killed 42 people largely because some commuters were already on it. A morning rush scenario means schools in transit, students on buses, workers in elevators, pedestrians near unreinforced masonry facades. Dispatch receives infrastructure failure reports alongside medical and structural calls simultaneously.
• Business hours (Nisqually scenario): Offices and schools occupied. Construction sites active. Courts and government buildings in session (the State Capitol was in use during Nisqually). Medical calls include workplace injuries and building-evacuation falls. School shelter-in-place or evacuation decisions create parent callback volume that can saturate lines. The aviation piece at Nisqually — Sea-Tac tower damaged, Boeing Field closed — was a business-hours problem. Midday flights were disrupted; that wouldn't have mattered at 4:30 a.m.
• Large event (Loma Prieta scenario): The World Series crowd at Candlestick Park created a unique dispatch picture — 60,000 people in one location, many of whom tried to call out simultaneously. Mass gathering venues, stadiums, concerts, and community events create concentrated caller populations. If your jurisdiction has a stadium, arena, or fairgrounds, what does your CAD look like if 50,000 people all dial 911 within 90 seconds?

Every major earthquake produces two simultaneous incident streams: the human casualty and damage calls, and the infrastructure degradation calls that change the operating environment for every response that follows. A dispatcher managing a structure collapse on the west side of the city needs to know that the bridge route is closed before sending units across it. That information doesn't arrive cleanly or quickly in the first minutes after a major event.

• Road and bridge status tracking is a dispatch function in an earthquake, whether it's formally assigned or not. Units self-reporting passable routes, engine companies reporting bridge conditions they observe en route, public works radio contacts — all of this intelligence flows through the dispatch center even if it isn't the primary call-taking function. Establishing a logging protocol for infrastructure status in the first hour prevents the situation where Unit 7 knows the I-5 on-ramp is blocked but no one else does.
• Airport and helipad availability matters earlier than it seems. At Nisqually, Sea-Tac transitioned to a temporary tower and partial capacity. That affected medevac routing. Air ambulance coordination, medical helicopters, and Search and Rescue aircraft all depend on airport infrastructure. The first time most centers find out an airport is degraded is when they try to activate an air asset and get told the facility is closed. Early confirmation of aviation infrastructure status — before it's needed — is a five-minute call that could save critical time later.
• Utility failures create secondary incident streams. Gas main breaks generate fire risk in areas that may not be near the primary structural damage. Water system failures affect firefighting capability. Power outages affect traffic signals, creating access problems, and they affect facilities like hospitals, dialysis centers, and care homes that dispatch may need to support or route around. Northridge produced fires from ruptured gas lines in areas that also had no water pressure — a combination that is specifically documented in the after-action literature as a dispatch coordination gap.
• The CAD-down scenario is an earthquake-specific planning requirement. Seven hours without computer-aided dispatch — as happened at Northridge — isn't a theoretical edge case. It's a documented outcome of a moderate urban earthquake. Manual logging protocols, radio-only resource tracking, paper run cards, and whiteboard unit status boards aren't archaic fallbacks. They're the earthquake backup system. Does your center know where they are and how to use them? Does your newest dispatcher know how to run a call without a computer?

Aftershock management is one of the most under-prepared dispatch challenges in seismically active regions. The mainshock response is what gets practiced and planned. The aftershock sequence — which may extend for weeks and which changes the risk profile of every structure that was damaged in the mainshock — gets almost no attention in most dispatch training.

• Units in compromised structures face new risk with every aftershock. A structure that was damaged but standing after the mainshock may not survive a significant aftershock. Search and rescue teams inside collapsed buildings, firefighters conducting searches in red-tagged structures, and utility crews working on damaged infrastructure all need real-time aftershock awareness. Dispatch coordinating with USGS or state seismic network feeds — or monitoring ShakeAlert where available — can provide units in the field with advance warning on detected shaking. That's a specific, trainable function.
• Aftershock calls are a second incident flood. An M5.9 aftershock one minute after the mainshock, as happened at Northridge, means the initial wave of calls from the mainshock is still incoming when a new wave begins. Callers who were just managing a minor injury from the mainshock are now calling back because the building shook again. People who evacuated to parking lots and gathering areas may now be reporting new damage. The call character of aftershock calls is different from mainshock calls — more fear, more "is this going to keep happening," more welfare check requests from people who couldn't reach family during the mainshock.
• The "is this the aftershock or the next big one" question is operationally real. After a major event, every subsequent shake is ambiguous until it's measured. Dispatch centers need a protocol for how to communicate with units about ground motion events — not just reporting "we just felt another shake," but integrating whatever seismic network information is available into the operational picture. Washington's ShakeAlert system, launched in 2019, provides seconds of warning before shaking arrives. That's not much, but for units in structurally compromised environments, it's something.

Every major earthquake produces two distinct call populations that arrive through the same channel: people with active emergencies, and people with questions, concerns, and information needs that are urgent to them but not operational emergencies. In the acute phase, these are mixed together. In the recovery phase, the question calls increasingly dominate. The 911 center becomes, involuntarily, the public information hub — because it's the only number people know to call.

• The public information call problem starts within hours, not days. At Nisqually, calls about building inspections, preparedness resources, and damage reports began flooding the emergency management office within the day. FEMA reported receiving 9,695 calls from Seattle businesses and homeowners before the individual assistance registration deadline. Those calls don't all come through 911, but the ones that do — the caller who wants to know if their building is safe, the caller who wants to know when the water will be back on, the caller who wants to know if their neighborhood is under curfew — compete with rescue calls for the same dispatcher attention.
• A dedicated earthquake information line is a pre-incident planning requirement, not a post-incident improvisation. The number needs to exist before the earthquake. It needs to be staffed within the first hour after a significant event. It needs to be communicated through media immediately — because the alternative is that every person in the coverage area calls 911. Seattle's after-action report recommended exactly this, in writing, in 2001. The question for your center is whether that recommendation has been implemented, tested, and whether the number is in your CAD as something to route non-emergency callers toward.
• The building safety question is one dispatchers will hear constantly and cannot answer. "Is it safe to go back into my house?" is a question only a structural inspector can answer — and in the first 24–72 hours after a major event, there are nowhere near enough inspectors to meet demand. Dispatch needs a consistent, accurate, short answer to this question: who to call, where to go, what the current guidance is. Inconsistent answers from different dispatchers create confusion and, potentially, liability. A scripted holding response — accurate, brief, directing callers to the right resource — is a training item, not an improvised response.
• The media and social media dynamic creates a parallel misinformation stream. Loma Prieta was the first earthquake broadcast live to national audiences — ABC cameras were already at Candlestick Park. Within minutes, partial information was being reported as fact. At every major event since, the information environment outside the PSAP moves faster than the confirmed information inside it. Dispatchers fielding calls from people who heard something on the radio or saw something on social media need to know what the official public messaging is — and they need to know it quickly enough to give consistent answers.

This question doesn't have a tactical answer. It has a human one — and it belongs in this exercise because it's the thing no one talks about in earthquake preparedness training.

The dispatcher who takes the first Nisqually call at 10:54 a.m. on February 28, 2001, is also a person who just experienced the earthquake. Their building shook. Their screens may have flickered. Their colleagues may be looking at each other. They don't know yet if the building they're in is structurally sound. They don't know if their family is okay. And they are, at that exact moment, the primary communications link for an entire county's emergency response.

• Dispatcher wellness during an earthquake is a specific, underaddressed topic. CISM programs are designed for discrete critical incidents — a line-of-duty death, a pediatric call that went badly, a long and terrible MCI. Earthquake dispatch is not a discrete incident. It's a 30-to-40-second event followed by hours of high-volume multi-incident response followed by days or weeks of recovery operations — all while the dispatcher is also, personally, an earthquake survivor. The cumulative exposure is different in character from any other incident type in the training literature.
• The "I need to check on my family" pull is real and documented. In major disasters, dispatcher absenteeism following the event — people leaving their posts or not coming in for shifts — is a known problem. People who are worried about family members they can't reach will eventually prioritize that. Pre-event planning that includes family preparedness — so dispatchers know their families have a plan before the event happens — is a documented mitigation strategy for this. It's also a conversation most centers never have.
• Physical safety of the dispatch center itself is not guaranteed. Nisqually damaged the Sea-Tac tower. Northridge knocked out power to much of Los Angeles. A direct hit on an unreinforced masonry building housing a PSAP is not impossible. Backup facility, backup power, backup communications — and knowing where the backup center is and how to activate it in the first minutes after a major event — is an earthquake-specific operational requirement.