As of April 8, 24.4 percent of special agents in the FBI were female in 2024, compared to 75.6 percent who were male. However, more women than men held careers in the FBI as professional staff or intelligence analysts. In that year, 45.9 percent of the entire FBI workforce was female. The FBI The FBI is the United States government agency that deals with national security and law enforcement. As the principal agency that deals with law enforcement, it is primarily focused on domestic issues. The FBI focuses on protecting the United States from terrorist attacks, protecting civil rights, and protecting the United States from foreign espionage and cyber-attacks. The FBI is broken down into six branches, each lead by an executive director. FBI findings As one of the most important agencies in the United States, it was estimated that the FBI spent over 8.9 billion U.S. dollars on all programs in 2020. With the goal to protect Americans domestically, it sees all different types of crime. In 2023, assault and drug and narcotic offenses were the leading reasons for arrest by the FBI. Furthermore, hate crimes have been on the rise lately in the United States, with race, ethnicity, and/or ancestry being the leading reason for hate crime arrests nationwide.

As of 2023, there were 36,945 positions for FBI personnel in the United States. This is an increase from 2017, when there were 35,194 positions for personnel in the FBI.

As of April 8, 45.9 percent of FBI employees were female, while 27.5 percent were part of a racial or ethnic minority in 2024. In comparison, only 4.7 percent of FBI employees in that year had a disability.

As of 2024, 9.1 percent of special agents working for the Federal Bureau of Investigation in the United States were Hispanic or Latino, while 5.4 percent who were Black. In comparison, 14.3 percent of FBI employees working professional careers were Black, followed by 10.6 percent who were Hispanic or Latino.

Vietnam BS: Number of Employees: FBI: Other Financial Activities data was reported at 15,952.000 Person in 2015. This records an increase from the previous number of 13,084.000 Person for 2014. Vietnam BS: Number of Employees: FBI: Other Financial Activities data is updated yearly, averaging 11,876.500 Person from Dec 2005 (Median) to 2015, with 10 observations. The data reached an all-time high of 15,952.000 Person in 2015 and a record low of 4,560.000 Person in 2005. Vietnam BS: Number of Employees: FBI: Other Financial Activities data remains active status in CEIC and is reported by General Statistics Office. The data is categorized under Global Database’s Vietnam – Table VN.S002: The Situation of Enterprises Survey: VSIC 2007: Number of Employees.

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.

Vietnam BS: Number of Employees: FBI: Insurance, Reinsure, Pension Funds data was reported at 30,688.000 Person in 2016. This records an increase from the previous number of 19,800.000 Person for 2015. Vietnam BS: Number of Employees: FBI: Insurance, Reinsure, Pension Funds data is updated yearly, averaging 22,515.000 Person from Dec 2005 (Median) to 2016, with 11 observations. The data reached an all-time high of 30,688.000 Person in 2016 and a record low of 13,466.000 Person in 2007. Vietnam BS: Number of Employees: FBI: Insurance, Reinsure, Pension Funds data remains active status in CEIC and is reported by General Statistics Office. The data is categorized under Global Database’s Vietnam – Table VN.S002: The Situation of Enterprises Survey: VSIC 2007: Number of Employees.

The Uniform Crime Reporting Program Data, Police Employee Data, 2021 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.

Vietnam BS: Number of Employees: FBI: Finacial Service Activities data was reported at 230,978.000 Person in 2015. This records an increase from the previous number of 220,858.000 Person for 2014. Vietnam BS: Number of Employees: FBI: Finacial Service Activities data is updated yearly, averaging 192,839.500 Person from Dec 2005 (Median) to 2015, with 10 observations. The data reached an all-time high of 236,006.000 Person in 2013 and a record low of 82,843.000 Person in 2005. Vietnam BS: Number of Employees: FBI: Finacial Service Activities data remains active status in CEIC and is reported by General Statistics Office. The data is categorized under Global Database’s Vietnam – Table VN.S002: The Situation of Enterprises Survey: VSIC 2007: Number of Employees.

As of 2023, there were a total of 56 FBI field offices located across the United States and Puerto Rico. Texas and California were the states with the highest number of FBI field offices, with four field offices in each state.

For a comprehensive guide to this data and other UCR data, please see my book at ucrbook.comVersion 13 release notes:Adds 2022 dataVersion 12 release notes:Adds 2021 data.Version 11 release notes:Adds 2020 data. Please note that the FBI has retired UCR data ending in 2020 data so this will (probably, I haven't seen confirmation either way) be the last LEOKA 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 data for 2019.Version 8 release notes:Fix bug for years 1960-1971 where the number of months reported variable was incorrectly down by 1 month. I recommend caution when using these years as they only report either 0 or 12 months of the year, which differs from every other year in the data. Added the variable officers_killed_total which is the sum of officers_killed_by_felony and officers_killed_by_accident.Version 7 release notes:Adds data from 2018Version 6 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 5 release notes: Adds data for 1960-1974 and 2017. Note: many columns (including number of female officers) will always have a value of 0 for years prior to 1971. This is because those variables weren't collected prior to 1971. These should be NA, not 0 but I'm keeping it as 0 to be consistent with the raw data. Removes support for .csv and .sav files.Adds a number_of_months_reported variable for each agency-year. A month is considered reported if the month_indicator column for that month has a value of "normal update" or "reported, not data."The formatting of the monthly data has changed from wide to long. This means that each agency-month has a single row. The old data had each agency being a single row with each month-category (e.g. jan_officers_killed_by_felony) being a column. Now there will just be a single column for each category (e.g. officers_killed_by_felony) and the month can be identified in the month column. This also results in most column names changing. As such, be careful when aggregating the monthly data since some variables are the same every month (e.g. number of officers employed is measured annually) so aggregating will be 12 times as high as the real value for those variables. Adds a date column. This date column is always set to the first of the month. It is NOT the date that a crime occurred or was reported. It is only there to make it easier to create time-series graphs that require a date input.All the data in this version was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. Data is the same as from NACJD but using all FBI files makes cleaning easier as all column names are already identical. Version 4 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 3 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The LEOKA data sets contain highly detailed data about the number of officers/civilians employed by an agency and how many officers were killed or assaulted. All the data was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. About 7% of all agencies in the data report more officers or civilians than population. As such, I removed the officers/civilians per 1,000 population variables. You should exercise caution if deciding to generate and use these variables yourself. Several agency had impossible large (>15) officer deaths in a single month. For those months I changed the value to NA. The UCR Handbook (https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view) describes the LEOKA data as follows:"The UCR Program collects data from all contributing agencies ... on officer line-of-duty deaths and assaults. Reporting agencies must submit data on ... their own duly sworn officers feloniously or accidentally killed or assaulted in the line of duty. The purpose of this data collect

All the data was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files.

About 7% of all agencies in the data report more officers or civilians than population. As such, I removed the officers/civilians per 1,000 population variables. You should exercise caution if deciding to generate and use these variables yourself.

Several agency had impossible large (>15) officer deaths in a single month. For those months I changed the value to NA. See the R code for a complete list.

For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data">https://github.com/jacobkap/crime_data.

The UCR Handbook (https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view">https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view) describes the LEOKA data as follows:

"The UCR Program collects data from all contributing agencies ... on officer line-of-duty deaths and assaults. Reporting agencies must submit data on ... their own duly sworn officers feloniously or accidentally killed or assaulted in the line of duty. The purpose of this data collection is to identify situations in which officers are killed or assaulted, describe the incidents statistically, and publish the data to aid agencies in developing policies to improve offic

This statistics shows the share of people in the U.S. who agree with the perceptions that Trump fired Comey due to the FBI investigations into Trump's administration's links to Russia and the Clinton email scandal, as of May 2017. According to the survey, 31 percent of people believed that Trump fired Comey in order to slow down the investigation into his administration's ties to Russia.

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.

The UNIFORM CRIME REPORTING PROGRAM DATA: SUPPLEMENTARY HOMICIDE REPORTS, 2020 (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 statistic shows the share of adults in the United States who think it is likely that the claim of the intelligence agencies that Russia attempted to interfere with the U.S. 2016 presidential election is correct, as of March 4th, 2017. In March 2017, 32 percent of Americans thought it was extremely likely that the reports were correct.

Version 5 release notes: Adds data for 1960-1974 and 2017. Note: many columns (including number of female officers) will always have a value of 0 for years prior to 1971.Removes support for .csv and .sav files.Adds a number_of_months_reported variable for each agency-year. A month is considered reported if the month_indicator column for that month has a value of "normal update" or "reported, not data."The formatting of the monthly data has changed from wide to long. This means that each agency-month has a single row. The old data had each agency being a single row with each month-category (e.g. jan_officers_killed_by_felony) being a column. Now there will just be a single column for each category (e.g. officers_killed_by_felony) and the month can be identified in the month column. This also results in most column names changing. As such, be careful when aggregating the monthly data since some variables are the same every month (e.g. number of officers employed is measured annually) so aggregating will be 12 times as high as the real value for those variables. Adds a date column. This date column is always set to the first of the month. It is NOT the date that a crime occurred or was reported. It is only there to make it easier to create time-series graphs that require a date input.All the data in this version was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. Data is the same as from NACJD but using all FBI files makes cleaning easier as all column names are already identical. Version 4 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 3 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The LEOKA data sets contain highly detailed data about the number of officers/civilians employed by an agency and how many officers were killed or assaulted. All the data was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. About 7% of all agencies in the data report more officers or civilians than population. As such, I removed the officers/civilians per 1,000 population variables. You should exercise caution if deciding to generate and use these variables yourself. Several agency had impossible large (>15) officer deaths in a single month. For those months I changed the value to NA. See the R code for a complete list. For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data.The UCR Handbook (https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view) describes the LEOKA data as follows:"The UCR Program collects data from all contributing agencies ... on officer line-of-duty deaths and assaults. Reporting agencies must submit data on ... their own duly sworn officers feloniously or accidentally killed or assaulted in the line of duty. The purpose of this data collection is to identify situations in which officers are killed or assaulted, describe the incidents statistically, and publish the data to aid agencies in developing policies to improve officer safety."... agencies must record assaults on sworn officers. Reporting agencies must count all assaults that resulted in serious injury or assaults in which a weapon was used that could have caused serious injury or death. They must include other assaults not causing injury if the assault involved more than mere verbal abuse or minor resistance to an arrest. In other words, agencies must include in this section all assaults on officers, whether or not the officers sustained injuries."If you have any questions, comments, or suggestions please contact me at jkkaplan6@gmail.com

This statistic shows the share of Americans concerned about contact between the Trump campaign and Russia in 2019. During the survey, 22 percent of respondents reported that they were not at all concerned about inappropriate contacts between Donald Trump or others involved with his campaign and the Russian government.

The ICE Security Program Office (SEC) safeguards people, information, and facilities through comprehensive and integrated programs encompassing threat management and personnel, physical, information, and administrative security. During FY 2022, OPR’s Personnel Security Division (PSD) began enrolling all personnel in national security positions into the Federal Bureau of Investigation (FBI) Rap Back, which ensures employees’ fingerprints are continuously compared with criminal history and civil records. Enrollment into FBI Rap Back is a Trusted Workforce certification requirement, and in FY 2022, PSD was able to enroll 35% of personnel occupying national security positions. Additionally, SEC conducted 334 polygraph examinations of entry level law enforcement officers and 196 insider threat assessments.

The National Incident-Based Reporting System (NIBRS) is a part of the Uniform Crime Reporting Program (UCR), administered by the Federal Bureau of Investigation (FBI). In the late 1970s, the law enforcement community called for a thorough evaluative study of the UCR with the objective of recommending an expanded and enhanced UCR program to meet law enforcement needs into the 21st century. The FBI fully concurred with the need for an updated program to meet contemporary needs and provided its support, formulating a comprehensive redesign effort. Following a multiyear study, a "Blueprint for the Future of the Uniform Crime Reporting Program" was developed. Using the "Blueprint," and in consultation with local and state law enforcement executives, the FBI formulated new guidelines for the Uniform Crime Reports. The National Incident-Based Reporting System (NIBRS) was implemented to meet these guidelines. NIBRS data are archived at ICPSR as 11 separate data files per year, which may be merged by using linkage variables. Prior to 2013 the data were archived and distributed as 13 separate data files, including three separate batch header record files. Starting with the 2013 data, the FBI combined the three batch header files into one file. Consequently, ICPSR instituted new file numbering for the data. NIBRS data focus on a variety of aspects of a crime incident. Part 2 (formerly Part 4), Administrative Segment, offers data on the incident itself (date and time). Each crime incident is delineated by one administrative segment record. Also provided are Part 3 (formerly Part 5), Offense Segment (offense type, location, weapon use, and bias motivation), Part 4 (formerly Part 6), Property Segment (type of property loss, property description, property value, drug type and quantity), Part 5 (formerly Part 7), Victim Segment (age, sex, race, ethnicity, and injuries), Part 6 (formerly Part 8), Offender Segment (age, sex, and race), and Part 7 (formerly Part 9), Arrestee Segment (arrest date, age, sex, race, and weapon use). The Batch Header Segment (Part 1, formerly Parts 1-3) separates and identifies individual police agencies by Originating Agency Identifier (ORI). Batch Header information, which is contained on three records for each ORI, includes agency name, geographic location, and population of the area. Part 8 (formerly Part 10), Group B Arrest Report Segment, includes arrestee data for Group B crimes. Window Segments files (Parts 9-11, formerly Parts 11-13) pertain to incidents for which the complete Group A Incident Report was not submitted to the FBI. In general, a Window Segment record will be generated if the incident occurred prior to January 1 of the previous year or if the incident occurred prior to when the agency started NIBRS reporting. As with the UCR, participation in NIBRS is voluntary on the part of law enforcement agencies. The data are not a representative sample of crime in the United States.