A newer version of this project is available. See below for other available versions.
Jacob Kaplan's Concatenated Files: Uniform Crime Reporting (UCR) Program Data: Arson 1979-2021
Principal Investigator(s): View help for Principal Investigator(s) Jacob Kaplan, Princeton University
Version: View help for Version V11
Name | File Type | Size | Last Modified |
---|---|---|---|
|
application/zip | 148.5 MB | 04/02/2023 10:23:AM |
|
application/zip | 95.7 MB | 04/02/2023 10:23:AM |
|
application/zip | 17.6 MB | 04/02/2023 10:22:AM |
|
application/zip | 14.2 MB | 04/02/2023 11:54:AM |
Project Citation:
Kaplan, Jacob. Jacob Kaplan’s Concatenated Files: Uniform Crime Reporting (UCR) Program Data: Arson 1979-2021. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 2023-04-02. https://doi.org/10.3886/E103540V11
Project Description
Summary:
View help for Summary
Version 8 release notes:
For a comprehensive guide to this data and other UCR data, please see my book at ucrbook.com
Version 11 release notes:
- Adds 2021 data.
Version 10 release notes:
- Adds 2020 data.
- Please note that the FBI has retired UCR data ending in 2020 data so this will be the last arson data they release.
- Changes .rda file to .rds.
Version 9 release notes:
- Changes release notes description, does not change data.
- Adds 2019 data.
- Note that the number of months missing variable sharply changes starting in 2018. This is probably due to changes in UCR reporting of the column_2_type variable which is used to generate the months missing county (the code I used does not change). So pre-2018 and 2018+ years may not be comparable for this variable.
Version 7 release notes:
- Adds a last_month_reported column which says which month was reported last. This is actually how the FBI defines number_of_months_reported so is a more accurate representation of that. Removes the number_of_months_reported variable as the name is misleading. You should use the last_month_reported or the number_of_months_missing (see below) variable instead.
- Adds a number_of_months_missing in the annual data which is the sum of the number of times that the agency reports "missing" data (i.e. did not report that month) that month in the card_2_type variable or reports NA in that variable. Please note that this variable is not perfect and sometimes an agency does not report data but this variable does not say it is missing. Therefore, this variable will not be perfectly accurate.
Version 6 release notes:
- Adds 2018 data
Version 5 release notes:
- Adds data in the following formats: SPSS and Excel.
- Changes project name to avoid confusing this data for the ones done by NACJD.
Version 4 release notes:
Version 3 release notes:
- Add data for 2016.
- Order rows by year (descending) and ORI.
- Removed data from Chattahoochee Hills (ORI = "GA06059") from 2016 data. In 2016, that agency reported about 28 times as many vehicle arsons as their population (Total mobile arsons = 77762, population = 2754.
Version 2 release notes:
- Fix bug where Philadelphia Police Department had incorrect FIPS county code.
This Arson data set is an FBI data set that is part of the annual
Uniform Crime Reporting (UCR) Program data. This data contains
information about arsons reported in the United States. The information is the number of arsons reported, to have actually occurred, to not have occurred ("unfounded"), cleared by arrest of at least one arsoning, cleared by arrest where all offenders are under the age of 18, and the cost of the arson. This is done for a number of different arson location categories such as community building, residence, vehicle, and industrial/manufacturing structure.
The yearly data sets here combine data from the years 1979-2018 into a single
file for each group of crimes. Each monthly file is only a single year
as my laptop can't handle combining all the years together. These files
are quite large and may take some time to load. I also added state, county, and place FIPS code from the LEAIC (crosswalk).
A small number of agencies had some months with clearly incorrect data. I changed the incorrect columns to NA and left the other columns unchanged for that agency. The following are data problems that I fixed - there are still likely issues remaining in the data so make sure to check yourself before running analyses.
- Oneida, New York (ORI = NY03200) had multiple years that reported single arsons costing over $700 million. I deleted this agency from all years of data.
- In January 1989 Union, North Carolina (ORI = NC09000) reported 30,000 arsons in uninhabited single occupancy buildings and none any other months.
- In December 1991 Gadsden, Florida (ORI = FL02000) reported that a single arson at a community/public building caused $99,999,999 in damages (the maximum possible).
- In April 2017 St. Paul, Minnesota (ORI = MN06209) reported 73,400 arsons in uninhabited storage buildings and 10,000 arsons in uninhabited community/public buildings and one or fewer every other month.
When an arson is determined to be unfounded the estimated damage from that arson is added as negative to zero out the previously reported estimated damages. This occasionally leads to some agencies have negative values for arson damages. You should be cautious when using the estimated damage columns as some values are quite large. Negative values in other columns are also due to adjustments (zeroing out the error) from month to month. Negative values are not meant to be NA in this data set.
Scope of Project
Subject Terms:
View help for Subject Terms
arson;
Uniform Crime Reports;
crime;
arrests;
crime rates;
law enforcement;
fire
Geographic Coverage:
View help for Geographic Coverage
United States
Time Period(s):
View help for Time Period(s)
1979 – 2020
Methodology
Unit(s) of Observation:
View help for Unit(s) of Observation
Agency-month, agency-year
Geographic Unit:
View help for Geographic Unit
Police agency
Related Publications
Published Versions
Report a Problem
Found a serious problem with the data, such as disclosure risk or copyrighted content? Let us know.
This material is distributed exactly as it arrived from the data depositor. ICPSR has not checked or processed this material. Users should consult the investigator(s) if further information is desired.