PoliceCensus

Home / States / Arizona / Tucson Police Department

Tucson Police Department

City agency in Pima, Arizona, United States. Reports crime data to the FBI, and has done since 2024.

ORI
AZ0100300
Type
City
County
Pima
State
Arizona (AZ)
FBI reporting
Reporting since 2024-01-01
Location
32.2181, -110.9706

Workforce

As reported to the FBI for 2025, covering a population of 556,898.

755Sworn officers
443Civilian staff
2.15Employees per 1,000 people
556,898Population served
YearOfficersCiviliansPopulation servedPer 1,000
2025755443556,8982.15
2024732351548,7891.97
2023777366548,5442.08
2022777313544,6292.00
2021820239556,2971.90
2020855232550,4481.97
2019901228548,3742.06
2018807208537,3921.89
2017834340532,3232.21
2016870298533,6632.19
2015932290529,6752.31
2014934285527,3282.31

Officer and civilian counts are full-time employees as filed by the agency in its annual return. A dash means the agency did not report that figure for that year — it does not mean zero.

Crime and clearances

Offences and clearances filed by Tucson Police Department in its monthly returns to the FBI, added up by calendar year, 2019–2026. Violent crime and property crime are the FBI’s two categories. These are the counts as filed: Police Census does not turn them into a rate.

Violent crime
YearMonths filedOffencesClearedCleared as % of offences
20268 of 121,67281048.4%
2025122,0501,48172.2%
2024123,5441,36138.4%
2023122,59783132.0%
2022122,67585932.1%
2021Not reported
2020123,7801,10229.2%
2019123,77583922.2%
Property crime
YearMonths filedOffencesClearedCleared as % of offences
20268 of 127,0231,18916.9%
20251211,4701,93416.9%
20241218,9881,8159.6%
20231215,1641,4699.7%
20221215,5681,4309.2%
2021Not reported
20201220,1032,05510.2%
20191218,0851,3197.3%

Reading the table. “Not reported” means the agency filed nothing for that year; it does not mean zero. A 0 is a figure the agency filed. For 2026 the FBI is still collecting: that year is not complete in the file we read, so where this agency has no 2026 figures the table says “Not yet in the FBI’s file” rather than “Not reported”. We can see that the agency is absent from the file so far; we cannot tell whether it has not filed or has not yet been published, and we do not guess. A year marked “7 of 12” adds up only the months the agency filed, so it is not a full-year total. A dash in the last column means the percentage cannot be worked out: it needs both figures, and at least one offence.

“Cleared” is the FBI file’s clearance count for the year. Clearances in a year can relate to offences from earlier years, so the percentage is not the share of that year’s offences that were solved, and it can exceed 100%. Figures are not adjusted: a year far below the agency’s neighbouring years, or a 0 beside many offences, may reflect what was submitted rather than what happened. The file does not say which, and Police Census does not guess.

Source: FBI Crime Data Explorer, summarized data for agency record AZ0100300.

Arrests

Arrests made by Tucson Police Department, all offences combined, as filed with the FBI and added up by calendar year, 2019–2026.

YearMonths filedArrests
20268 of 129,773
20251215,660
20241214,608
20231217,199
20221216,003
2021Not reported
20201223,783
20191234,024

“Not reported” means the agency filed nothing for that year; it does not mean zero. A year marked “7 of 12” adds up only the months filed. For 2026 the FBI is still collecting, so an absent agency reads “Not yet in the FBI’s file”: absent from the file so far, which is not the same claim as having filed nothing. Source: FBI Crime Data Explorer, arrest data for agency record AZ0100300.

Bias-motivated incidents in the FBI’s file

3 incidents appear in the FBI’s hate crime file for Tucson Police Department for 2025, as at 14 August 2026. The table lists every year from 1991 to 2025 for which the file has at least one.

Incidents appearing in the FBI’s file, as at 14 August 2026
YearIncidents appearing in the file
20253
202414
20235
201916
201817
20175
20165
20154
20149
201326
201210
201014
200911
200813
200611
200527
200422
200328
200223
200147
200019
199939
199829
19976
19964
19955
199414
199325
19924
Bias motivation recorded, in the FBI’s words, 1992–2025
Bias motivationIncidents
Anti-Black or African American118
Anti-Gay (Male)74
Anti-Jewish68
Anti-Hispanic or Latino28
Anti-Islamic (Muslim)26
Anti-Other Race/Ethnicity/Ancestry25
Anti-Lesbian, Gay, Bisexual, or Transgender (Mixed Group)21
Anti-Multiple Races, Group21
Anti-Lesbian (Female)16
Anti-Other Religion15
Anti-White11
Anti-Catholic6
Anti-Asian5
Anti-Multiple Religions, Group3
Anti-Transgender3
Anti-Bisexual2
Anti-Mental Disability2
Anti-Other Christian2
Anti-Physical Disability2
Anti-Protestant2
Anti-American Indian or Alaska Native1
Anti-Arab1
Anti-Female1

2 of these incidents record more than one bias motivation. The FBI’s file stores those as a single list; each is shown here as its separate entries joined by “+”, and none is added to a line in the table above.

Absence from this file is not a zero. The file lists incidents that were reported to the FBI. An agency can be missing from it because it recorded none, because it did not report, or because it does not take part in the FBI’s hate crime program, and nothing Police Census holds can tell these apart. In any one year the file lists incidents for only a minority of the agencies the FBI counts as reporting.

The figures are counts of incidents as they appear in the file, as at 14 August 2026; Police Census does not turn them into a rate and does not compare them with other agencies. Offence and bias wording is the FBI’s own, unaltered. Source: FBI Crime Data Explorer, additional datasets, hate crime bulk file, agency record AZ0100300.

Deaths during encounters with this agency

115 people have died during an encounter with Tucson Police Department between 2000 and 2026, according to the two datasets named below.

115Deaths recorded
20.65Per 100,000 people policed
2000–2026Period covered
Recorded causeDeaths
Gunshot101
Vehicle6
Tasered3
Taser2
Physical Restraint1
Drug overdose1
Asphyxiated/Restrained1

What this figure is and is not. It counts deaths recorded as occurring during an encounter with this agency. It is not a finding of wrongdoing, and a death being recorded here says nothing about whether it was lawful. Many involve armed confrontations; some involve none. Police Census publishes counts only and does not name the people who died.

Source: these records come from Fatal Encounters (59) and Mapping Police Violence (56). Where both recorded the same death it is counted once. They are not official statistics, and no federal database records this comprehensively. See Deaths for how the two are combined. Mapping Police Violence data is displayed with attribution to its compiler; the written scope of this site’s right to display it is being confirmed (note dated 11 October 2026).

Assaults on officers

Officers of Tucson Police Department assaulted in the line of duty, by the weapon reported, between 1995 and 2025. These are the FBI’s own weapon categories.

Weapon reportedOfficers assaulted
Firearm172
Knife or other cutting instrument100
Hands, fists or feet1,828
Other weapon767
YearFirearmKnifeHands, fists, feetOther
1995855717
1996866622
1997736124
1998735821
1999824827
2000435921
2001864919
2002944025
2003734327
2004825125
2005424218
2006313718
2007314813
2008714416
2009314910
201032514
2011214612
2012305214
2013644125
2014233630
2015532831
2016133635
2017332932
2018652127
2019652637
2020642928
2022534019
2023635918
202410924753
202514933599

Why there is no single total here. The FBI publishes two breakdowns of the same assaults — by weapon, and by how the officer was deployed — and nationally they do not agree: the assignment columns sum to 1,869,337 and the weapon columns to 1,744,852, and the two match on only 84% of rows. Police Census publishes the weapon breakdown as the FBI states it rather than picking one basis and calling it ‘the total’. The file’s ‘cleared’ column is not shown either: it sums higher than the assaults themselves, so it is not a subset of what is above and we have not established what it counts.

This comes from the FBI’s Law Enforcement Officers Killed and Assaulted programme. Despite the name, the file carries no officers-killed data at all — those columns are empty for every agency and every year, so this page reports assaults only and says nothing about officers killed.

LEOKA identifies agencies by name, not by the ORI used elsewhere on this site. A row was attached only where exactly one agency in that state reduces to the same base name; 78.7% of rows matched nationwide. An agency with nothing here may have reported no assaults, or may be one of the names that did not match — Police Census does not guess which.

Military surplus received

Transferred under the Department of Defense 1033 programme, which passes surplus military equipment to law enforcement agencies at no cost. Values are the Department’s original acquisition cost, not what the equipment is worth today.

$746,613Original acquisition value
74Line items received
2000–2026Years of transfers
ItemQuantityAcquisition valueMost recent
Truck,Utility7$392,6482012-05-22
Image Intensifier,Night Vision52$344,4982008-05-22
Detecting Set,Mine2$4,9002026-02-11
Goggles,Nightvisio1$2,7482014-01-15
Rifle,7.62 Millimeter10$1,3802000-07-14
Sight,Reflex1$3392012-10-10
Shipping Case4$1002026-06-17

Source: Defense Logistics Agency, Law Enforcement Support Office, public data as at 30 June 2026. Items are grouped by description; the date shown is the most recent shipment of that item.

Also policing Pima

Jurisdictions overlap. These agencies are also recorded against the same county, so a single address may be covered by more than one of them.

Source

Agency identity, type, jurisdiction, coordinates and reporting status are as published by the FBI Crime Data Explorer, agency record AZ0100300. Police Census reproduces these values without adjustment. Where the FBI publishes nothing, this page says so rather than estimating.

Believe something on this page is wrong? Tell us at corrections@policecensus.com — every correction is published on Corrections.