Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Homicide

Homicide calls over time: volume, outcomes, and response speed

Homicide: Call Volume

Call volume is the number of events logged in the Seattle Police Department’s Computer-Aided Dispatch (CAD) system. It counts calls from the public (by 911, phone, text or alarm) as well as officer-initiated activity, once per event, grouped by the call type assigned when the call was dispatched, before any investigation. It is not the same as the number of crimes reported.

Included: Every event logged in CAD: calls from the public and events officers logged themselves (52% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
0751502009: 89 homicide calls logged in CAD2010: 87 homicide calls logged in CAD2011: 45 homicide calls logged in CAD2012: 82 homicide calls logged in CAD2013: 85 homicide calls logged in CAD2014: 109 homicide calls logged in CAD2015: 80 homicide calls logged in CAD2016: 71 homicide calls logged in CAD2017: 69 homicide calls logged in CAD2018: 68 homicide calls logged in CAD2019: 71 homicide calls logged in CAD2020: 113 homicide calls logged in CAD2021: 63 homicide calls logged in CAD2022: 81 homicide calls logged in CAD2023: 106 homicide calls logged in CAD2024: 99 homicide calls logged in CAD2025: 67 homicide calls logged in CAD2026: 68 homicide calls logged in CAD2009n=892011n=452013n=852015n=802017n=692019n=712021n=632023n=1062025n=672026n=68
homicide calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodHomicide calls logged in CAD
200989
201087
201145
201282
201385
2014109
201580
201671
201769
201868
201971
2020113
202163
202281
2023106
202499
202567
202668
Homicide Calls Are Down 41% From Their 2020 PeakSeattle Police logged 113 homicide calls in 2020 and 67 in 2025, the most recent full year.

Homicide: What Happened When Officers Responded

Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.

Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.

Swipe sideways to see the full chart →
100%50%0%2009 · Arrest / citation: 3.4%2009 · Report taken, no arrest: 66.3%2009 · Resolved on scene: 25.8%2009 · Unable to locate: 2.2%2009 · Other (unfounded / cancelled): 2.2%2010 · Arrest / citation: 8.0%2010 · Report taken, no arrest: 59.8%2010 · Resolved on scene: 27.6%2010 · Unable to locate: 2.3%2010 · Other (unfounded / cancelled): 2.2%2011 · Arrest / citation: 6.7%2011 · Report taken, no arrest: 64.4%2011 · Resolved on scene: 24.4%2011 · Unable to locate: 4.4%2012 · Arrest / citation: 7.3%2012 · Report taken, no arrest: 63.4%2012 · Resolved on scene: 28.0%2012 · Other (unfounded / cancelled): 1.2%2013 · Arrest / citation: 4.7%2013 · Report taken, no arrest: 69.4%2013 · Resolved on scene: 21.2%2013 · Unable to locate: 4.7%2014 · Arrest / citation: 2.8%2014 · Report taken, no arrest: 79.8%2014 · Resolved on scene: 14.7%2014 · Unable to locate: 2.8%2015 · Arrest / citation: 7.5%2015 · Report taken, no arrest: 73.8%2015 · Resolved on scene: 17.5%2015 · Unable to locate: 1.2%2016 · Arrest / citation: 9.9%2016 · Report taken, no arrest: 76.1%2016 · Resolved on scene: 11.3%2016 · Unable to locate: 1.4%2016 · Other (unfounded / cancelled): 1.4%2017 · Arrest / citation: 8.7%2017 · Report taken, no arrest: 78.3%2017 · Resolved on scene: 10.1%2017 · Other (unfounded / cancelled): 2.8%2018 · Arrest / citation: 8.8%2018 · Report taken, no arrest: 80.9%2018 · Resolved on scene: 7.4%2018 · Unable to locate: 2.9%2019 · Arrest / citation: 15.5%2019 · Report taken, no arrest: 66.2%2019 · Resolved on scene: 15.5%2019 · Unable to locate: 2.8%2020 · Arrest / citation: 15.0%2020 · Report taken, no arrest: 73.5%2020 · Resolved on scene: 11.5%2021 · Arrest / citation: 4.8%2021 · Report taken, no arrest: 76.2%2021 · Resolved on scene: 12.7%2021 · Unable to locate: 3.2%2021 · Other (unfounded / cancelled): 3.2%2022 · Arrest / citation: 12.3%2022 · Report taken, no arrest: 85.2%2022 · Resolved on scene: 2.5%2023 · Arrest / citation: 13.2%2023 · Report taken, no arrest: 79.2%2023 · Resolved on scene: 4.7%2023 · Unable to locate: 2.8%2024 · Arrest / citation: 12.1%2024 · Report taken, no arrest: 77.8%2024 · Resolved on scene: 10.1%2025 · Arrest / citation: 13.4%2025 · Report taken, no arrest: 77.6%2025 · Resolved on scene: 9.0%2026 · Arrest / citation: 10.3%2026 · Report taken, no arrest: 70.6%2026 · Resolved on scene: 19.1%2009n=892011n=452013n=852015n=802017n=692019n=712021n=632023n=1062025n=672026n=68
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
2009893.4%66.3%25.8%2.2%2.2%
2010878.0%59.8%27.6%2.3%2.2%
2011456.7%64.4%24.4%4.4%—
2012827.3%63.4%28.0%—1.2%
2013854.7%69.4%21.2%4.7%—
20141092.8%79.8%14.7%2.8%—
2015807.5%73.8%17.5%1.2%—
2016719.9%76.1%11.3%1.4%1.4%
2017698.7%78.3%10.1%—2.8%
2018688.8%80.9%7.4%2.9%—
20197115.5%66.2%15.5%2.8%—
202011315.0%73.5%11.5%——
2021634.8%76.2%12.7%3.2%3.2%
20228112.3%85.2%2.5%——
202310613.2%79.2%4.7%2.8%—
20249912.1%77.8%10.1%——
20256713.4%77.6%9.0%——
20266810.3%70.6%19.1%——
“Unable to Locate” Outcomes Are Holding Near 0% of Homicide CallsReport-taken outcomes moved from 76% of calls in 2016 to 71% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Homicide: How Long It Took

Response time is how long it took, from the moment a called-in event was queued with dispatch, until the first officer arrived on scene. Dispatch delay is the first part of that wait: the time before an officer was assigned and sent. Both lines show the average, which a small number of very long waits pull up, so it runs higher than the typical (median) call.

Included: Only events called in by the public and dispatched to an officer. The averages use those with a recorded officer arrival. The n= under each bar is the number of called-in events. Excluded: Events officers logged themselves (on view), which are 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min40 min80 min2009: 10.4 min2010: 11.2 min2011: 4.4 min2012: 4.4 min2013: 2.3 min2014: 20.8 min2015: 11.0 min2016: 7.0 min2017: 6.5 min2018: 6.5 min2019: 12.1 min2020: 11.8 min2021: 1.9 min2022: 17.4 min2023: 3.8 min2024: 27.2 min2025: 14.2 min2026: 61.7 min2009: 19.7 min2010: 16.8 min2011: 8.3 min2012: 8.0 min2013: 8.2 min2014: 26.6 min2015: 22.2 min2016: 11.7 min2017: 11.6 min2018: 16.3 min2019: 19.7 min2020: 20.7 min2021: 6.0 min2022: 22.4 min2023: 9.2 min2024: 21.3 min2025: 20.7 min2026: 60.7 min2009n=202011n=192013n=272015n=462017n=372019n=402021n=302023n=612025n=412026n=36
Average response timeAverage dispatch delay
Small sample: Only a small share of homicide events are called in. The year with the fewest had only 19, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20092010.4 min19.7 min
20102011.2 min16.8 min
2011194.4 min8.3 min
2012314.4 min8.0 min
2013272.3 min8.2 min
20144420.8 min26.6 min
20154611.0 min22.2 min
2016367.0 min11.7 min
2017376.5 min11.6 min
2018416.5 min16.3 min
20194012.1 min19.7 min
20205811.8 min20.7 min
2021301.9 min6.0 min
20225017.4 min22.4 min
2023613.8 min9.2 min
20245627.2 min21.3 min
20254114.2 min20.7 min
20263661.7 min60.7 min
The Average Call Waits 61 Minutes for an Officer to ArriveDespite a 6% drop in calls between 2016 and 2025, average response time has grown about 5-fold in the past 10 years, from 12 minutes in 2016 to 61 in 2026, driven largely by dispatch delays. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Homicide: How Long It Took, in Full

The same response times, broken into bands so the slowest calls are visible. Each bar shows the share of called-in events by how long the first officer took to arrive after the event was queued, including the ones that took hours. “No recorded response” means no arrival was ever logged.

Included: Only events called in by the public and dispatched to an officer, including those with no recorded arrival (shown as “No recorded response”). Excluded: Events officers logged themselves (on view), which are 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
100%50%0%2009 · 0–5 min: 55.0%2009 · 5–30 min: 35.0%2009 · 1–4 hr: 10.0%2010 · No recorded response: 5.0%2010 · 0–5 min: 70.0%2010 · 5–30 min: 10.0%2010 · 30–60 min: 5.0%2010 · 1–4 hr: 10.0%2011 · No recorded response: 10.5%2011 · 0–5 min: 47.4%2011 · 5–30 min: 36.9%2011 · 30–60 min: 5.3%2012 · No recorded response: 3.2%2012 · 0–5 min: 61.3%2012 · 5–30 min: 29.0%2012 · 30–60 min: 3.2%2012 · 1–4 hr: 3.2%2013 · 0–5 min: 48.1%2013 · 5–30 min: 51.9%2014 · No recorded response: 4.5%2014 · 0–5 min: 45.5%2014 · 5–30 min: 29.6%2014 · 30–60 min: 11.4%2014 · 1–4 hr: 6.8%2014 · 4–8 hr: 2.3%2015 · 0–5 min: 41.3%2015 · 5–30 min: 41.3%2015 · 30–60 min: 2.2%2015 · 1–4 hr: 15.2%2016 · No recorded response: 11.1%2016 · 0–5 min: 38.9%2016 · 5–30 min: 38.9%2016 · 30–60 min: 8.3%2016 · 1–4 hr: 2.8%2017 · 0–5 min: 70.3%2017 · 5–30 min: 21.6%2017 · 30–60 min: 2.7%2017 · 1–4 hr: 5.4%2018 · No recorded response: 2.4%2018 · 0–5 min: 53.7%2018 · 5–30 min: 31.7%2018 · 30–60 min: 7.3%2018 · 1–4 hr: 4.9%2019 · No recorded response: 2.5%2019 · 0–5 min: 47.5%2019 · 5–30 min: 32.5%2019 · 30–60 min: 7.5%2019 · 1–4 hr: 10.0%2020 · No recorded response: 5.2%2020 · 0–5 min: 46.5%2020 · 5–30 min: 34.5%2020 · 30–60 min: 5.2%2020 · 1–4 hr: 8.6%2021 · No recorded response: 3.3%2021 · 0–5 min: 63.3%2021 · 5–30 min: 30.0%2021 · 30–60 min: 3.3%2022 · 0–5 min: 62.0%2022 · 5–30 min: 30.0%2022 · 1–4 hr: 6.0%2022 · Over 8 hr: 2.0%2023 · 0–5 min: 47.5%2023 · 5–30 min: 45.9%2023 · 30–60 min: 3.3%2023 · 1–4 hr: 3.3%2024 · No recorded response: 3.6%2024 · 0–5 min: 46.4%2024 · 5–30 min: 39.3%2024 · 30–60 min: 3.6%2024 · 1–4 hr: 5.4%2024 · Over 8 hr: 1.8%2025 · 0–5 min: 48.8%2025 · 5–30 min: 31.7%2025 · 30–60 min: 9.8%2025 · 1–4 hr: 9.8%2026 · No recorded response: 5.6%2026 · 0–5 min: 30.6%2026 · 5–30 min: 36.1%2026 · 30–60 min: 11.1%2026 · 1–4 hr: 8.3%2026 · 4–8 hr: 5.6%2026 · Over 8 hr: 2.8%2009n=202011n=192013n=272015n=462017n=372019n=402021n=302023n=612025n=412026n=36
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of homicide events are called in. The year with the fewest had only 19, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in events0–5 min5–30 min1–4 hrNo recorded response30–60 min4–8 hrOver 8 hr
20092055.0%35.0%10.0%————
20102070.0%10.0%10.0%5.0%5.0%——
20111947.4%36.9%—10.5%5.3%——
20123161.3%29.0%3.2%3.2%3.2%——
20132748.1%51.9%—————
20144445.5%29.6%6.8%4.5%11.4%2.3%—
20154641.3%41.3%15.2%—2.2%——
20163638.9%38.9%2.8%11.1%8.3%——
20173770.3%21.6%5.4%—2.7%——
20184153.7%31.7%4.9%2.4%7.3%——
20194047.5%32.5%10.0%2.5%7.5%——
20205846.5%34.5%8.6%5.2%5.2%——
20213063.3%30.0%—3.3%3.3%——
20225062.0%30.0%6.0%———2.0%
20236147.5%45.9%3.3%—3.3%——
20245646.4%39.3%5.4%3.6%3.6%—1.8%
20254148.8%31.7%9.8%—9.8%——
20263630.6%36.1%8.3%5.6%11.1%5.6%2.8%
The Average Call Waits 62 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 62 minutes in 2026, more than double what it was in 2016. 17% of calls took more than an hour to get a response in 2026, compared with 3% in 2016. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2009 and 2026 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each year is the number of events logged that year in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.