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

Escape/Eluding Police

Escape/Eluding Police calls over time: volume, outcomes, and response speed

Escape/Eluding Police: 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 (94% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
015302009: 7 escape/eluding police calls logged in CAD2010: 10 escape/eluding police calls logged in CAD2011: 9 escape/eluding police calls logged in CAD2012: 15 escape/eluding police calls logged in CAD2013: 10 escape/eluding police calls logged in CAD2014: 6 escape/eluding police calls logged in CAD2015: 8 escape/eluding police calls logged in CAD2016: 8 escape/eluding police calls logged in CAD2017: 5 escape/eluding police calls logged in CAD2018: 14 escape/eluding police calls logged in CAD2019: 7 escape/eluding police calls logged in CAD2020: 4 escape/eluding police calls logged in CAD2021: 5 escape/eluding police calls logged in CAD2022: 18 escape/eluding police calls logged in CAD2023: 20 escape/eluding police calls logged in CAD2024: 25 escape/eluding police calls logged in CAD2025: 10 escape/eluding police calls logged in CAD2026: 7 escape/eluding police calls logged in CAD2009n=72011n=92013n=102015n=82017n=52019n=72021n=52023n=202025n=102026n=7
escape/eluding police calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodEscape/eluding police calls logged in CAD
20097
201010
20119
201215
201310
20146
20158
20168
20175
201814
20197
20204
20215
202218
202320
202425
202510
20267
Escape/Eluding Police Calls Average About 11 a YearSeattle Police logged 188 escape/eluding police calls between 2009 and 2026, with a high of 25 in 2024.

Escape/Eluding Police: 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 · Report taken, no arrest: 28.6%2009 · Unable to locate: 14.3%2009 · Other (unfounded / cancelled): 57.1%2010 · Report taken, no arrest: 10.0%2010 · Other (unfounded / cancelled): 90.0%2011 · Arrest / citation: 11.1%2011 · Report taken, no arrest: 22.2%2011 · Other (unfounded / cancelled): 66.7%2012 · Other (unfounded / cancelled): 100.0%2013 · Other (unfounded / cancelled): 100.0%2014 · Other (unfounded / cancelled): 100.0%2015 · Other (unfounded / cancelled): 100.0%2016 · Other (unfounded / cancelled): 100.0%2017 · Other (unfounded / cancelled): 100.0%2018 · Report taken, no arrest: 7.1%2018 · Other (unfounded / cancelled): 92.9%2019 · Report taken, no arrest: 28.6%2019 · Resolved on scene: 14.3%2019 · Other (unfounded / cancelled): 57.1%2020 · Other (unfounded / cancelled): 100.0%2021 · Other (unfounded / cancelled): 100.0%2022 · Report taken, no arrest: 5.6%2022 · Other (unfounded / cancelled): 94.4%2023 · Report taken, no arrest: 20.0%2023 · Other (unfounded / cancelled): 80.0%2024 · Report taken, no arrest: 8.0%2024 · Unable to locate: 4.0%2024 · Other (unfounded / cancelled): 88.0%2025 · Other (unfounded / cancelled): 100.0%2026 · Arrest / citation: 14.3%2026 · Resolved on scene: 14.3%2026 · Other (unfounded / cancelled): 71.4%2009n=72011n=92013n=102015n=82017n=52019n=72021n=52023n=202025n=102026n=7
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
PeriodEventsReport taken, no arrestUnable to locateOther (unfounded / cancelled)Arrest / citationResolved on scene
2009728.6%14.3%57.1%——
20101010.0%—90.0%——
2011922.2%—66.7%11.1%—
201215——100.0%——
201310——100.0%——
20146——100.0%——
20158——100.0%——
20168——100.0%——
20175——100.0%——
2018147.1%—92.9%——
2019728.6%—57.1%—14.3%
20204——100.0%——
20215——100.0%——
2022185.6%—94.4%——
20232020.0%—80.0%——
2024258.0%4.0%88.0%——
202510——100.0%——
20267——71.4%14.3%14.3%
1% of Escape/Eluding Police Calls End “Unable to Locate”Across 2009 to 2026, report-taken outcomes were 8% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Escape/Eluding Police: 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 94% of escape/eluding police 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 escape/eluding police 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 min125 min250 min2009: 1.3 min2012: 203.5 min2016: 0.7 min2018: 8.5 min2019: 2.9 min2022: 7.7 min2023: 131.5 min2024: 0.8 min2026: 2.9 min2009: 7.8 min2016: 9.2 min2018: 13.8 min2019: 7.2 min2022: 17.0 min2023: 13.4 min2024: 8.7 min2026: 7.2 min2009n=12011n=02013n=02015n=02017n=02019n=22021n=02023n=22025n=02026n=1
Average response timeAverage dispatch delay
Small sample: Only a small share of escape/eluding police events are called in. The year with the fewest had only 1, 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
200911.3 min7.8 min
20100——
20110——
20121203.5 min—
20130——
20140——
20150——
201610.7 min9.2 min
20170——
201818.5 min13.8 min
201922.9 min7.2 min
20200——
20210——
202217.7 min17.0 min
20232131.5 min13.4 min
202410.8 min8.7 min
20250——
202612.9 min7.2 min
Called-In Events Waited 7.2 Minutes on Average in 2026That is the average across 1 called-in events in 2026. Counts this small can swing a lot from year to year.
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.

Escape/Eluding Police: 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 94% of escape/eluding police events, because they have no wait. Because most escape/eluding police 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 · 5–30 min: 100.0%2012 · No recorded response: 100.0%2016 · 5–30 min: 100.0%2018 · 5–30 min: 100.0%2019 · No recorded response: 50.0%2019 · 5–30 min: 50.0%2022 · 5–30 min: 100.0%2023 · No recorded response: 50.0%2023 · 5–30 min: 50.0%2024 · 5–30 min: 100.0%2026 · 5–30 min: 100.0%2009n=12011n=02013n=02015n=02017n=02019n=22021n=02023n=22025n=02026n=1
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of escape/eluding police events are called in. The year with the fewest had only 1, 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 events5–30 minNo recorded response
20091100.0%—
20100——
20110——
20121—100.0%
20130——
20140——
20150——
20161100.0%—
20170——
20181100.0%—
2019250.0%50.0%
20200——
20210——
20221100.0%—
2023250.0%50.0%
20241100.0%—
20250——
20261100.0%—
0% of Called-In Events Took Over an Hour in 2026That is 0% of 1 called-in events. Counts this small can swing a lot from year to year.
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.