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.

"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...

The Uniform Crime Reporting Program Data, Police Employee Data, 2019 file contains monthly data on felonious or accidental killings and assaults upon United States law enforcement officers acting in the line of duty. The Federal Bureau of Investigation (FBI) assembled the data and processed them from UCR Master Police Employee (LEOKA) data tapes. Each agency record in the file includes the following summary variables: state code, population group code, geographic division, Metropolitan Statistical Area code, and agency name. These variables afford considerable flexibility in creating subsets or aggregations of the data. Since 1930, the Federal Bureau of Investigation has compiled the Uniform Crime Reports (UCR) to serve as a periodic nationwide assessment of reported crimes not available elsewhere in the criminal justice system. Each year, this information is reported in four types of files: (1) Offenses Known and Clearances by Arrest, (2) Property Stolen and Recovered, (3) Supplementary Homicide Reports (SHR), and (4) Police Employee (LEOKA) Data. The Police Employee (LEOKA) Data provide information about law enforcement officers killed or assaulted (hence the acronym, LEOKA) in the line of duty. The variables created from the LEOKA forms provide in-depth information on the circumstances surrounding killings or assaults, including type of call answered, type of weapon used, and type of patrol the officers were on.

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 publication in which the FBI provides data on law enforcement uses of force that result in the death of a person, serious bodily injury of a person, or when law enforcement discharges a firearm at or in the direction of a person. In addition, law enforcement agencies can indicate months where no incidents meeting the above criteria occurred.

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.

The UNIFORM CRIME REPORTING PROGRAM DATA: SUPPLEMENTARY HOMICIDE REPORTS, 2019 (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 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.

Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

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 49 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 49 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.

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

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.

This 2019 crime data is the list of crimes that the Syracuse Police Department responded to in 2019. These records does not include rape offenses as well as any crimes that have been sealed by the court. Crimes are reported to the FBI in two major categories under the Uniform Crime Reports specification: Part 1 and Part 2 crimes. Part 1 crimes include criminal homicide, forcible rape, robbery, aggravated assault, burglary, larceny-theft, and motor vehicle theft. In these records, rape offenses have been excluded due to victim privacy concerns.Part 2 crimes include all other offenses. A more detailed guide to Part 1 crimes is listed below. More details about Part 2 Crimes is listed in the Part 2 Crimes Dataset.When using the data, the date and time provided are when the crime was actually reported. This means that though a larceny might be reported at noon, the actual crime could have happened at 8am, but was not realized until someone noticed hours later. Similarly, if a home break-in happens during a holiday weekend when the owners are out of town, the crime report may not come in until they return home and notice the crime took place previously. The address in the dataset is where the crime occurred. The location is also anonymized to the block level, so a crime that occurred at 123 Main St. will appear as occurring on the 100 block of Main St. This is to protect the privacy of all involved. Finally, information about crimes is fluid, and details about the crime could change.Data DictionaryDR Number - Department Report (DR) number is a unique number assigned by the Records Management System, the first two numbers identify the year in which the incident was reported.Time start and time end - Listed in military time (2400) - Burglaries and larcenies are often a time frame. Address - Where the crime occurred. All addresses are in the 100’s because the Syracuse Police Department allows privacy for residents and only lists the block number.Code Defined - Offense names are listed as crime categories group for ease of understanding. There may have been other offenses also, but the one displayed is the highest Unified Crime Reporting (UCR) category.Arrest - Means that there was an arrest, but not necessarily for that crime.Larceny Code - Indicates the type of larceny (Example: From Building or From Motor Vehicle).DisclaimerData derived from the Syracuse Police Department record management system, any data not listed is not currently available.Part I Crime DefinitionsCriminal homicide—a.) Murder and non-negligent manslaughter: the willful (non-negligent) killing of one human being by another. Deaths caused by negligence, attempts to kill, assaults to kill, suicides, and accidental deaths are excluded. The program classifies justifiable homicides separately and limits the definition to: (1) the killing of a felon by a law enforcement officer in the line of duty; or (2) the killing of a felon, during the commission of a felony, by a private citizen. b.) Manslaughter by negligence: the killing of another person through gross negligence. Deaths of persons due to their own negligence, accidental deaths not resulting from gross negligence, and traffic fatalities are not included in the category Manslaughter by Negligence. Robbery—The taking or attempting to take anything of value from the care, custody, or control of a person or persons by force or threat of force or violence and/or by putting the victim in fear. Aggravated assault—An unlawful attack by one person upon another for the purpose of inflicting severe or aggravated bodily injury. This type of assault usually is accompanied by the use of a weapon or by means likely to produce death or great bodily harm. Simple assaults are excluded. Burglary (breaking or entering)—The unlawful entry of a structure to commit a felony or a theft. Attempted forcible entry is included. Larceny-theft (except motor vehicle theft)—The unlawful taking, carrying, leading, or riding away of property from the possession or constructive possession of another. Examples are thefts of bicycles, motor vehicle parts and accessories, shoplifting, pocket picking, or the stealing of any property or article that is not taken by force and violence or by fraud. Attempted larcenies are included. Embezzlement, confidence games, forgery, check fraud, etc., are excluded. Motor vehicle theft—The theft or attempted theft of a motor vehicle. A motor vehicle is self-propelled and runs on land surface and not on rails. Motorboats, construction equipment, airplanes, and farming equipment are specifically excluded from this category.

!!!WARNING~~~This dataset has a large number of flaws and is unable to properly answer many questions that people generally use it to answer, such as whether national hate crimes are changing (or at least they use the data so improperly that they get the wrong answer). A large number of people using this data (academics, advocates, reporting, US Congress) do so inappropriately and get the wrong answer to their questions as a result. Indeed, many published papers using this data should be retracted. Before using this data I highly recommend that you thoroughly read my book on UCR data, particularly the chapter on hate crimes (https://ucrbook.com/hate-crimes.html) as well as the FBI's own manual on this data. The questions you could potentially answer well are relatively narrow and generally exclude any causal relationships. ~~~WARNING!!!Version 8 release notes:Adds 2019 dataVersion 7 release notes:Changes release notes description, does not change data.Version 6 release notes:Adds 2018 dataVersion 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. 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), made all character values lower case, reordered columns. I also generated incident month, weekday, and month-day variables from the incident date variable included in the original data.

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

The "2019 Crimes Data" dataset contains information about reported crimes in various regions through the year 2000-2019. This dataset aims to provide insights into crime trends, patterns, and rates for analysis and predictive modeling. The data can be used for exploratory data analysis (EDA), trend identification, and forecasting future crime activities and rates. The dataset is particularly valuable for law enforcement agencies, researchers, and analysts interested in understanding crime dynamics. ***Source of Data*:** The data was collected from official crime statistics sources, police department records, and news articles from reputable sources. All efforts were made to ensure accuracy and reliability in data collection.

Usage: This dataset is suitable for a wide range of analyses, including exploratory data analysis, trend visualization, and predictive modeling. Analysts and researchers can use this data to uncover crime patterns, identify hotspots, and develop models for predicting crime rates in upcoming years. Law enforcement agencies, such as the FBI, can benefit from insights gained through this dataset to improve crime prevention and resource allocation strategies.

The data within only represent 2019 and prior. As of January 2020, Mesa PD transitioned crime reporting to the FBI Unified Crime Reporting (UCR) Program from the Summary Reporting System (SRS) format to the new National Incident-Based Reporting System (NIBRS) format. As of January 1, 2021, the National Incident-Based Reporting System (NIBRS) became the national crime data collection program.

NIBRS was implemented to improve the overall quality of crime data collected by law enforcement, by capturing details on each single crime incident, as well as on separate offenses within the same incident. The historic Summary Reporting System (SRS) data collection, which collects more limited information than the more robust NIBRS, was phased out to make Uniform Crime Reporting (UCR) a NIBRS-only data collection.

The data within only represent 2019 and prior. As of January 2020, Mesa PD transitioned crime reporting to the FBI Unified Crime Reporting (UCR) Program from the Summary Reporting System (SRS) format to the new National Incident-Based Reporting System (NIBRS) format. For current clearance rate data based on NIBRS reporting standard please navigate to: https://citydata.mesaaz.gov/Police/Police-Case-Clearance-Rates/wzgc-a7ci

A case is considered “cleared” when it is cleared by arrest or exceptional means. Cases credited as “cleared” in a given month or year may have been opened in a previous month or year. For this reason, the clearance rate for a given period may be above 100%. For information and definitions about calculating clearance rates visit https://ucr.fbi.gov/crime-in-the-u.s/2018/crime-in-the-u.s.-2018/topic-pages/clearances

Abstract: The dataset contains a subset of locations and attributes of incidents reported in the ASAP (Analytical Services Application) crime report database by the District of Columbia Metropolitan Police Department (MPD). Visit crimecards.dc.gov for more information. This data is shared via an automated process where addresses are geocoded to the District's Master Address Repository and assigned to the appropriate street block. Block locations for some crime points could not be automatically assigned resulting in 0,0 for x,y coordinates. These can be interactively assigned using the MAR Geocoder.On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments.Purpose: On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments. This change was not applied to datasets pre-2020.Supplemental Information: All statistics presented in Crime Cards are based on preliminary DC criminal code offense definitions. The data do not represent official statistics submitted to the FBI under the Uniform Crime Reporting program (UCR) or National Incident Based Reporting System (NIBRS). All preliminary offenses are coded based on DC criminal code and not the FBI offense classifications. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. The MPD does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information. The MPD will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. Please note that changes to MPD's PSA and police district boundaries occasionally occur. The statistics provided through DC Crime Mapping Application are based on current police boundaries as of January 3, 2017. Sex Assault Data Availability: In an effort to provide more clear information about the most serious sex assaults that are most closely aligned with the public's perception of rape and attempted rape, the most serious sex abuse categories are included in the reports of DC Code Index Violent Crimes: Sex Assault. The figures reported in this category include First Degree Sex Abuse, Second Degree Sex Abuse, Attempted First Degree Sex Abuse and Assault with Intent to Commit First Degree Sex Abuse against adults. Data in this format is available online from 2011. Similar to the other offense data, the sex assault statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. Please also be aware that on Sunday, August 23, 2015, the MPD implemented a new records management system called Cobalt. The offense categories presented within this application have remained the same; however, all statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. All statistics presented in Crime Cards are based on preliminary DC Index crime data reported from 2009 up to a second before midnight today (that's 11:59:59 pm yesterday) . They are compiled based on the date the offense was reported ( Report Date) to the police department. The date and time window of the crime’s occurrence is provided in the See a detailed list… car

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.