Home / States / California / Yucaipa Police Department
Yucaipa Police Department
City agency in San Bernardino, California, United States. This agency has no NIBRS start date on record. The FBI file does carry arrest counts for it, shown below; Police Census holds no crime counts or clearance rates for it.
- ORI
- CA036350X
- Type
- City
- County
- San Bernardino
- State
- California (CA)
- FBI reporting
- No NIBRS start date
No crime counts or clearance rates are published for this jurisdiction. Yucaipa Police Department has no National Incident-Based Reporting System start date on record, and Police Census holds no crime or clearance figures for it. The FBI file does carry arrest counts for this agency; they are shown below.
Workforce
As reported to the FBI for 2015, covering a population of 53,498.
| Year | Officers | Civilians | Population served | Per 1,000 |
|---|---|---|---|---|
| 2015 | 1 | 0 | 53,498 | 0.02 |
| 2014 | 1 | 0 | 52,794 | 0.02 |
| 2011 | 1 | 0 | 51,971 | 0.02 |
| 1998 | 0 | 0 | 37,006 | 0.00 |
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.
Arrests
Arrests made by Yucaipa Police Department, all offences combined, as filed with the FBI and added up by calendar year, 2019–2026.
| Year | Months filed | Arrests |
|---|---|---|
| 2026 | Not yet in the FBI’s file | |
| 2025 | 12 | 0 |
| 2024 | 12 | 0 |
| 2023 | 7 of 12 | 565 |
| 2022 | 12 | 1,286 |
| 2021 | Not reported | |
| 2020 | 12 | 901 |
| 2019 | 12 | 1,493 |
“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. A 0 is the figure as filed: the file does not distinguish an agency that made no arrests from one that did not submit them, and Police Census cannot either. Source: FBI Crime Data Explorer, arrest data for agency record CA036350X.
Bias-motivated incidents in the FBI’s file
1 incident appears in the FBI’s hate crime file for Yucaipa Police Department for 2020, as at 14 August 2026. The table lists every year from 1991 to 2025 for which the file has at least one.
| Year | Incidents appearing in the file |
|---|---|
| 2020 | 1 |
| 2018 | 1 |
| 2014 | 1 |
| 2012 | 1 |
| 2009 | 1 |
| 2006 | 1 |
| Bias motivation | Incidents |
|---|---|
| Anti-Black or African American | 2 |
| Anti-Gay (Male) | 1 |
| Anti-Hispanic or Latino | 1 |
| Anti-Lesbian, Gay, Bisexual, or Transgender (Mixed Group) | 1 |
| Anti-Other Religion | 1 |
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 CA036350X.
Assaults on officers
Officers of Yucaipa 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 reported | Officers assaulted |
|---|---|
| Firearm | 1 |
| Knife or other cutting instrument | 2 |
| Hands, fists or feet | 86 |
| Other weapon | 23 |
| Year | Firearm | Knife | Hands, fists, feet | Other |
|---|---|---|---|---|
| 1995 | 0 | 0 | 1 | 0 |
| 1996 | 0 | 0 | 1 | 0 |
| 1997 | 0 | 0 | 2 | 0 |
| 1998 | 0 | 1 | 2 | 0 |
| 1999 | 0 | 0 | 1 | 1 |
| 2000 | 0 | 0 | 1 | 0 |
| 2001 | 0 | 0 | 1 | 2 |
| 2002 | 0 | 0 | 2 | 0 |
| 2003 | 0 | 0 | 2 | 2 |
| 2004 | 0 | 0 | 2 | 3 |
| 2005 | 0 | 0 | 2 | 0 |
| 2008 | 0 | 0 | 1 | 0 |
| 2010 | 0 | 0 | 1 | 0 |
| 2011 | 0 | 0 | 1 | 0 |
| 2014 | 0 | 0 | 4 | 0 |
| 2015 | 0 | 0 | 2 | 0 |
| 2016 | 0 | 0 | 0 | 3 |
| 2017 | 0 | 0 | 5 | 1 |
| 2018 | 0 | 0 | 12 | 0 |
| 2019 | 0 | 0 | 8 | 2 |
| 2020 | 1 | 0 | 3 | 3 |
| 2022 | 0 | 1 | 9 | 2 |
| 2024 | 0 | 0 | 15 | 2 |
| 2025 | 0 | 0 | 8 | 2 |
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.
Also policing San Bernardino
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 CA036350X. 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.