Sadly, the trend of fatal police shootings in the United States seems to only be increasing, with a total 1,173 civilians having been shot, 248 of whom were Black, as of December 2024. In 2023, there were 1,164 fatal police shootings. Additionally, the rate of fatal police shootings among Black Americans was much higher than that for any other ethnicity, standing at 6.1 fatal shootings per million of the population per year between 2015 and 2024. Police brutality in the U.S. In recent years, particularly since the fatal shooting of Michael Brown in Ferguson, Missouri in 2014, police brutality has become a hot button issue in the United States. The number of homicides committed by police in the United States is often compared to those in countries such as England, where the number is significantly lower. Black Lives Matter The Black Lives Matter Movement, formed in 2013, has been a vocal part of the movement against police brutality in the U.S. by organizing “die-ins”, marches, and demonstrations in response to the killings of black men and women by police. While Black Lives Matter has become a controversial movement within the U.S., it has brought more attention to the number and frequency of police shootings of civilians.

As of November 17, 277 Black people were killed by the police in the United States in 2024. This compares to 201 Hispanic people and 445 white people. The rate of police shootings of Black Americans is much higher than any other ethnicity, at 6.2 per million people. This rate stands at 2.8 per million for Hispanic people and 2.4 per million for white people.

A geographically-resolved, multi-level Bayesian model is used to analyze the data presented in the U.S. Police-Shooting Database (USPSD) in order to investigate the extent of racial bias in the shooting of American civilians by police officers in recent years. In contrast to previous work that relied on the FBI’s Supplemental Homicide Reports that were constructed from self-reported cases of police-involved homicide, this data set is less likely to be biased by police reporting practices. County-specific relative risk outcomes of being shot by police are estimated as a function of the interaction of: 1) whether suspects/civilians were armed or unarmed, and 2) the race/ethnicity of the suspects/civilians. The results provide evidence of a significant bias in the killing of unarmed black Americans relative to unarmed white Americans, in that the probability of being {black, unarmed, and shot by police} is about 3.49 times the probability of being {white, unarmed, and shot by police} on average. Furthermore, the results of multi-level modeling show that there exists significant heterogeneity across counties in the extent of racial bias in police shootings, with some counties showing relative risk ratios of 20 to 1 or more. Finally, analysis of police shooting data as a function of county-level predictors suggests that racial bias in police shootings is most likely to emerge in police departments in larger metropolitan counties with low median incomes and a sizable portion of black residents, especially when there is high financial inequality in that county. There is no relationship between county-level racial bias in police shootings and crime rates (even race-specific crime rates), meaning that the racial bias observed in police shootings in this data set is not explainable as a response to local-level crime rates.

The rate of fatal police shootings in the United States shows large differences based on ethnicity. Among Black Americans, the rate of fatal police shootings between 2015 and December 2024 stood at 6.1 per million of the population per year, while for white Americans, the rate stood at 2.4 fatal police shootings per million of the population per year. Police brutality in the United States Police brutality is a major issue in the United States, but recently saw a spike in online awareness and protests following the murder of George Floyd, an African American who was killed by a Minneapolis police officer. Just a few months before, Breonna Taylor was fatally shot in her apartment when Louisville police officers forced entry into her apartment. Despite the repeated fatal police shootings across the country, police accountability has not been adequate according to many Americans. A majority of Black Americans thought that police officers were not held accountable for their misconduct, while less than half of White Americans thought the same. Political opinions Not only are there differences in opinion between ethnicities on police brutality, but there are also major differences between political parties. A majority of Democrats in the United States thought that police officers were not held accountable for their misconduct, while a majority of Republicans that they were held accountable. Despite opposing views on police accountability, both Democrats and Republicans agree that police should be required to be trained in nonviolent alternatives to deadly force.

The study was a comprehensive analysis of felonious killings of officers. The purposes of the study were (1) to analyze the nature and circumstances of incidents of felonious police killings and (2) to analyze trends in the numbers and rates of killings across different types of agencies and to explain these differences. For Part 1, Incident-Level Data, an incident-level database was created to capture all incidents involving the death of a police officer from 1983 through 1992. Data on officers and incidents were collected from the Law Enforcement Officers Killed and Assaulted (LEOKA) data collection as coded by the Uniform Crime Reporting (UCR) program. In addition to the UCR data, the Police Foundation also coded information from the LEOKA narratives that are not part of the computerized LEOKA database from the FBI. For Part 2, Agency-Level Data, the researchers created an agency-level database to research systematic differences among rates at which law enforcement officers had been feloniously killed from 1977 through 1992. The investigators focused on the 56 largest law enforcement agencies because of the availability of data for explanatory variables. Variables in Part 1 include year of killing, involvement of other officers, if the officer was killed with his/her own weapon, circumstances of the killing, location of fatal wounds, distance between officer and offender, if the victim was wearing body armor, if different officers were killed in the same incident, if the officer was in uniform, actions of the killer and of the officer at entry and final stage, if the killer was visible at first, if the officer thought the killer was a felon suspect, if the officer was shot at entry, and circumstances at anticipation, entry, and final stages. Demographic variables for Part 1 include victim's sex, age, race, type of assignment, rank, years of experience, agency, population group, and if the officer was working a security job. Part 2 contains variables describing the general municipal environment, such as whether the agency is located in the South, level of poverty according to a poverty index, population density, percent of population that was Hispanic or Black, and population aged 15-34 years old. Variables capturing the crime environment include the violent crime rate, property crime rate, and a gun-related crime index. Lastly, variables on the environment of the police agencies include violent and property crime arrests per 1,000 sworn officers, percentage of officers injured in assaults, and number of sworn officers.

These data provide information on the number of arrests reported to the Federal Bureau of Investigation's (FBI) Uniform Crime Reporting (UCR) Program each month by police agencies in the United States. Although not as well known as the "Crimes Known to the Police" data drawn from the Uniform Crime Report's Return A form, the arrest reports by age, sex, and race provide valuable data on 44 offenses including violent, drug, gambling, and larceny crimes. The data received by ICPSR were structured as a hierarchical file containing (per reporting police agency) an agency header record, and 1 to 12 monthly header reports, and 1 to 43 detail offense records containing the counts of arrests by age, sex, and race for a particular offense. ICPSR restructured the original data to a rectangular format.

In 2023, the FBI reported that there were 9,284 Black murder victims in the United States and 7,289 white murder victims. In comparison, there were 554 murder victims of unknown race and 586 victims of another race. Victims of inequality? In recent years, the role of racial inequality in violent crimes such as robberies, assaults, and homicides has gained public attention. In particular, the issue of police brutality has led to increasing attention following the murder of George Floyd, an African American who was killed by a Minneapolis police officer. Studies show that the rate of fatal police shootings for Black Americans was more than double the rate reported of other races. Crime reporting National crime data in the United States is based off the Federal Bureau of Investigation’s new crime reporting system, which requires law enforcement agencies to self-report their data in detail. Due to the recent implementation of this system, less crime data has been reported, with some states such as Delaware and Pennsylvania declining to report any data to the FBI at all in the last few years, suggesting that the Bureau's data may not fully reflect accurate information on crime in the United States.

This dataset contains aggregate data on violent index victimizations at the quarter level of each year (i.e., January – March, April – June, July – September, October – December), from 2001 to the present (1991 to present for Homicides), with a focus on those related to gun violence. Index crimes are 10 crime types selected by the FBI (codes 1-4) for special focus due to their seriousness and frequency. This dataset includes only those index crimes that involve bodily harm or the threat of bodily harm and are reported to the Chicago Police Department (CPD). Each row is aggregated up to victimization type, age group, sex, race, and whether the victimization was domestic-related. Aggregating at the quarter level provides large enough blocks of incidents to protect anonymity while allowing the end user to observe inter-year and intra-year variation. Any row where there were fewer than three incidents during a given quarter has been deleted to help prevent re-identification of victims. For example, if there were three domestic criminal sexual assaults during January to March 2020, all victims associated with those incidents have been removed from this dataset. Human trafficking victimizations have been aggregated separately due to the extremely small number of victimizations.

This dataset includes a " GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized dataset, but with "UNKNOWN" in the shooting column.

The dataset is refreshed daily, but excludes the most recent complete day to allow CPD time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.

How does this dataset classify victims?

The methodology by which this dataset classifies victims of violent crime differs by victimization type:

Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.

To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset.

For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset do not align with the homicide/non-fatal shooting categorization:

1. In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a first-degree murder (IUCR code = 0110) or a second-degree murder (IUCR code = 0130).
2. When a non-fatal shooting victimization does not correspond to an IUCR code that signifies a criminal sexual assault, robbery, or aggravated battery, we enter “UNK” in the IUCR column, “YES” in the GUNSHOT_I column, and “NON-FATAL” in the PRIMARY column to indicate that the victim was non-fatally shot, but the precise IUCR code is unknown.

Other violent crime victims: For other violent crime types, we refer to the IUCR classification that exists in CPD's victim table, with only one exception:

1. When there is an incident that is associated with no victim with a matching IUCR code, we assume that this is an error. Every crime should have at least 1 victim with a matching IUCR code. In these cases, we change the IUCR code to reflect the incident IUCR code because CPD's incident table is considered to be more reliable than the victim table.

Note: All businesses identified as victims in CPD data have been removed from this dataset.

Note: The definition of “homicide” (shooting or otherwise) does not include justifiable homicide or involuntary manslaughter. This dataset also excludes any cases that CPD considers to be “unfounded” or “noncriminal.”

Note: In some instances, the police department's raw incident-level data and victim-level data that were inputs into this dataset do not align on the type of crime that occurred. In those instances, this dataset attempts to correct mismatches between incident and victim specific crime types. When it is not possible to determine which victims are associated with the most recent crime determination, the dataset will show empty cells in the respective demographic fields (age, sex, race, etc.).

Note: The initial reporting officer usually asks victims to report demographic data. If victims are unable to recall, the reporting officer will use their best judgment. “Unknown” can be reported if it is truly unknown.

Investigator(s): Federal Bureau of Investigation Since 1930, the Federal Bureau of Investigation (FBI) has compiled the Uniform Crime Reports (UCR) to serve as periodic nationwide assessments of reported crimes not available elsewhere in the criminal justice system. With the 1977 data, the title was expanded to Uniform Crime Reporting Program Data. Each year, participating law enforcement agencies contribute reports to the FBI either directly or through their state reporting programs. ICPSR archives the UCR data as five separate components: (1) summary data, (2) county-level data, (3) incident-level data (National Incident-Based Reporting System [NIBRS]), (4) hate crime data, and (5) various, mostly nonrecurring, data collections. Summary data are reported in four types of files: (a) Offenses Known and Clearances by Arrest, (b) Property Stolen and Recovered, (c) Supplementary Homicide Reports (SHR), and (d) Police Employee (LEOKA) Data (Law Enforcement Officers Killed or Assaulted). The county-level data provide counts of arrests and offenses aggregated to the county level. County populations are also reported. In the late 1970s, new ways to look at crime were studied. The UCR program was subsequently expanded to capture incident-level data with the implementation of the National Incident-Based Reporting System. The NIBRS data focus on various aspects of a crime incident. The gathering of hate crime data by the UCR program was begun in 1990. Hate crimes are defined as crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity. In September 1994, disabilities, both physical and mental, were added to the list. The fifth component of ICPSR's UCR holdings is comprised of various collections, many of which are nonrecurring and prepared by individual researchers. These collections go beyond the scope of the standard UCR collections provided by the FBI, either by including data for a range of years or by focusing on other aspects of analysis. NACJD has produced resource guides on UCR and on NIBRS data.

About this dataset

The Washington Post compiled a dataset of every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

In 2015, The Post began tracking more than a dozen details about each killing by culling local news reports, law enforcement websites and social media and by monitoring independent databases such as Killed by Police and Fatal Encounters. The available features are: - Race of the deceased; - Circumstances of the shooting; - Whether the person was armed; - Whether the victim was experiencing a mental-health crisis; - Among others.

In 2016, The Post is gathering additional information about each fatal shooting that occurs this year and is filing open-records requests with departments. More than a dozen additional details are being collected about officers in each shooting.

The Post is documenting only those shootings in which a police officer, in the line of duty, shot and killed a civilian — the circumstances that most closely parallel the 2014 killing of Michael Brown in Ferguson, Mo., which began the protest movement culminating in Black Lives Matter and an increased focus on police accountability nationwide. The Post is not tracking deaths of people in police custody, fatal shootings by off-duty officers or non-shooting deaths.

The FBI and the Centers for Disease Control and Prevention log fatal shootings by police, but officials acknowledge that their data is incomplete. In 2015, The Post documented more than two times more fatal shootings by police than had been recorded by the FBI. Last year, the FBI announced plans to overhaul how it tracks fatal police encounters.

How to use this dataset

• Understanding US Police Shootings by Curtis Thompson
• Dataset Questions and Suggestions
• More datasets

Acknowledgements

If you use this dataset in your research, please credit the authors.

BibTeX

@misc{wapo-police-shootings-bot , author = {The Washington Post}, title = {data-police-shootings}, month = jan, year = 2015, publisher = {Github}, url = {https://github.com/washingtonpost/data-police-shootings} }

License

CC BY NC SA 4.0

Splash banner

Image by pixabay avaiable on pexels.

As of October 22, police in the United States had shot 23 unarmed people to death in 2024. The most common weapon for a victim of a fatal police shooting to be carrying is a gun. In 2023, 717 people carrying a gun were shot and killed by the U.S. police.

In 2023, ** offenders who killed law enforcement officers in the United States were of an unknown race or their race was not reported to the FBI. ** white offenders and ** Black offenders also killed law enforcement officers in that year. From the total of known offenders that year, ** were male.

The Washington Post is compiling a database of every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

In 2015, The Post began tracking more than a dozen details about each killing — including the race of the deceased, the circumstances of the shooting, whether the person was armed and whether the person was experiencing a mental-health crisis — by culling local news reports, law enforcement websites and social media, and by monitoring independent databases such as Killed by Police and Fatal Encounters. The Post conducted additional reporting in many cases.

In 2016, The Post is gathering additional information about each fatal shooting by police that occurs this year and is filing open-records requests with departments. More than a dozen additional details are being collected about officers in each shooting. Officers’ names are being included in the database after The Post contacts the departments to request comment.

The Post is documenting only those shootings in which a police officer, in the line of duty, shoots and kills a civilian — the circumstances that most closely parallel the 2014 killing of Michael Brown in Ferguson, Mo., which began the protest movement culminating in Black Lives Matter and an increased focus on police accountability nationwide. The Post is not tracking deaths of people in police custody, fatal shootings by off-duty officers or non-shooting deaths. The FBI and the Centers for Disease Control and Prevention log fatal shootings by police, but officials acknowledge that their data is incomplete. In 2015, The Post documented more than twice as many fatal shootings by police as had been recorded by the FBI. Last year, the FBI announced plans to overhaul how it tracks fatal police encounters.

The Post's database is updated regularly as fatal shootings are reported and as facts emerge about individual cases. The Post is seeking assistance in making the database as comprehensive as possible. To provide information about fatal police shootings since Jan. 1, 2015, send us an email at policeshootingsfeedback@washpost.com. The Post is also interested in obtaining photos of the deceased and original videos of fatal encounters with police.

Data Dictionary

...

Key	List of...	Comment	Example Value
Person.Name	String	Full name of the individual or "Unknown" if not reported	"Tim Elliot"
Person.Age	Integer	Age in years of the individual or 0 (zero) if not reported	53
Person.Gender	String	One of Male, Female, or Unknown	"Male"
Person.Race	String	One of Asian, African American, White, Hispanic, Native American, Other, or Unknown.	"Asian"
Incident.Date.Month	Integer	Month (1-12) in which the shooting occurred	1
Incident.Date.Day	Integer	Day (1-31) in which the shooting occurred	2
Incident.Date.Year	Integer	Year (2015-2019) in which the shooting occurred	2015
Incident.Date.Full	String	Date in which shooting occurred (Year/Month/Day)	"2015/01/02"
Incident.Location.City	String	Name of city in which the shooting occurred	"Shelton"
Incident.Location.State	String	Name of U.S. State in which the shooting occurred	"WA"
Factors.Armed	String	Description of any weapon carried by the person (.e., "gun", "knife", "unarmed"); value is "unknown" if not reported.	"gun"
Factors.Mental-Illness	Boolean	True if factors of mental illness were perceived in the person; False otherwise	True
Factors.Threat-Level	String	Threat of person as perceived by police. One of "attack", "undetermined", or "other"; value is "unknown" if not reported.	"attack"
Factors.Fleeing	String	Means by which person was fleeing (e.g., "Car", "Foot") or "Not fleeing"; value is "unknown" if not reported.	"Not fleeing"
Shooting.Manner

Version 5 release notes: Removes support for SPSS and Excel data.Changes the crimes that are stored in each file. There are more files now with fewer crimes per file. The files and their included crimes have been updated below.Adds in agencies that report 0 months of the year.Adds a column that indicates the number of months reported. This is generated summing up the number of unique months an agency reports data for. Note that this indicates the number of months an agency reported arrests for ANY crime. They may not necessarily report every crime every month. Agencies that did not report a crime with have a value of NA for every arrest column for that crime.Removes data on runaways.Version 4 release notes: Changes column names from "poss_coke" and "sale_coke" to "poss_heroin_coke" and "sale_heroin_coke" to clearly indicate that these column includes the sale of heroin as well as similar opiates such as morphine, codeine, and opium. Also changes column names for the narcotic columns to indicate that they are only for synthetic narcotics. Version 3 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 2 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The Arrests by Age, Sex, and Race data is an FBI data set that is part of the annual Uniform Crime Reporting (UCR) Program data. This data contains highly granular data on the number of people arrested for a variety of crimes (see below for a full list of included crimes). The data sets here combine data from the years 1980-2015 into a single file. These files are quite large and may take some time to load. All the data was downloaded from NACJD as ASCII+SPSS Setup files and read into R using the package asciiSetupReader. All work to clean the data and save it in various file formats was also done in R. For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data. If you have any questions, comments, or suggestions please contact me at jkkaplan6@gmail.com.I did not make any changes to the data other than the following. When an arrest column has a value of "None/not reported", I change that value to zero. This makes the (possible incorrect) assumption that these values represent zero crimes reported. The original data does not have a value when the agency reports zero arrests other than "None/not reported." In other words, this data does not differentiate between real zeros and missing values. Some agencies also incorrectly report the following numbers of arrests which I change to NA: 10000, 20000, 30000, 40000, 50000, 60000, 70000, 80000, 90000, 100000, 99999, 99998. To reduce file size and make the data more manageable, all of the data is aggregated yearly. All of the data is in agency-year units such that every row indicates an agency in a given year. Columns are crime-arrest category units. For example, If you choose the data set that includes murder, you would have rows for each agency-year and columns with the number of people arrests for murder. The ASR data breaks down arrests by age and gender (e.g. Male aged 15, Male aged 18). They also provide the number of adults or juveniles arrested by race. Because most agencies and years do not report the arrestee's ethnicity (Hispanic or not Hispanic) or juvenile outcomes (e.g. referred to adult court, referred to welfare agency), I do not include these columns. To make it easier to merge with other data, I merged this data with the Law Enforcement Agency Identifiers Crosswalk (LEAIC) data. The data from the LEAIC add FIPS (state, county, and place) and agency type/subtype. Please note that some of the FIPS codes have leading zeros and if you open it in Excel it will automatically delete those leading zeros. I created 9 arrest categories myself. The categories are: Total Male JuvenileTotal Female JuvenileTotal Male AdultTotal Female AdultTotal MaleTotal FemaleTotal JuvenileTotal AdultTotal ArrestsAll of these categories are based on the sums of the sex-age categories (e.g. Male under 10, Female aged 22) rather than using the provided age-race categories (e.g. adult Black, juvenile Asian). As not all agencies report the race data, my method is more accurate. These categories also make up the data in the "simple" version of the data. The "simple" file only includes the above 9 columns as the arrest data (all other columns in the

For any questions about this data please email me at jacob@crimedatatool.com. If you use this data, please cite it.

Version 5 release notes:
Adds data in the following formats: SPSS, SAS, and Excel.Changes project name to avoid confusing this data for the ones done by NACJD.Adds data for 1991.Fixes bug where bias motivation "anti-lesbian, gay, bisexual, or transgender, mixed group (lgbt)" was labeled "anti-homosexual (gay and lesbian)" prior to 2013 causing there to be two columns and zero values for years with the wrong label.All data is now directly from the FBI, not NACJD. The data initially comes as ASCII+SPSS Setup files and read into R using the package asciiSetupReader. All work to clean the data and save it in various file formats was also done in R. For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data. Version 4 release notes:
Adds data for 2017.Adds rows that submitted a zero-report (i.e. that agency reported no hate crimes in the year). This is for all years 1992-2017. Made changes to categorical variables (e.g. bias motivation columns) to make categories consistent over time. Different years had slightly different names (e.g. 'anti-am indian' and 'anti-american indian') which I made consistent.
Made the 'population' column which is the total population in that agency.

Version 3 release notes:
Adds data for 2016.Order rows by year (descending) and ORI.Version 2 release notes:
Fix bug where Philadelphia Police Department had incorrect FIPS county code. The Hate Crime data is an FBI data set that is part of the annual Uniform Crime Reporting (UCR) Program data. This data contains information about hate crimes reported in the United States. Please note that the files are quite large and may take some time to open.

Each row indicates a hate crime incident for an agency in a given year. I have made a unique ID column ("unique_id") by combining the year, agency ORI9 (the 9 character Originating Identifier code), and incident number columns together. Each column is a variable related to that incident or to the reporting agency.
Some of the important columns are the incident date, what crime occurred (up to 10 crimes), the number of victims for each of these crimes, the bias motivation for each of these crimes, and the location of each crime. It also includes the total number of victims, total number of offenders, and race of offenders (as a group). Finally, it has a number of columns indicating if the victim for each offense was a certain type of victim or not (e.g. individual victim, business victim religious victim, etc.).

The only changes I made to the data are the following. Minor changes to column names to make all column names 32 characters or fewer (so it can be saved in a Stata format), changed the name of some UCR offense codes (e.g. from "agg asslt" to "aggravated assault"), made all character values lower case, reordered columns. I also added state, county, and place FIPS code from the LEAIC (crosswalk) and generated incident month, weekday, and month-day variables from the incident date variable included in the original data.

For a comprehensive guide to this data and other UCR data, please see my book at ucrbook.comVersion 11 release notes:Adds 2020 data. Please note that the FBI has retired UCR data ending in 2020 data so this will be the last SHR data they release. Changes .rda file to .rds.Version 10 release notes:Changes release notes description, does not change data.Version 9 release notes:Adds 2019 data.Version 8 release notes:Adds 2018 data.Changes source of data for years 1985-2018 to be directly from the FBI. 2018 data was received via email from the FBI, 2016-2017 is from the FBI who mailed me a DVD, and 1985-2015 data is from the FBI's Crime Data Explorer site (https://crime-data-explorer.fr.cloud.gov/downloads-and-docs).Adds .csv version of the data.Makes minor changes to value labels for consistency and to fix grammar. Version 7 release notes:Changes project name to avoid confusing this data for the ones done by NACJD.Version 6 release notes:Adds 2017 data.Version 5 release notes:Adds 2016 data.Standardizes the "group" column which categorizes cities and counties by population.Arrange rows in descending order by year and ascending order by ORI. Version 4 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. Version 3 Release Notes:Merges data with LEAIC data to add FIPS codes, census codes, agency type variables, and ORI9 variable.Change column names for relationship variables from offender_n_relation_to_victim_1 to victim_1_relation_to_offender_n to better indicate that all relationship are victim 1's relationship to each offender. Reorder columns.This is a single file containing all data from the Supplementary Homicide Reports from 1976 to 2018. The Supplementary Homicide Report provides detailed information about the victim, offender, and circumstances of the murder. Details include victim and offender age, sex, race, ethnicity (Hispanic/not Hispanic), the weapon used, circumstances of the incident, and the number of both offenders and victims. Years 1976-1984 were downloaded from NACJD, while more recent years are from the FBI. All files came as ASCII+SPSS Setup files and were cleaned using R. The "cleaning" just means that column names were standardized (different years have slightly different spellings for many columns). Standardization of column names is necessary to stack multiple years together. Categorical variables (e.g. state) were also standardized (i.e. fix spelling errors, have terminology be the same across years). The following is the summary of the Supplementary Homicide Report copied from ICPSR's 2015 page for the data.The Uniform Crime Reporting Program Data: Supplementary Homicide Reports (SHR) provide detailed information on criminal homicides reported to the police. These homicides consist of murders; non-negligent killings also called non-negligent manslaughter; and justifiable homicides. UCR Program contributors compile and submit their crime data by one of two means: either directly to the FBI or through their State UCR Programs. State UCR Programs frequently impose mandatory reporting requirements which have been effective in increasing both the number of reporting agencies as well as the number and accuracy of each participating agency's reports. Each agency may be identified by its numeric state code, alpha-numeric agency ("ORI") code, jurisdiction population, and population group. In addition, each homicide incident is identified by month of occurrence and situation type, allowing flexibility in creating aggregations and subsets.

The Tempe Police Department prides itself in its continued efforts to reduce harm within the community and is providing this dataset on hate crime incidents that occur in Tempe.The Tempe Police Department documents the type of bias that motivated a hate crime according to those categories established by the FBI. These include crimes motivated by biases based on race and ethnicity, religion, sexual orientation, disability, gender and gender identity.The Bias Type categories provided in the data come from the Bias Motivation Categories as defined in the Federal Bureau of Investigation (FBI) National Incident-Based Reporting System (NIBRS) manual, version 2020.1 dated 4/15/2021. The FBI NIBRS manual can be found at https://www.fbi.gov/file-repository/ucr/ucr-2019-1-nibrs-user-manua-093020.pdf with the Bias Motivation Categories found on pages 78-79.Although data is updated monthly, there is a delay by one month to allow for data validation and submission.Information about Tempe Police Department's collection and reporting process for possible hate crimes is included in https://storymaps.arcgis.com/stories/a963e97ca3494bfc8cd66d593eebabaf.Additional InformationSource: Data are from the Law Enforcement Records Management System (RMS)Contact: Angelique BeltranContact E-Mail: angelique_beltran@tempe.govData Source Type: TabularPreparation Method: Data from the Law Enforcement Records Management System (RMS) are entered by the Tempe Police Department into a GIS mapping system, which automatically publishes to open data.Publish Frequency: MonthlyPublish Method: New data entries are automatically published to open data. Data Dictionary

This segment of NIBRS data provides information on crime victims, including their age, race, sex, ethnicity, residency status within the jurisdiction, and victim type (e.g., individual, police officer, business, government). This data records physical injuries sustained, with up to five of seven possible injury types. A key variable is the victim-offender relationship, which is available for up to 10 offenders and categorizes relationships into 27 types (e.g., spouse, child, employee, stranger). This data is limited to individual and police officer victims, though non-human victims could have relevant offender relationships. Additionally, for aggravated assaults and homicides, a “circumstance” variable indicates the motive (e.g., argument, domestic violence, hunting accident). A victim sequence number distinguishes multiple victims within a single incident.

For any questions about this data please email me at jacob@crimedatatool.com. If you use this data, please cite it.Version 8 release notes:Adds 2018 data.Changes source of data for years 1985-2018 to be directly from the FBI. 2018 data was received via email from the FBI, 2016-2017 is from the FBI who mailed me a DVD, and 1985-2015 data is from the FBI's Crime Data Explorer site (https://crime-data-explorer.fr.cloud.gov/downloads-and-docs).Adds .csv version of the data.Makes minor changes to value labels for consistency and to fix grammar. Version 7 release notes:Changes project name to avoid confusing this data for the ones done by NACJD.Version 6 release notes:Adds 2017 data.Version 5 release notes:Adds 2016 data.Standardizes the "group" column which categorizes cities and counties by population.Arrange rows in descending order by year and ascending order by ORI. Version 4 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. Version 3 Release Notes:Merges data with LEAIC data to add FIPS codes, census codes, agency type variables, and ORI9 variable.Change column names for relationship variables from offender_n_relation_to_victim_1 to victim_1_relation_to_offender_n to better indicate that all relationship are victim 1's relationship to each offender. Reorder columns.This is a single file containing all data from the Supplementary Homicide Reports from 1976 to 2018. The Supplementary Homicide Report provides detailed information about the victim, offender, and circumstances of the murder. Details include victim and offender age, sex, race, ethnicity (Hispanic/not Hispanic), the weapon used, circumstances of the incident, and the number of both offenders and victims. Years 1976-1984 were downloaded from NACJD, while more recent years are from the FBI. All files came as ASCII+SPSS Setup files and were cleaned using R. The "cleaning" just means that column names were standardized (different years have slightly different spellings for many columns). Standardization of column names is necessary to stack multiple years together. Categorical variables (e.g. state) were also standardized (i.e. fix spelling errors, have terminology be the same across years). The following is the summary of the Supplementary Homicide Report copied from ICPSR's 2015 page for the data.The Uniform Crime Reporting Program Data: Supplementary Homicide Reports (SHR) provide detailed information on criminal homicides reported to the police. These homicides consist of murders; non-negligent killings also called non-negligent manslaughter; and justifiable homicides. UCR Program contributors compile and submit their crime data by one of two means: either directly to the FBI or through their State UCR Programs. State UCR Programs frequently impose mandatory reporting requirements which have been effective in increasing both the number of reporting agencies as well as the number and accuracy of each participating agency's reports. Each agency may be identified by its numeric state code, alpha-numeric agency ("ORI") code, jurisdiction population, and population group. In addition, each homicide incident is identified by month of occurrence and situation type, allowing flexibility in creating aggregations and subsets.

Abstract (en): For any questions about this data please email me at jacob@crimedatatool.com. If you use this data, please cite it.Version 7 release notes:Changes project name to avoid confusing this data for the ones done by NACJD.Version 6 release notes:Adds 2017 data.Version 5 release notes:Adds 2016 data.Standardizes the "group" column which categorizes cities and counties by population.Arrange rows in descending order by year and ascending order by ORI. Version 4 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. Version 3 Release Notes:Merges data with LEAIC data to add FIPS codes, census codes, agency type variables, and ORI9 variable.Change column names for relationship variables from offender_n_relation_to_victim_1 to victim_1_relation_to_offender_n to better indicate that all relationship are victim 1's relationship to each offender. Reorder columns.This is a single file containing all data from the Supplementary Homicide Reports from 1976 to 2017. The Supplementary Homicide Report provides detailed information about the victim, offender, and circumstances of the murder. Details include victim and offender age, sex, race, ethnicity (Hispanic/not Hispanic), the weapon used, circumstances of the incident, and the number of both offenders and victims. All the data was downloaded from NACJD as ASCII+SPSS Setup files and cleaned using R. The "cleaning" just means that column names were standardized (different years have slightly different spellings for many columns). Standardization of column names is necessary to stack multiple years together. Categorical variables (e.g. state) were also standardized (i.e. fix spelling errors, have terminology be the same across years). The following is the summary of the Supplementary Homicide Report copied from ICPSR's 2015 page for the data.The Uniform Crime Reporting Program Data: Supplementary Homicide Reports (SHR) provide detailed information on criminal homicides reported to the police. These homicides consist of murders; non-negligent killings also called non-negligent manslaughter; and justifiable homicides. UCR Program contributors compile and submit their crime data by one of two means: either directly to the FBI or through their State UCR Programs. State UCR Programs frequently impose mandatory reporting requirements which have been effective in increasing both the number of reporting agencies as well as the number and accuracy of each participating agency's reports. Each agency may be identified by its numeric state code, alpha-numeric agency ("ORI") code, jurisdiction population, and population group. In addition, each homicide incident is identified by month of occurrence and situation type, allowing flexibility in creating aggregations and subsets. Victims of homicide in the United States between 1976 and 2017.Smallest Geographic Unit: Police agency