Live scanner & dispatch traffic · 24/7
Long-form reference pieces on Seattle public safety, dispatch, and emergency response.
The live feed on Seattle Breaking shows what is happening right now. The articles below explain the context behind it — how Seattle's 911 system actually routes a call, what a "Code 3 response" means, why some neighborhoods generate more dispatch traffic than others, and how to read what you see on the map. They are written for a general reader, not for analysts or first responders.
A walkthrough of the path a Seattle 911 call takes from the moment you press send to the moment a unit arrives — including why the operator asks the same question three different ways and how dispatchers decide whether to send one truck or four.
What "AID Response," "Aid-MVI," "Auto Fire Alarm" and the rest of the SFD type strings actually mean — and why an "Aid Response" sometimes shows up with four units while a "Structure Fire" can clear in fifteen minutes with two.
"DV — Disturbance," "Suspicious Circumstance," "Welfare Check," "Trespass — Premise Check" — what those clearance descriptions mean in practice and what they don't mean. Includes notes on why SPD data appears in our feed hours after the fact.
Dispatch volume is not the same as danger. A walkthrough of the demographic, geographic, and infrastructural reasons why downtown Seattle, the Aurora corridor, and the International District show more calls than Magnolia or View Ridge — and why that doesn't mean what people sometimes assume.
The Seattle Fire Department runs 33 stations and roughly 230 firefighters per shift across 84 square miles. How are responses actually assigned? Why does Station 10 dispatch a ladder truck to North Capitol Hill when Station 25 is closer? An explainer on coverage zones and mutual aid.
Seattle sits on top of the Seattle Fault and adjacent to the Cascadia Subduction Zone. What that actually means for your apartment, your car, and your weekend plans — plus a concrete, two-hour preparedness checklist you can finish today.
Across roughly 350,000 fire and EMS calls per year in Seattle, a handful of categories dominate the numbers. What are they, why are they so prevalent, and what does the breakdown tell us about how the city allocates its public-safety resources?
An overview of the radio frequencies and online tools used to listen to Seattle Fire, SPD, King County Sheriff, and surrounding agencies — plus what's legal, what's encrypted, and the etiquette of using public safety audio responsibly.
How Seattle went from paper run-cards in the 1970s to the unified CAD system that powers the data on this site. Includes the political fights that shaped the technology and why the SFD and SPD ended up with different CAD vendors for so long.
Seattle's open data portal is one of the more mature public-safety data programs in the country, but it isn't the only one. A tour of what Seattle, King County, Bellevue, Tacoma, and Portland publish — and what they conspicuously don't.