"In 2015, The Washington Post began to log every fatal shooting by an on-duty police officer in the United States. In that time there have been more than 5,000 such shootings recorded by The Post. After Michael Brown, an unarmed Black man, was killed in 2014 by police in Ferguson, Mo., a Post investigation found that the FBI undercounted fatal police shootings by more than half. This is because reporting by police departments is voluntary and many departments fail to do so. The Washington Post’s data relies primarily on news accounts, social media postings, and police reports. Analysis of more than five years of data reveals that the number and circumstances of fatal shootings and the overall demographics of the victims have remained relatively constant..." SOURCE ==> Washington Post Article

For more information about this story

This dataset has been prepared by The Washington Post (they keep updating it on runtime) with every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

2016 PoliceKillingUS DATASET
2017 PoliceKillingUS DATASET
2018 PoliceKillingUS DATASET
2019 PoliceKillingUS DATASET
2020 PoliceKillingUS DATASET

Features at the Dataset:

The file fatal-police-shootings-data.csv contains data about each fatal shooting in CSV format. The file can be downloaded at this URL. Each row has the following variables:

• id: a unique identifier for each victim
• name: the name of the victim
• date: the date of the fatal shooting in YYYY-MM-DD format
• manner_of_death: shot, shot and Tasered
• armed: indicates that the victim was armed with some sort of implement that a police officer believed could inflict harm
  • undetermined: it is not known whether or not the victim had a weapon
  • unknown: the victim was armed, but it is not known what the object was
  • unarmed: the victim was not armed
• age: the age of the victim
• gender: the gender of the victim. The Post identifies victims by the gender they identify with if reports indicate that it differs from their biological sex.
  • M: Male
  • F: Female
  • None: unknown
• race:
  • W: White, non-Hispanic
  • B: Black, non-Hispanic
  • A: Asian
  • N: Native American
  • H: Hispanic
  • O: Other
  • None: unknown
• city: the municipality where the fatal shooting took place. Note that in some cases this field may contain a county name if a more specific municipality is unavailable or unknown.
• state: two-letter postal code abbreviation
• signs of mental illness: News reports have indicated the victim had a history of mental health issues, expressed suicidal intentions or was experiencing mental distress at the time of the shooting.
• threat_level: The threat_level column was used to flag incidents for the story by Amy Brittain in October 2015. http://www.washingtonpost.com/sf/investigative/2015/10/24/on-duty-under-fire/ As described in the story, the general criteria for the attack label was that there was the most direct and immediate threat to life. That would include incidents where officers or others were shot at, threatened with a gun, attacked with other weapons or physical force, etc. The attack category is meant to flag the highest level of threat. The other and undetermined categories represent all remaining cases. Other includes many incidents where officers or others faced significant threats.
• flee: News reports have indicated the victim was moving away from officers
  • Foot
  • Car
  • Not fleeing

The threat column and the fleeing column are not necessarily related. For example, there is an incident in which the suspect is fleeing and at the same time turns to fire at gun at the officer. Also, attacks represent a status immediately before fatal shots by police while fleeing could begin slightly earlier and involve a chase. - body_camera: News reports have indicated an officer w...

This data was obtained from https://mappingpoliceviolence.us/.

Mapping Police Violence is a 501(c)(3) organization that publishes the most comprehensive and up-to-date data on police violence in America to support transformative change.

This is a database set on openly sharing information on police violence in America.

Some information on this data according to their website: Our data has been meticulously sourced from official police use of force data collection programs in states like California, Texas and Virginia, combined with nationwide data from The Gun Violence Archive and the Fatal Encounters database, two impartial crowdsourced databases. We've also done extensive original research to further improve the quality and completeness of the data; searching social media, obituaries, criminal records databases, police reports and other sources to identify the race of 90 percent of all victims in the database.

We believe the data represented on this site is the most comprehensive accounting of people killed by police since 2013. Note that the Mapping Police Violence database is more comprehensive than the Washington Post police shootings database: while WaPo only tracks cases where people are fatally shot by on-duty police officers, our database includes additional incidents such as cases where police kill someone through use of a chokehold, baton, taser or other means as well as cases such as killings by off-duty police. A recent report from the Bureau of Justice Statistics estimated approximately 1,200 people were killed by police between June, 2015 and May, 2016. Our database identified 1,100 people killed by police over this time period. While there are undoubtedly police killings that are not included in our database (namely, those that go unreported by the media), these estimates suggest that our database captures 92% of the total number of police killings that have occurred since 2013. We hope these data will be used to provide greater transparency and accountability for police departments as part of the ongoing work to end police violence in America.

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.

This dataset, compiled by The Washington Post, logs every person shot and killed by an on-duty police officer in the United States from 2015 to 2024. Following the 2014 shooting of Michael Brown in Ferguson, it was discovered that FBI reports were significantly undercounted, with only a third of fatal shootings recorded by 2021. This comprehensive database aims to fill that gap and provide detailed information on each incident, including the police departments involved, to enhance accountability.

The Shootings dashboard contains information on shooting incidents where a victim was struck by a bullet, either fatally or non-fatally; that occurred in the City of Boston and fall under Boston Police Department jurisdiction. The dashboard does not contain records for self-inflicted gunshot wounds or shootings determined to be justifiable. Information on the incident, and the demographics of victims are included. This information is updated based on analysis conducted by the Boston Regional Intelligence Center under the Boston Police Department Bureau of Intelligence and Analysis. The data is for 2015 forward, with a 7 day rolling delay to allow for analysis and data entry to occur.

A comprehensive review of an aggregated dataset, containing any death happening between the years 2015 to 2021 that is inflicted by an on-duty or off-duty officer where the officer fatally shoots the victim. The dataset is called aggregated because it's an aggregation of the observations inside three fatal police datasets: Fatal Encounters, Mapping Police Violence, Washington Post.

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.

Bloomington Police Department cases where officers have fired a gun at an individual. Key code for Race: A- Asian/Pacific Island, Non-Hispanic B- African American, Non-Hispanic C- Hawaiian/Other Pacific Island, Hispanic H- Hawaiian/Other Pacific Island, Non-Hispanic I- Indian/Alaskan Native, Non-Hispanic K- African American, Hispanic L- Caucasian, Hispanic N- Indian/Alaskan Native, Hispanic P- Asian/Pacific Island, Hispanic S- Asian, Non-Hispanic T- Asian, Hispanic U- Unknown W- Caucasian, Non-Hispanic Key Code for Reading Districts: Example: LB519 L for Law call or incident B stands for Bloomington 5 is the district or beat where incident occurred All numbers following represents a grid sector. Disclaimer: The Bloomington Police Department takes great effort in making open data as accurate as possible, but there is no avoiding the introduction of errors in this process, which relies on data provided by many people and that cannot always be verified. Information contained in this dataset may change over a period of time. The Bloomington Police Department is not responsible for any error or omission from this data, or for the use or interpretation of the results of any research conducted.

Police killings dataset (not just shooting, but by any means) is from https://mappingpoliceviolence.org/ that covers the period 2013-2023. This includes the Washington Post (WaPo) dataset on shooting victims.The curated datasets are included here along with a research question and guiding questions.See the codebook for full details.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

Context

This dataset contains information about fatal shooting of civilians by police officers in the US since Jan 1st, 2015. The data about the shootings was collected by the Washington Post in their fatal police shootings dataset. The city locations were geocoded using OpenStreetMap Nominatim.

Content

fatal-police-shootings-data.csv contains information about each shooting. Each row is a shooting, and columns contain information about

• Name of the individual shot
• Date of the shooting
• Manner of death of the individual shot
• If and how the individual shot was armed
• Age of the individual shot
• Gender of the individual shot
• Race of the individual shot
• Whether the individual shot displayed signs of mental illness
• To what level the individual shot was attacking when shot
• If and how the individual shot was fleeing from police
• If an officer present for the shooting was wearing a body camera

CityLocations.csv contains the latitude and longitude for each city present in fatal-police-shootings-data.csv.

Acknowledgements and Licenses

The data in fatal-police-shootings-data.csv was collected by the Washington Post, and is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License.

The data in CityLocations.csv was geocoded using OpenStreetMap Nominatim, and is licensed under the Open Database License.

Cover image by Spenser.

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.

This set of raw data contains information from Bloomington Police Department cases, specifically it identified cases where officers have fired a gun at a suspect.

**Please note that this particular dataset contains no data. As of current date, the Bloomington Police Department has had no officer involved shootings to report. **

Key code for Race:

• A- Asian/Pacific Island, Non-Hispanic
• B- African American, Non-Hispanic
• I- Indian/Alaskan Native, Non-Hispanic
• K- African American, Hispanic
• L- Caucasian, Hispanic
• N- Indian/Alaskan Native, Hispanic
• P- Asian/Pacific Island, Hispanic
• U- Unknown
• W- Caucasian, Non-Hispanic

Key Code for Reading Districts:

Example: LB519

• ‘L’ for Law call or incident
• ‘B’ stands for Bloomington
• 5 is the district or beat where incident occurred
• All numbers following represents a grid sector.

A map of the five districts can be located on Raidsonline.com, under the tab labeled ‘Agency Layers’.

Disclaimer: The Bloomington Police Department takes great effort in making all sets of data as accurate as possible, but there is no avoiding the introduction of errors in this process. Information contained in this dataset may change over a period of time. The Bloomington Police Department is not responsible for any error or omission from this data or for the use, or interpretation of the results of any research conducted.

Records of Officer Involved Shootings (OIS) from 2005 to the present, including a brief narrative synopsis. Beginning in Q3 2023, the summary will be replaced with a link to the FRB findings documented, prepared for public release. A link for each OIS will be embedded in the file. Data set does not contain records from active investigations. Data is visualized in a dashboard on the SPD public site (https://www.seattle.gov/police/information-and-data/use-of-force-data/officer-involved-shootings-dashboard), please reference as a guide for use. Dashboard is available for download. Updates are posted twice a year (January and July), as cases complete the inquest process (https://kingcounty.gov/services/inquest-program.aspx). Use of force data also available here: https://data.seattle.gov/Public-Safety/Use-Of-Force/ppi5-g2bj and is updated daily. Data includes Type III - OIS.

Dallas Police Public Data - Officer Involved Shootings City Of Dallas

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.

List of every shooting incident that occurred in NYC during the current calendar year. This is a breakdown of every shooting incident that occurred in NYC during the current calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents a shooting incident in NYC and includes information about the event, the location and time of occurrence. In addition, information related to suspect and victim demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.

An Officer Involved Shooting (OIS) is the discharge of a firearm, whether accidental or intentional, by a police officer, whether on or off duty. For the purposes of this posting, an OIS will only refer to the instances in which an officer discharged a firearm at a person. CMPD posts Officer Involved Shootings in an effort to create greater transparency of the actions of our employees. It is important to us that members of the community are informed whenever an officer discharges his/her firearm at a person and whether the shooting follows department policies and procedures. We believe that your trust and confidence in the Charlotte-Mecklenburg Police Department will increase as you understand what our officers encounter and how we hold them accountable for their actions. The CMPD is continuously reviewing and improving our practices to reduce the likelihood of deadly force incidents. For more information, please visit https://charlottenc.gov/CMPD/Pages/Resources/CMPD-OpenData.aspx.

This is a set of csv files including a number of variables including fatal police shootings and other crime and socioeconomic covariates at different levels of geographical aggregation from 2013-2016. Five of the files use only the Washington Post data covering years 2015 and 2016, whereas the other five files utilize fatal police shootings of civilians for years 2013-2016, combining the Lott & Moody (2016) data for years 2013-2015 and Washington Post data for 2016. Other variables are included from the American Community Survey (ACS), the FBI's Uniform Crime Reports (UCR), the Law Enforcement Management and Administrative Statistics (LEMAS), Stanford Education Data Archive (SEDA), the US Census, and the Local Area Unemployment Statistics (LAUS) provided by the Bureau of Labor Statistics (BLS). The base file is the county-level data. The two files labelled "tenk" consist of regions with at least 10,000 residents. Counties with fewer than 10,000 residents are combined with adjacent counties, ranked by population in ascending order, so that counties with fewer than 10,000 residents are iteratively combined with adjacent neighbors with the fewest residents until they reach the threshold of 10,000 residents. The same algorithm is used to produce regions with 100,000 and 1 million residents. The final two files are state-level aggregations.

Data Description: This dataset captures confirmed shooting events in the City of Cincinnati. Shootings events are captured in the Computer Aided Dispatch System (CAD), and are ultimately stored in the City's Records Management System (RMS).

No personal or identifying (or otherwise sensitive) victim or suspect information is included in this data set.

Data Creation: This data is created through the City’s computer-aided dispatch (CAD) system.

Data Created By: The source of this data is the Cincinnati Police Department.

Refresh Frequency: This data is updated daily.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/xw7t-5phj

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.