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.

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 killing of Tyre Nichols in January 2023 by Memphis Police Officers has reignited debates about police brutality in the United States. Between 2013 and 2024, over 1,000 people have been killed by police every year. Some of the most infamous examples include the murder of George Floyd in May 2020 and the shooting of Breonna Taylor earlier that year. Within the provided time period, the most people killed by police in the United States was in 2024, at 1,375 people. Police Violence in the U.S. Police violence is defined as any instance where a police officer’s use of force results in a civilian’s death, regardless of whether it is considered justified by the law. While many people killed by police in the U.S. were shot, other causes of death have included tasers, vehicles, and physical restraints or beatings. In the United States, the rate of police shootings is much higher for Black Americans than it is for any other ethnicity, and recent incidents of police killing unarmed Black men and women in the United States have led to widespread protests against police brutality, particularly towards communities of color. America’s Persistent Police Problem Despite increasing visibility surrounding police violence in recent years, police killings have continued to occur in the United States at a consistently high rate. In comparison to other countries, police in the U.S. have killed people at a rate three times higher than police in Canada and 60 times the rate of police in England. While U.S. police have killed people in almost all 50 states, as well as the District of Columbia, New Mexico was reported to have the highest rate of people killed by the police in the United States, with 8.03 people per million inhabitants killed by police.

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.

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.

This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

Data Description: This data represents officer involved shooting incidents by the Cincinnati Police Department. An officer involved shooting (OIS) may be defined as the discharge of a firearm, which may include accidental and intentional discharges, by a police officer, whether on or off duty.

Data Creation: This data is created through reporting by the Cincinnati Police Department.

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

Refresh Frequency: This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

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/c64e-ybfz/

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: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

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. The following is a complete list of OIS tables posted on the Charlotte Open Data Portal:1) Officer Involved Shootings – Incidents: contains INCIDENT_ID (for joining to other OIS tables), year and month recorded, location, district attorney legal review status, descriptive narrative of incident2) Officer Involved Shootings – Individuals: contains INCIDENT_ID (for joining to other OIS tables) as well as individual’s race, gender, age, and injury type3) Officer Involved Shootings – Officers: contains INCIDENT_ID (for joining to other OIS tables) as well as officer’s race, gender, years of service, and CMPD policy violation status. Please note that the relationship of the Incidents table to the Individuals table is one-to-many, and the relationship of the Incidents table to the Officers table is one-to-many.

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.

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.

The police shootings data is from the database maintained by Washington Post at https://github.com/washingtonpost/data-police-shootings (version 2) that covers the period 2015-2023.The curated datasets are included here along with a research question and guiding questions.See the codebook for full details.

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.

Dallas Police Public Data - Officer Involved Shootings City Of Dallas

In 2023/24, the police in England and Wales fatally shot two people, compared with three in the previous reporting year, and six in 2016/17. During the same reporting year, the police used firearms twice, compared with ten times in 2022/23. In general, the police in England and Wales and in the rest of the UK do not have a tradition of carrying firearms, with the country having some of the strictest gun laws in the world. In 2023/24, out of around 147,746 police officers, just 5,861 were licensed to carry firearms in England and Wales. Comparisons with the United States Among developed economies, the United States is something of an outlier when it comes to police shootings. In 2024, it is estimated that the police in the United States fatally shot 1,173 people. There are also significant disparities based on a person's ethnicity. Between 2015 and March 2024, the rate of fatal police shootings among Black Americans was 6.1 per one million people, 2.7 per million people for Hispanic Americans and 2.4 per million people for white Americans. Gun violence overall is also far more prevalent in the United States, with 42 percent of American households owning a firearm as of 2023. Gun homicides rare in England and Wales Of the 583 homicides that took place in England and Wales in 2023/24, just 22 were committed by a person using a firearm. By far the most common method of killing was using a knife or other sharp instrument, at 262 homicides, or around 46 percent of them. Compared with twenty years ago, homicides in England and Wales have declined, falling from 1,047 in 2002/03, to just 533 in 2014/15. After this point, annual homicides rose, and by 2016/17 there were more than 700 homicides recorded in England and Wales. Although there have been some fluctuations, particularly during 2020/21 at the height of COVID-19 lockdowns.

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.

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

Officer Involved Shooting (OIS) Database and Statistical Analysis. Data is updated after there is an officer involved shooting.PIU#Incident # - the number associated with either the incident or used as reference to store the items in our evidence rooms Date of Occurrence Month - month the incident occurred (Note the year is labeled on the tab of the spreadsheet)Date of Occurrence Day - day of the month the incident occurred (Note the year is labeled on the tab of the spreadsheet)Time of Occurrence - time the incident occurredAddress of incident - the location the incident occurredDivision - the LMPD division in which the incident actually occurredBeat - the LMPD beat in which the incident actually occurredInvestigation Type - the type of investigation (shooting or death)Case Status - status of the case (open or closed)Suspect Name - the name of the suspect involved in the incidentSuspect Race - the race of the suspect involved in the incident (W-White, B-Black)Suspect Sex - the gender of the suspect involved in the incidentSuspect Age - the age of the suspect involved in the incidentSuspect Ethnicity - the ethnicity of the suspect involved in the incident (H-Hispanic, N-Not Hispanic)Suspect Weapon - the type of weapon the suspect used in the incidentOfficer Name - the name of the officer involved in the incidentOfficer Race - the race of the officer involved in the incident (W-White, B-Black, A-Asian)Officer Sex - the gender of the officer involved in the incidentOfficer Age - the age of the officer involved in the incidentOfficer Ethnicity - the ethnicity of the suspect involved in the incident (H-Hispanic, N-Not Hispanic)Officer Years of Service - the number of years the officer has been serving at the time of the incidentLethal Y/N - whether or not the incident involved a death (Y-Yes, N-No, continued-pending)Narrative - a description of what was determined from the investigationContact:Carol Boylecarol.boyle@louisvilleky.gov

This dataset contains Phoenix Police Department Officer-Involved Shooting (OIS) incidents from January 2017 forward, including demographic information for officers as well as individuals. Data is updated hourly; however, new OIS incidents are only displayed after information is compiled for all the fields displayed in the dataset, which may take several days following the incident.

More than one officer may discharge their weapon during the same incident. Accidental discharges, discharges at animals, and discharges at objects where there was not an active threat by a subject are not included in this data set.

View Operations Order 1.5: Response to Resistance Policy

Provide your feedback!

Help us improve this site and complete the Open Data Customer Survey.

The data set is refreshed on the last Friday of the month at 7:30 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.

This dataset contains individual-level homicide and non-fatal shooting victimizations, including homicide data from 1991 to the present, and non-fatal shooting data from 2010 to the present (2010 is the earliest available year for shooting data). 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-access dataset, but with "UNKNOWN" in the shooting column.

Each row represents a single victimization, i.e., a unique event when an individual became the victim of a homicide or non-fatal shooting. Each row does not represent a unique victim—if someone is victimized multiple times there will be multiple rows for each of those distinct events.

The dataset is refreshed daily, but excludes the most recent complete day to allow the Chicago Police Department (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.

A version of this dataset with additional crime types is available by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Violence Reduction Victims Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup.

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: 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.” Officer-involved shootings are not included.

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.

Note: In some instances, CPD'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 reliable crime determination, the dataset will show empty cells in the respective demographic fields (age, sex, race, etc.).

Note: Homicide victims names are delayed by two weeks to allow time for the victim’s family to be notified of their passing.

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.

Note: This dataset includes variables referencing administrative or political boundaries that are subject to change. These include Street Outreach Organization boundary, Ward, Chicago Police Department District, Chicago Police Department Area, Chicago Police Department Beat, Illinois State Senate District, and Illinois State House of Representatives District. These variables reflect current geographic boundaries as of November 1st, 2021. In some instances, current boundaries may conflict with those that were in place at the time that a given incident occurred in prior years. For example, the Chicago Police Department districts 021 and 013 no longer exist. Any historical violent crime victimization that occurred in those districts when they were in existence are marked in this dataset as having occurred in the current districts that expanded to replace 013 and 021."

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.