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

Casualty (Non-Traffic, Non-Criminal, including Man Down, Injured & Sick Person, DOA)

Casualty (Non-Traffic, Non-Criminal, including Man Down, Injured & Sick Person, DOA) calls over time: volume, outcomes, and response speed

Casualty: 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 (18% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
01,5003,0002009: 1,565 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2010: 2,329 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2011: 2,301 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2012: 2,366 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2013: 2,353 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2014: 2,195 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2015: 2,142 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2016: 2,017 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2017: 1,867 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2018: 1,595 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2019: 1,567 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2020: 1,375 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2021: 1,640 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2022: 1,994 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2023: 2,256 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2024: 1,966 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2025: 1,858 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2026: 1,460 casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD2009n=1,5652011n=2,3012013n=2,3532015n=2,1422017n=1,8672019n=1,5672021n=1,6402023n=2,2562025n=1,8582026n=1,460
casualty (non-traffic, non-criminal, including man down, injured & sick person, doa) calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodCasualty calls logged in CAD
20091,565
20102,329
20112,301
20122,366
20132,353
20142,195
20152,142
20162,017
20171,867
20181,595
20191,567
20201,375
20211,640
20221,994
20232,256
20241,966
20251,858
20261,460
Casualty Calls Are Down 21% From Their 2012 PeakSeattle Police logged 2,366 casualty calls in 2012 and 1,858 in 2025, the most recent full year.

Casualty: 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: 0.6%2009 · Report taken, no arrest: 39.7%2009 · Resolved on scene: 51.9%2009 · Unable to locate: 4.5%2009 · Other (unfounded / cancelled): 3.3%2010 · Arrest / citation: 0.3%2010 · Report taken, no arrest: 43.4%2010 · Resolved on scene: 49.0%2010 · Unable to locate: 4.5%2010 · Other (unfounded / cancelled): 2.8%2011 · Arrest / citation: 0.3%2011 · Report taken, no arrest: 46.8%2011 · Resolved on scene: 45.8%2011 · Unable to locate: 3.5%2011 · Other (unfounded / cancelled): 3.6%2012 · Arrest / citation: 0.2%2012 · Report taken, no arrest: 44.5%2012 · Resolved on scene: 47.0%2012 · Unable to locate: 4.8%2012 · Other (unfounded / cancelled): 3.6%2013 · Arrest / citation: 0.1%2013 · Report taken, no arrest: 45.4%2013 · Resolved on scene: 45.1%2013 · Unable to locate: 5.5%2013 · Other (unfounded / cancelled): 3.9%2014 · Arrest / citation: 0.2%2014 · Report taken, no arrest: 46.7%2014 · Resolved on scene: 43.3%2014 · Unable to locate: 4.8%2014 · Other (unfounded / cancelled): 5.0%2015 · Arrest / citation: 0.1%2015 · Report taken, no arrest: 45.9%2015 · Resolved on scene: 44.1%2015 · Unable to locate: 5.6%2015 · Other (unfounded / cancelled): 4.3%2016 · Report taken, no arrest: 47.4%2016 · Resolved on scene: 41.2%2016 · Unable to locate: 5.1%2016 · Other (unfounded / cancelled): 6.3%2017 · Arrest / citation: 0.3%2017 · Report taken, no arrest: 52.4%2017 · Resolved on scene: 35.5%2017 · Unable to locate: 3.4%2017 · Other (unfounded / cancelled): 8.5%2018 · Report taken, no arrest: 57.1%2018 · Resolved on scene: 32.9%2018 · Unable to locate: 3.5%2018 · Other (unfounded / cancelled): 6.6%2019 · Report taken, no arrest: 63.3%2019 · Resolved on scene: 26.5%2019 · Unable to locate: 3.3%2019 · Other (unfounded / cancelled): 6.8%2020 · Report taken, no arrest: 73.3%2020 · Resolved on scene: 18.6%2020 · Unable to locate: 3.3%2020 · Other (unfounded / cancelled): 4.8%2021 · Report taken, no arrest: 77.0%2021 · Resolved on scene: 15.1%2021 · Unable to locate: 3.2%2021 · Other (unfounded / cancelled): 4.7%2022 · Arrest / citation: 0.2%2022 · Report taken, no arrest: 70.8%2022 · Resolved on scene: 21.6%2022 · Unable to locate: 3.6%2022 · Other (unfounded / cancelled): 3.9%2023 · Report taken, no arrest: 66.6%2023 · Resolved on scene: 20.4%2023 · Unable to locate: 5.5%2023 · Other (unfounded / cancelled): 7.4%2024 · Arrest / citation: 0.1%2024 · Report taken, no arrest: 67.0%2024 · Resolved on scene: 20.0%2024 · Unable to locate: 6.2%2024 · Other (unfounded / cancelled): 6.7%2025 · Report taken, no arrest: 65.3%2025 · Resolved on scene: 19.9%2025 · Unable to locate: 6.6%2025 · Other (unfounded / cancelled): 8.3%2026 · Arrest / citation: 0.1%2026 · Report taken, no arrest: 55.1%2026 · Resolved on scene: 28.8%2026 · Unable to locate: 10.3%2026 · Other (unfounded / cancelled): 5.7%2009n=1,5652011n=2,3012013n=2,3532015n=2,1422017n=1,8672019n=1,5672021n=1,6402023n=2,2562025n=1,8582026n=1,460
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)
20091,5650.6%39.7%51.9%4.5%3.3%
20102,3290.3%43.4%49.0%4.5%2.8%
20112,3010.3%46.8%45.8%3.5%3.6%
20122,3660.2%44.5%47.0%4.8%3.6%
20132,3530.1%45.4%45.1%5.5%3.9%
20142,1950.2%46.7%43.3%4.8%5.0%
20152,1420.1%45.9%44.1%5.6%4.3%
20162,017—47.4%41.2%5.1%6.3%
20171,8670.3%52.4%35.5%3.4%8.5%
20181,595—57.1%32.9%3.5%6.6%
20191,567—63.3%26.5%3.3%6.8%
20201,375—73.3%18.6%3.3%4.8%
20211,640—77.0%15.1%3.2%4.7%
20221,9940.2%70.8%21.6%3.6%3.9%
20232,256—66.6%20.4%5.5%7.4%
20241,9660.1%67.0%20.0%6.2%6.7%
20251,858—65.3%19.9%6.6%8.3%
20261,4600.1%55.1%28.8%10.3%5.7%
10% of Casualty Calls End “Unable to Locate,” Up From 5%Report-taken outcomes moved from 47% of calls in 2016 to 55% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Casualty: 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 18% of casualty 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. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min25 min50 min2009: 7.3 min2010: 5.9 min2011: 5.7 min2012: 5.7 min2013: 7.9 min2014: 10.4 min2015: 11.1 min2016: 8.0 min2017: 4.4 min2018: 5.2 min2019: 7.5 min2020: 6.5 min2021: 8.4 min2022: 10.2 min2023: 9.6 min2024: 19.5 min2025: 24.5 min2026: 18.7 min2009: 14.7 min2010: 13.0 min2011: 13.1 min2012: 13.7 min2013: 15.4 min2014: 18.7 min2015: 19.9 min2016: 17.0 min2017: 12.6 min2018: 14.4 min2019: 16.4 min2020: 17.4 min2021: 19.8 min2022: 20.1 min2023: 20.4 min2024: 30.3 min2025: 37.9 min2026: 29.1 min2009n=1,1202011n=1,7112013n=1,7742015n=1,5932017n=1,4852019n=1,3622021n=1,5362023n=2,0792025n=1,7392026n=1,379
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20091,1207.3 min14.7 min
20101,6855.9 min13.0 min
20111,7115.7 min13.1 min
20121,7395.7 min13.7 min
20131,7747.9 min15.4 min
20141,64510.4 min18.7 min
20151,59311.1 min19.9 min
20161,4928.0 min17.0 min
20171,4854.4 min12.6 min
20181,3105.2 min14.4 min
20191,3627.5 min16.4 min
20201,2496.5 min17.4 min
20211,5368.4 min19.8 min
20221,76610.2 min20.1 min
20232,0799.6 min20.4 min
20241,80919.5 min30.3 min
20251,73924.5 min37.9 min
20261,37918.7 min29.1 min
The Average Call Waits 29 Minutes for an Officer to ArriveDespite an 8% drop in calls between 2016 and 2025, average response time has increased 71% in the past 10 years, from 17 minutes in 2016 to 29 in 2026, driven largely by dispatch delays.
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.

Casualty: 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 18% of casualty events, because they have no wait. 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 · No recorded response: 4.4%2009 · 0–5 min: 23.7%2009 · 5–30 min: 63.2%2009 · 30–60 min: 5.2%2009 · 1–4 hr: 3.3%2009 · 4–8 hr: 0.3%2010 · No recorded response: 3.6%2010 · 0–5 min: 27.5%2010 · 5–30 min: 60.7%2010 · 30–60 min: 5.6%2010 · 1–4 hr: 2.5%2010 · 4–8 hr: 0.1%2011 · No recorded response: 4.8%2011 · 0–5 min: 25.0%2011 · 5–30 min: 61.9%2011 · 30–60 min: 5.9%2011 · 1–4 hr: 2.3%2012 · No recorded response: 5.0%2012 · 0–5 min: 23.6%2012 · 5–30 min: 63.8%2012 · 30–60 min: 4.8%2012 · 1–4 hr: 2.8%2012 · 4–8 hr: 0.1%2013 · No recorded response: 5.0%2013 · 0–5 min: 25.1%2013 · 5–30 min: 62.2%2013 · 30–60 min: 5.0%2013 · 1–4 hr: 2.2%2013 · 4–8 hr: 0.3%2013 · Over 8 hr: 0.2%2014 · No recorded response: 5.2%2014 · 0–5 min: 20.9%2014 · 5–30 min: 64.2%2014 · 30–60 min: 6.2%2014 · 1–4 hr: 3.2%2014 · 4–8 hr: 0.2%2014 · Over 8 hr: 0.1%2015 · No recorded response: 5.5%2015 · 0–5 min: 17.8%2015 · 5–30 min: 65.2%2015 · 30–60 min: 6.5%2015 · 1–4 hr: 4.6%2015 · 4–8 hr: 0.3%2015 · Over 8 hr: 0.2%2016 · No recorded response: 7.2%2016 · 0–5 min: 20.6%2016 · 5–30 min: 63.9%2016 · 30–60 min: 4.7%2016 · 1–4 hr: 3.1%2016 · 4–8 hr: 0.4%2016 · Over 8 hr: 0.1%2017 · No recorded response: 8.5%2017 · 0–5 min: 23.9%2017 · 5–30 min: 62.1%2017 · 30–60 min: 3.6%2017 · 1–4 hr: 1.9%2017 · 4–8 hr: 0.1%2018 · No recorded response: 6.6%2018 · 0–5 min: 22.1%2018 · 5–30 min: 63.8%2018 · 30–60 min: 4.8%2018 · 1–4 hr: 2.6%2018 · 4–8 hr: 0.1%2019 · No recorded response: 6.8%2019 · 0–5 min: 20.5%2019 · 5–30 min: 64.9%2019 · 30–60 min: 4.3%2019 · 1–4 hr: 3.0%2019 · 4–8 hr: 0.4%2019 · Over 8 hr: 0.1%2020 · No recorded response: 4.6%2020 · 0–5 min: 16.8%2020 · 5–30 min: 70.0%2020 · 30–60 min: 5.4%2020 · 1–4 hr: 2.7%2020 · 4–8 hr: 0.2%2020 · Over 8 hr: 0.2%2021 · No recorded response: 4.6%2021 · 0–5 min: 13.9%2021 · 5–30 min: 69.9%2021 · 30–60 min: 7.4%2021 · 1–4 hr: 3.8%2021 · 4–8 hr: 0.5%2022 · No recorded response: 4.4%2022 · 0–5 min: 18.2%2022 · 5–30 min: 65.9%2022 · 30–60 min: 7.4%2022 · 1–4 hr: 3.3%2022 · 4–8 hr: 0.7%2022 · Over 8 hr: 0.1%2023 · No recorded response: 7.7%2023 · 0–5 min: 19.7%2023 · 5–30 min: 63.0%2023 · 30–60 min: 4.7%2023 · 1–4 hr: 4.0%2023 · 4–8 hr: 0.7%2023 · Over 8 hr: 0.1%2024 · No recorded response: 6.7%2024 · 0–5 min: 14.3%2024 · 5–30 min: 59.9%2024 · 30–60 min: 9.1%2024 · 1–4 hr: 8.5%2024 · 4–8 hr: 1.1%2024 · Over 8 hr: 0.4%2025 · No recorded response: 6.8%2025 · 0–5 min: 13.7%2025 · 5–30 min: 54.3%2025 · 30–60 min: 10.6%2025 · 1–4 hr: 12.7%2025 · 4–8 hr: 1.3%2025 · Over 8 hr: 0.6%2026 · No recorded response: 6.3%2026 · 0–5 min: 13.1%2026 · 5–30 min: 58.9%2026 · 30–60 min: 11.6%2026 · 1–4 hr: 9.3%2026 · 4–8 hr: 0.6%2026 · Over 8 hr: 0.3%2009n=1,1202011n=1,7112013n=1,7742015n=1,5932017n=1,4852019n=1,3622021n=1,5362023n=2,0792025n=1,7392026n=1,379
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
20091,1204.4%23.7%63.2%5.2%3.3%0.3%—
20101,6853.6%27.5%60.7%5.6%2.5%0.1%—
20111,7114.8%25.0%61.9%5.9%2.3%——
20121,7395.0%23.6%63.8%4.8%2.8%0.1%—
20131,7745.0%25.1%62.2%5.0%2.2%0.3%0.2%
20141,6455.2%20.9%64.2%6.2%3.2%0.2%0.1%
20151,5935.5%17.8%65.2%6.5%4.6%0.3%0.2%
20161,4927.2%20.6%63.9%4.7%3.1%0.4%0.1%
20171,4858.5%23.9%62.1%3.6%1.9%0.1%—
20181,3106.6%22.1%63.8%4.8%2.6%0.1%—
20191,3626.8%20.5%64.9%4.3%3.0%0.4%0.1%
20201,2494.6%16.8%70.0%5.4%2.7%0.2%0.2%
20211,5364.6%13.9%69.9%7.4%3.8%0.5%—
20221,7664.4%18.2%65.9%7.4%3.3%0.7%0.1%
20232,0797.7%19.7%63.0%4.7%4.0%0.7%0.1%
20241,8096.7%14.3%59.9%9.1%8.5%1.1%0.4%
20251,7396.8%13.7%54.3%10.6%12.7%1.3%0.6%
20261,3796.3%13.1%58.9%11.6%9.3%0.6%0.3%
The Average Call Waits 19 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 19 minutes in 2026, more than double what it was in 2016. 10% of calls took more than an hour to get a response in 2026, compared with 4% in 2016.
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.