NIBRS 2023.0 Technical Specification
U. S. Department of Justice
Federal Bureau of Investigation
Criminal Justice Information Services Division
Criminal Justice Information Services Division
Uniform Crime Reporting Program
2023.0
National Incident-Based Reporting System
Technical Specification
6/30/2023
Prepared by:
Criminal Justice Information Services Division
Law Enforcement Engagement and Data Sharing Section
Crime and Law Enforcement Statistics Unit
CHANGE DESCRIPTION FORM
Revision Change Description Date
1.0 UCRRP Initial Release 04/16/2012
Attaching CJIS Template and
1.0 08/27/2013
formatting.
2015 Bias Motivation Code
1.1 09/17/2014
Additions
2.0 See Appendix for all new changes 07/10/2015
2.0 Edit/format to CJIS Template 10/16/2015
2.0 Review for Security 10/27/2015
2.0 Adjustments from Security 10/28/2015
2.1 Correction of Missing Information 11/03/2015
Edit/format correction to CJIS
2.1 11/03/2015
template
Business rules updates, 7/18/2016
3.0
verification, and formatting 8/15/2015
3.1 Technical Changes 1/09/2017
Alignment with user manual
3.2 8/30/2017
(version 2.0).
2019.0 2019 Additions 03/22/2018
2019.1 UCR-TR Modifications 06/30/2018
Inclusion of new offenses
(reported by federal and tribal
LEAs only), Judicial Districts and
2019.2 reconciliation with UCR Tech 05/15/2020
Refresh system processing.
Additional updates as noted in the
Change Description Details below.
Correction to the alignment of
2019.2.1 Data Structure Errors Table and 06/15/2020
Change Description Details.
2023.0 UCR Modifications 6/30/2023
6/30/2023 2023.0 NIBRS Technical Specification 1
6/30/2023 2023.0 NIBRS Technical Specification 2
VERSION 2023.0 CHANGE DESCRIPTION DETAILS
Section or Table Change Description
Updated information for file naming convention and added a note
Section 1
about the rejection of file names with blank spaces.
Section 2.2.1.1 Updated the Line Length to 91 for Federal Agency Reporting
Only—Judicial District Code and noted that the Line Length will
exceed the Segment Length of 0088. (Positions for Federal Judicial
District Code were already included in the Segment Layout
Diagram.)
Section 6.1 Added line length to 0091 (Federal Agency Reporting Only -
Judicial District Code) and added note that Federal Agency Line
Length will be 91, however 0088 for Segment Length.
Updated the Line Length to 69 for Federal Agency Reporting
Only—Judicial District Code and noted that the Line Length will
Section 2.3.1 exceed the Segment Length of 0066. (Positions were already
included in the Segment Layout Diagram.)
Section 6.7 Added line length to 0066 (Federal Agency Reporting Only -
Judicial District Code) and added note that Federal Agency Line
Length will be 69, however 0066 for Segment Length.
Updated Anti-Mormon to the Anti-Church of Jesus Christ in Data
Section 3.3.3.4
Values.
Updated the list of offenses to include Federal Offenses that
Section 3.3.4.1
make the reporting of the Type Property Loss/Etc., mandatory.
Updated the Edits for Data Element 34 to specify the data
Section 3.3.5.15 element is mandatory for Crimes Against Property in the instance
of Robbery.
Table 3-2 Updated Robbery to replace Crimes Against Property for Error
Table 5-2 085.
Removed following language from Error 470: “However, there
Table 3-2
may be some situations where only one of the victims is also the
Table 3-51
offender, but where the other victim(s) is not also the
Table 5-6
offender(s).”
Table 3-2
Table 3-54 Removed NIBRS Error 560.
Table 5-8
Table 3-11
Table 3-15 Removed NIBRS Error 173.
Table 5-3
Table 5-4 Added Tribal Agencies to the Error Message for Error 250.
Changed Money Laundering from a Crime Against Property to a
Appendix A
Crime Against Society.
Appendix A.2 Removed Peeping Tom, Bad Checks, and Drunkenness.
Changed Attempted to Completed in #1, removed previous
Appendix E, information about when the offender sequence number is
subsection E, 3 unknown (formerly in #4), and renumbered remaining
information.
6/30/2023 2023.0 NIBRS Technical Specification 3
Appendix E,
Changed False to Completed in #3.
subsection E, 4
Appendix E, Changed Completed to Attempted in #5, removed illogical
subsection E, 5 property types from #7 and renumbered remaining information.
Appendix E,
Removed the word “Indicator” from #2 and #3.
subsection E, 11
Appendix E,
Removed the word “Indicator” from #4.
subsection E, 14
Updated #3 to note the Type of Victim of Law Enforcement
Officer can only be reported with the offense of Murder and
Nonnegligent Manslaughter.
Appendix E, Added information to #4 to note if the Reporting Agency’s ORI
subsection E, 18 differs from the ORI of the Officer’s regular jurisdiction, then it
must be reported.
Combined relevant information from #7 and #10 about Justifiable
Homicide in #7 and renumbered remaining information.
Appendix E, Added “If” to #3 to specify “if Type of Victim” is Individual, then
subsection E, 26 the Type Injury must be reported.
Removed duplicate language and renumbered relevant
Appendix E,
information in #6 and also removed previous information about
subsection E, 27
when the offender sequence number is unknown.
Removed duplicate language in #3 and removed #4, which was
Appendix E,
information about when the offender sequence number is
subsection E, 28
unknown.
Combined relevant information from #3-#5 concerning the
Appendix E,
Government as the Type of Victim for federal offenses and
subsection E, 32
renumbered remaining information.
6/30/2023 2023.0 NIBRS Technical Specification 4
TABLE OF CONTENTS
1 Background ......................................................................................................................... 12
2 Incident Reports .................................................................................................................. 14
2.1 Header Data Elements................................................................................................... 14
2.2 Group A Incident Reports ............................................................................................. 15
2.2.1 Level 1–Administrative Segment ............................................................................. 15
Administrative Segment Layout (Level 1) ...................................................... 16
2.2.2 Level 2–Offense Segment ......................................................................................... 16
Offense Segment Layout (Level 2) ................................................................. 17
2.2.3 Level 3–Property Segment ........................................................................................ 17
Property Segment Layout (Level 3) ................................................................ 18
2.2.4 Level 4–Victim Segment .......................................................................................... 18
Victim Segment Layout (Level 4) ................................................................... 19
2.2.5 Level 5–Offender Segment ....................................................................................... 19
Offender Segment Layout (Level 5) ................................................................ 20
2.2.6 Level 6–Arrestee Segment ........................................................................................ 20
Arrestee Segment Layout (Level 6)................................................................. 21
2.3 Level 7–Group B Arrest Report Segment ..................................................................... 21
2.3.1 Group B Arrest Report Segment Layout (Level 7) ................................................... 22
2.4 Level 0–Zero Report Segment ...................................................................................... 22
2.4.1 Zero Report Segment Layout (Level 0) .................................................................... 23
3 Data Element Definitions ................................................................................................... 24
3.1 Data Elements ............................................................................................................... 24
3.2 Data Values ................................................................................................................... 24
3.3 Data Element Descriptions ........................................................................................... 24
3.3.1 Header Data Elements............................................................................................... 25
Segment Length ............................................................................................... 25
Segment Level ................................................................................................. 26
Segment Action Type ...................................................................................... 31
Month of Submission....................................................................................... 32
Year of Submission ......................................................................................... 33
City Indicator ................................................................................................... 33
3.3.2 Administrative Segment............................................................................................ 34
Data Element 1-ORI ........................................................................................ 34
Data Element 1A-Federal Judicial District (JD) [Federal Submissions Only] 35
Data Element 2-Incident Number .................................................................... 37
Data Element 2A-Cargo Theft ......................................................................... 39
Data Element 3-Incident Date ......................................................................... 40
Data Element 3-Report Date Indicator ............................................................ 42
6/30/2023 2023.0 NIBRS Technical Specification 5
Data Element 3-Incident Hour ......................................................................... 42
Data Element 4-Cleared Exceptionally ........................................................... 43
Data Element 5-Exceptional Clearance Date .................................................. 44
3.3.3 Offense Segment ....................................................................................................... 45
Data Element 6-UCR Offense Code ................................................................ 46
Data Element 7-Offense Attempted/Completed .............................................. 47
Data Element 8-Offender Suspected of Using ................................................ 48
Data Element 8A-Bias Motivation .................................................................. 49
Data Element 9-Location Type........................................................................ 51
Data Element 10-Number of Premises Entered ............................................... 53
Data Element 11-Method of Entry .................................................................. 54
Data Element 12-Type Criminal Activity/Gang Information.......................... 55
Data Element 13-Type Weapon/Force Involved ............................................. 58
Data Element 13-Automatic Weapon Indicator .............................................. 61
3.3.4 Property Segment ...................................................................................................... 62
Data Element 14-Type Property Loss/Etc. ...................................................... 62
Data Element 15-Property Description............................................................ 72
3.3.4.2.1 Illogical Property Description for the Offense(s) Submitted ...................... 76
Data Element 16-Value of Property ................................................................ 78
Data Element 17-Date Recovered ................................................................... 80
Data Element 18-Number of Stolen Motor Vehicles ...................................... 81
Data Element 19-Number of Recovered Motor Vehicles ............................... 82
Data Element 20-Suspected Drug Type .......................................................... 83
Data Element 21-Estimated Drug Quantity ..................................................... 86
Data Element 22-Type Drug Measurement ..................................................... 87
3.3.5 Victim Segment ........................................................................................................ 89
Data Element 23-Victim Sequence Number ................................................... 89
Data Element 24-Victim Connected to UCR Offense Code ........................... 90
Data Element 25-Type of Victim .................................................................... 94
Data Element 25A-Type of Officer Activity/Circumstance ............................ 96
Data Element 25B-Officer Assignment Type ................................................. 97
Data Element 25C-Officer-ORI Other Jurisdiction ......................................... 98
Data Element 26-Age of Victim ...................................................................... 98
Data Element 27-Sex of Victim..................................................................... 100
Data Element 28-Race of Victim................................................................... 101
Data Element 29-Ethnicity of Victim ............................................................ 101
Data Element 30-Resident Status of Victim .................................................. 102
Data Element 31-Aggravated Assault/Homicide Circumstances .................. 102
Data Element 32-Additional Justifiable Homicide Circumstances ............... 104
Data Element 33-Type Injury ........................................................................ 105
Data Element 34-Offender Number to be Related ........................................ 107
Data Element 35-Relationship of Victim to Offender ................................... 108
3.3.6 Offender Segment ................................................................................................... 110
6/30/2023 2023.0 NIBRS Technical Specification 6
Data Element 36-Offender Sequence Number .............................................. 111
Data Element 37-Age of Offender................................................................. 112
Data Element 38-Sex of Offender ................................................................. 113
Data Element 39-Race of Offender ............................................................... 114
Data Element 39A-Ethnicity of Offender ...................................................... 115
3.3.7 Arrestee Segment/Group B Arrest Report Segment ............................................... 115
Data Element 40-Arrestee Sequence Number ............................................... 116
Data Element 41-Arrest Transaction Number ............................................... 116
Data Element 42-Arrest Date ........................................................................ 117
Data Element 43-Type of Arrest ................................................................... 119
Data Element 44-Multiple Arrestee Segments Indicator ............................... 119
Data Element 45-UCR Arrest Offense Code ................................................. 120
Data Element 46-Arrestee Was Armed With ................................................ 121
Data Element 46-Automatic Weapon Indicator ............................................ 122
Data Element 47-Age of Arrestee ................................................................. 123
Data Element 48-Sex of Arrestee .................................................................. 124
Data Element 49-Race of Arrestee ................................................................ 125
Data Element 50-Ethnicity of Arrestee ......................................................... 125
Data Element 51-Resident Status of Arrestee ............................................... 126
Data Element 52-Disposition of Arrestee Under 18 ...................................... 127
3.3.8 Zero Report Segment .............................................................................................. 127
Data Element (unnumbered)-Zero Report Month ......................................... 128
Data Element (unnumbered)-Zero Report Year ............................................ 129
4 Submission Specifications ................................................................................................ 130
4.1 Segment Length .......................................................................................................... 130
4.2 Data Records Must Be Initialized to Blanks ............................................................... 130
4.3 Codes Must Be Right-Justified With Zero Left-Fill ................................................... 130
4.4 Victim/Offender/Arrestee Sequence Numbers Can Have Gaps ................................. 130
4.5 Segment Levels ........................................................................................................... 130
4.6 Segment Action Types ................................................................................................ 131
4.6.1 I = Incident Report .................................................................................................. 131
4.6.2 A = Add .................................................................................................................. 131
4.6.3 D = Delete ............................................................................................................... 132
4.7 Zero Reporting ............................................................................................................ 133
5 Errors ................................................................................................................................. 134
5.1 Error Data Set ............................................................................................................. 134
5.2 Error Numbers and Messages ..................................................................................... 135
5.2.1 Structure Check Errors ............................................................................................ 136
5.2.2 Administrative Segment Errors............................................................................... 151
5.2.3 Offense Segment Errors .......................................................................................... 155
5.2.4 Property Segment Errors ......................................................................................... 163
5.2.5 Victim Segment Errors ........................................................................................... 171
5.2.6 Offender Segment Errors ........................................................................................ 182
5.2.7 Arrestee Segment Errors ......................................................................................... 184
5.2.8 Group B Arrest Report Segment Errors .................................................................. 188
6/30/2023 2023.0 NIBRS Technical Specification 7
5.2.9 Zero Report Segment Errors ................................................................................... 192
5.2.10 Data Quality Checks ............................................................................................. 193
6 Record Layouts ................................................................................................................. 202
6.1 Administrative Segment Layout (Level 1) ................................................................. 202
6.2 Offense Segment Layout (Level 2) ............................................................................. 203
6.3 Property Segment Layout (Level 3) ............................................................................ 204
6.4 Victim Segment Layout (Level 4) .............................................................................. 205
6.5 Offender Segment Layout (Level 5) ........................................................................... 206
6.6 Arrestee Segment Layout (Level 6) ............................................................................ 207
6.7 Group B Arrest Report Segment Layout (Level 7) ..................................................... 208
6.8 Zero Report Segment Layout (Level 0) ...................................................................... 209
6.9 EDS Layout ................................................................................................................. 209
6.10 WDS Layout ............................................................................................................... 210
Offense Codes ................................................................................ A-1
Summary of Federal Additions ....................................................... B-1
Pre-NIBRS Incidents ...................................................................... C-1
Time-Window Submissions ........................................................... D-1
Mandatories......................................................................................E-1
Legacy Time-Window Errors .......................................................... F-1
6/30/2023 2023.0 NIBRS Technical Specification 8
LIST OF TABLES
Table 3-1 Segment Length Edit Description ................................................................................ 25
Table 3-2 Segment Level Edit Description................................................................................... 26
Table 3-3 Segment Action Type Edit Description ........................................................................ 31
Table 3-4 Month of Submission Edit Description ........................................................................ 32
Table 3-5 Year of Submission Edit Description ........................................................................... 33
Table 3-6 City Indicator Edit Description .................................................................................... 34
Table 3-7 ORI Edit Description .................................................................................................... 34
Table 3-8 Judicial District Edit Description ................................................................................ 35
Table 3-9 Incident Number Edit Description............................................................................... 38
Table 3-10 Cargo Theft Edit Description .................................................................................... 39
Table 3-11 Incident Date Edit Description .................................................................................. 41
Table 3-12 Report Date Indicator Edit Description ...................................................................... 42
Table 3-13 Incident Hour Edit Description .................................................................................. 43
Table 3-14 Cleared Exceptionally Edit Description ..................................................................... 43
Table 3-15 Exceptional Clearance Date Edit Description ............................................................ 44
Table 3-16 UCR Offense Code Edit Description ......................................................................... 46
Table 3-17 Offense Attempted/Completed Edit Description........................................................ 48
Table 3-18 Offender Suspected of Using Edit Description .......................................................... 49
Table 3-19 Bias Motivation Edit Description ............................................................................... 50
Table 3-20 Location Type Edit Description ................................................................................. 52
Table 3-21 Number of Premises Entered Edit Description .......................................................... 54
Table 3-22 Method of Entry Edit Description .............................................................................. 54
Table 3-23 Type Criminal Activity/Gang Information Edit Description ..................................... 56
Table 3-24 Type Weapon/Force Involved Edit Description ......................................................... 59
Table 3-25 Automatic Weapon Indicator Edit Description .......................................................... 62
Table 3-26 Type Property Loss/Etc. Edit Description .................................................................. 63
Table 3-27 Property Description Edit Description ....................................................................... 73
Table 3-28 Illogical Property Description by Offense .................................................................. 76
Table 3-29 Value of Property Edit Description ............................................................................ 79
Table 3-30 Date Recovered Edit Description ............................................................................... 81
Table 3-31 Number of Stolen Motor Vehicles Edit Description .................................................. 82
Table 3-32 Number of Recovered Motor Vehicles Edit Description ........................................... 83
Table 3-33 Suspected Drug Type Edit Description ...................................................................... 84
Table 3-34 Estimated Drug Quantity Edit Description................................................................. 87
Table 3-35 Type Drug Measurement Edit Description................................................................. 88
Table 3-36 Victim Sequence Number Edit Description ............................................................... 90
Table 3-37 Victim Connected to UCR Offense Code Edit Description ....................................... 91
Table 3-38 Type of Victim Edit Description ................................................................................ 94
Table 3-39 Type of Officer Activity/Circumstance Edit Description .......................................... 96
Table 3-40 Officer Assignment Type Edit Description ................................................................ 97
Table 3-41 Jurisdiction Edit Description ...................................................................................... 98
Table 3-42 Age of Victim Edit Description.................................................................................. 99
Table 3-43 Sex of Victim Edit Description ................................................................................ 100
Table 3-44 Race of Victim Edit Description .............................................................................. 101
6/30/2023 2023.0 NIBRS Technical Specification 9
Table 3-45 Ethnicity of Victim Edit Description........................................................................ 102
Table 3-46 Resident Status of Victim Edit Description ............................................................. 102
Table 3-47 Aggravated Assault/Homicide Circumstances Edit Description .............................. 103
Table 3-48 Additional Justifiable Homicide Circumstances Edit Description ........................... 105
Table 3-49 Type of Injury Edit Description ............................................................................... 106
Table 3-50 Offender Number to be Related Edit Description .................................................... 108
Table 3-51 Relationship of Victim to Offender Edit Description............................................... 109
Table 3-52 Offender Sequence Number Edit Description .......................................................... 111
Table 3-53 Age of Offender Edit Description ............................................................................ 112
Table 3-54 Sex of Offender Edit Description ............................................................................. 113
Table 3-55 Race of Offender Edit Description ........................................................................... 114
Table 3-56 Ethnicity of Offender Edit Description .................................................................... 115
Table 3-57 Arrestee Sequence Number Edit Description ........................................................... 116
Table 3-58 Arrest Transaction Number Edit Description ........................................................... 117
Table 3-59 Arrest Date Edit Description .................................................................................... 118
Table 3-60 Type of Arrest Edit Description ............................................................................... 119
Table 3-61 Multiple Arrestee Segments Indicator Edit Description .......................................... 120
Table 3-62 UCR Arrest Offense Code Edit Description ............................................................ 121
Table 3-63 Arrestee Was Armed With Edit Description ............................................................ 122
Table 3-64 Automatic Weapon Indicator Edit Description ........................................................ 123
Table 3-65 Age of Arrestee Edit Description ............................................................................. 124
Table 3-66 Sex of Arrestee Edit Description .............................................................................. 125
Table 3-67 Race of Arrestee Edit Description ............................................................................ 125
Table 3-68 Ethnicity of Arrestee Edit Description ..................................................................... 126
Table 3-69 Resident Status of Arrestee Edit Description ........................................................... 126
Table 3-70 Disposition of Arrestee Under 18 Edit Description ................................................. 127
Table 3-71 Zero Report Month Edit Description ........................................................................ 128
Table 3-72 Zero Report Year Edit Description........................................................................... 129
Table 5-1 EDS Record Layout .................................................................................................... 134
Table 5-2 Structure Check Errors ............................................................................................... 136
Table 5-3 Administrative Segment Errors .................................................................................. 151
Table 5-4 Offense Segment Errors ............................................................................................. 155
Table 5-5 Property Segment Errors ............................................................................................ 163
Table 5-6 Victim Segment Errors ............................................................................................... 171
Table 5-7 Mutually Exclusive Offenses for Error Code 478 Chart ............................................ 181
Table 5-8 Offender Segment Errors ............................................................................................ 182
Table 5-9 Arrestee Segment Errors............................................................................................. 184
Table 5-10 Group B Arrest Report Segment Errors ................................................................... 188
Table 5-11 Zero Report Segment Errors ..................................................................................... 192
6/30/2023 2023.0 NIBRS Technical Specification 10
LIST OF FIGURES
Figure 2-1 Administrative Segment Layout (Level 1).................................................................. 16
Figure 2-2 Offense Segment Layout (Level 2) ............................................................................. 17
Figure 2-3 Property Segment Layout (Level 3) ............................................................................ 18
Figure 2-4 Victim Segment Layout (Level 4)............................................................................... 19
Figure 2-5 Offender Segment Layout (Level 5) ........................................................................... 20
Figure 2-6 Arrestee Segment Layout (Level 6) ............................................................................ 21
Figure 2-7 Group B Arrest Report Segment Layout (Level 7) ..................................................... 22
Figure 2-8 Zero Report Segment Layout (Level 0) ...................................................................... 23
Figure 6-1 Administrative Segment Layout (Level 1)................................................................ 202
Figure 6-2 Offense Segment Layout (Level 2) ........................................................................... 203
Figure 6-3 Property Segment Layout (Level 3) .......................................................................... 204
Figure 6-4 Victim Segment Layout (Level 4)............................................................................. 205
Figure 6-5 Offender Segment Layout (Level 5) ......................................................................... 206
Figure 6-6 Arrestee Segment Layout (Level 6) .......................................................................... 207
Figure 6-7 Group B Arrest Report Segment Layout (Level 7) ................................................... 208
Figure 6-8 Zero Report Segment Layout (Level 0) .................................................................... 209
Figure 6-9 EDS Layout ............................................................................................................... 209
Figure 6-10 WDS Layout............................................................................................................ 210
6/30/2023 2023.0 NIBRS Technical Specification 11
1 BACKGROUND
This National Incident-Based Reporting System (NIBRS) Technical Specification has been
developed in accordance with the Federal Bureau of Investigation’s (FBI’s) UCR Program. The
UCR system will support the FBI’s ability to collect, analyze, and report on national crime
statistics.
The UCR system includes functionality to process NIBRS data submitted in Extensible Markup
Language (XML) format. However, to minimize impacts on law enforcement agencies (LEAs)
that participate in the FBI’s UCR Program, the UCR system will continue to accept data
submissions in the legacy NIBRS flat-file formats. This specification captures the requirements
for the legacy NIBRS position-based flat-file format in alignment with technical aspects and
documentation identified below:
• NIBRS Volume 1: Data Collection Guidelines, August 2000
• NIBRS Volume 2: Data Submission Specifications, November 2001
• NIBRS Volume 4: Error Message Manual, December 1999
• NIBRS Addendum for Submitting Cargo Theft Data, January 2010
• NIBRS Addendum for Submitting Law Enforcement Officers Killed and Assaulted
(LEOKA) Data, October 2002
• NIBRS Addendum for Submitting Additional Location and Property Data Values,
March 2010
• UCR State Program Bulletins, 1999–2013
• UCR Program Quarterly 2014-present
The new UCR system will be able to accept data that is more than two years old, thus
eliminating the need for window submissions. If you are upgrading or modifying your Records
Management System (RMS), do not code for Windows Submissions. The system will still accept
Window Submissions; however, the optimal way to submit is to delete the old incident first then
add the new incident with all of the updated information. Some of the information captured in
the documents referenced above has not been included in this specification since it pertains to
policy and user training and not to the technical implementation of a NIBRS system. This policy
and training-related information will be included in the NIBRS User Manual.
To ensure consistency with the data submissions, enhance efficiency, and decrease the time to
process the submitted files from the states, the FBI’s UCR Program has implemented a new file
naming convention that all flat file submissions must adhere to. Below is the new file naming
standard, an example (void of blank spaces), and the new naming convention defined.
Submitter ID 4 digit year 2 digit month 2 digit day submission format additional information
from the state series number
Example: TXUCR0001_20230622_NIBRS_011.txt or TXUCR0001_20210601_
SRS_ARSON_006.txt
SubmitterID = Submitting Agency Identifier or ORI
Date = the date the submission was generated
Submission format is either NIBRS or SRS (Summary Reporting System)
Additional Information: Hate Crime, Cargo Theft, Arson, Homicide, etc.
6/30/2023 2023.0 NIBRS Technical Specification 12
Series Number = number of submission per year, 001 indicates the first submission of the year
NOTE: File names with blank spaces present will NOT process, instead those submissions will
be rejected and require resubmittal utilizing the mandatory naming convention.
6/30/2023 2023.0 NIBRS Technical Specification 13
2 INCIDENT REPORTS
Agencies submit Incident Reports to the FBI using up to eight distinct records, each of which is
referred to as a “segment.” The 58 numbered data elements and 11 structural data elements
comprising the NIBRS data structure have been grouped into these segment levels and are
referred to as Levels 0–7. These segments are the mechanism by which agencies report NIBRS
data to the FBI.
The segment levels are as follows:
• Level 1–Administrative Segment
• Level 2–Offense Segment
• Level 3–Property Segment
• Level 4–Victim Segment
• Level 5–Offender Segment
• Level 6–Arrestee Segment
• Level 7–Group B Arrest Report Segment
• Level 0–Zero Report Segment
An incident report may consist of many possible combinations of circumstances ranging from
one simple offense, victim, and offender situation to a complex set of multiple offenses, property
loss, victims, offenders, and arrestees. Additionally, each of the victims may not be involved in
each of the offenses. In other words, one, some, or all of the victims may be connected to each
applicable offense.
There are two categories of offenses reported in the NIBRS: Group A and Group B. It is
important to determine which category an offense belongs to because the reporting requirements
for Group A and Group B reports are different. Group A offenses must include relevant incident
data represented in multiple segments (Administrative, Offense, Property, Victim, Offender, and
Arrestee); Group B offenses include only arrest data. 6.10Appendix A: Offense Codes provides a
listing of the offenses that fall under Group A or Group B.
Agencies should submit Incident Reports for all incidents committed within an agency’s
jurisdiction.
2.1 Header Data Elements
Header data elements indicate the type of data in a submission. They appear at the beginning of
each segment level to identify the segment and indicate the processing action required, as well as
to connect all of an agency’s data to a particular submission. These header data elements are:
• Segment Length
• Segment Level
• Segment Action Type
• Month of Submission
• Year of Submission
• City Indicator (Applicable only to direct reports)
Segment Length-Positions 1 through 4 contains the Record Descriptor Word (RDW) which is the
binary length of each segment. Each segment has variable lengths depending upon the segment.
6/30/2023 2023.0 NIBRS Technical Specification 14
The RDW is the length of the actual data set plus the beginning RDW. References to each
Segment Layout Section are:
Administrative Segment Layout (Level 1)
Offense Segment Layout (Level 2)
Property Segment Layout (Level 3)
Victim Segment Layout (Level 4)
Offender Segment Layout (Level 5)
Arrestee Segment Layout (Level 6)
Segment Level-Position 5 of each record (segment) will identify the segment level being
submitted.
Segment Action Type-Position 6 of each record (segment) will identify the action type being
submitted.
2.2 Group A Incident Reports
At a minimum, each Group A Incident Report will contain four (4) of the six (6) segment levels
(Administrative, Offense, Property, Victim, Offender, and Arrestee). Depending on circumstance
and rules contained within this document, a report may contain multiple segment levels of the
same type. Within each segment level, level specific data elements must be provided in the
report. The segment levels are described below.
2.2.1 Level 1–Administrative Segment
The Administrative Segment is the master segment. Only one Administrative Segment will be
accepted per Group A Incident Report. The Data Edit (Error 075) requires that each incident
report contain Segments 1, 2, 4, and 5. All other incident data relating to offenses, property,
victims, offenders, and arrestees are contained in the other segments that are linked to the
Administrative Segment by Data Element 1 (ORI) and Data Element 2 (Incident Number).
The data elements used in the Administrative Segment are:
Data Element 1-ORI
Data Element 1A-Judicial District* (federal and tribal agency reporting only)
Data Element 2-Incident Number
Data Element 2A-Cargo Theft
Data Element 3-Incident Date
Data Element 3-Report Date Indicator
• Only required if incident date is unknown, otherwise Report Date Indicator should be
blank
Data Element 3-Incident Hour
Data Element 4-Cleared Exceptionally
Data Element 5-Exceptional Clearance Date
Exceptional Clearance Offense Code-Place Holder (Deprecated)
6/30/2023 2023.0 NIBRS Technical Specification 15
Administrative Segment Layout (Level 1)
Segment Length: 0087 (without Cargo Theft)
0088 (with Cargo Theft)
0088 (Federal Agency Reporting Only - Judicial District Code)
*NOTE: The Line Length for Federal Agency will be 91 characters
long; however, the Segment Length in the transaction will be 0088.
SEGMENT INCIDENT
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2)
1-4 5 6 7-8 9-12 13-16 17-25 26-37
DATA ELEMENT 3 INCLUDES 3 ELEMENTS
REPORT EXCEPTIONAL
INCIDENT DATE INCIDENT CLEARED CLEARANCE
DATE INDICATOR HOUR EXCEPTIONALLY DATE
(3) (3) (3) (4) (5)
38-45 46 47-48 49 50-57
FEDERAL
AGENCY
EXCEPTIONAL CLEARANCE OFFENSE CODE OCCURS 10 REPORTING
TIMES OPTIONAL ONLY
EXCEPTIONAL FEDERAL
EXCEPTIONAL CLEARANCE CARGO JUDICIAL
CLEARNCE THROUGH OFFENSE CODE THEFT DISTRICT
OFFENSE CODE #1 #10 (2A) CODE (A1)
58-60 85-87 88 89-91
Figure 2-1 Administrative Segment Layout (Level 1)
2.2.2 Level 2–Offense Segment
The Offense Segment is used to identify and describe the types of offenses involved in the
incident.
The data elements used in the Offense Segment are:
Data Element 1-ORI
Data Element 2-Incident Number
Data Element 6-UCR Offense Code
Data Element 7-Offense Attempted/Completed
Data Element 8-Offender Suspected of Using
Data Element 8A-Bias Motivation
Data Element 9-Location Type
Data Element 10-Number of Premises Entered
Data Element 11-Method of Entry
Data Element 12-Type Criminal Activity/Gang Information
Data Element 13-Type Weapon/Force Involved
Data Element 13-Automatic Weapon Indicator
6/30/2023 2023.0 NIBRS Technical Specification 16
Offense Segment Layout (Level 2)
Segment Length: 0063 (1 Bias Motivation)
0071 (5 Bias Motivations)
UCR OFFENSE
SEGMENT INCIDENT OFFENSE ATTEMPTED/
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER CODE COMPLETED
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (6) (7)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-40 41
DATA ELEMENT 8 OCCURS 3 TIMES DATA ELEMENT 12 OCCURS 3 TIMES
OFFENDER OFFENDER NUMBER OF TYPE TYPE
SUSPECTED OF SUSPECTED OF LOCATION PREMISES METHOD CRIMINAL CRIMINAL
USING #1 THROUGH USING #3 TYPE ENTERED OF ENTRY ACTIVITY #1 THROUGH ACTIVITY #3
(8) (8) (9) (10) (11) (12) (12)
42 44 45-46 47-48 49 50 52
DATA ELEMENT 13 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 3 TIMES
TYPE WEAPON AUTOMATIC TYPE WEAPON AUTOMATIC
FORCE WEAPON FORCE WEAPON
INVOLVED #1 INDICATOR #1 THROUGH INVOLVED #3 INDICATOR #3
(13) (13) (13) (13)
53-54 55 59-60 61
BIAS MOTIVATION #2 - #5 ARE OPTIONAL
DATA ELEMENT 8A OCCURS 4 TIMES
BIAS BIAS BIAS
MOTIVATION #1 MOTIVATION #2 THROUGH MOTIVATION #5
(8A) (8A) (8A)
62-63 64-65 70-71
Figure 2-2 Offense Segment Layout (Level 2)
2.2.3 Level 3–Property Segment
The Property Segment provides information about the type, value, and (for drugs and narcotics
seized in drug cases) quantity of property involved in the incident.
The data elements used in the Property Segment are:
Data Element 1-ORI
Data Element 2-Incident Number
Data Element 14-Type Property Loss/Etc.
Data Element 15-Property Description
Data Element 16-Value of Property
Data Element 17-Date Recovered
Data Element 18-Number of Stolen Motor Vehicles
Data Element 19-Number of Recovered Motor Vehicles
Data Element 20-Suspected Drug Type
Data Element 21-Estimated Drug Quantity
Data Element 22-Type Drug Measurement
6/30/2023 2023.0 NIBRS Technical Specification 17
Property Segment Layout (Level 3)
Segment Length: 0307
TYPE
SEGMENT INCIDENT PROPERTY
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER LOSS/ETC.
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (14)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38
DATA ELEMENTS 15, 16, & 17 AS A GROUP OCCUR 10 TIMES
PROPERTY VALUE OF DATE PROPERTY VALUE OF DATE
DESCRIPTION PROPERTY #1 RECOVERED #1 DESCRIPTION #10 PROPERTY #10 RECOVERED #10
THROUGH
#1 (15) (16) (17) (15) (16) (17)
39-40 41-49 50-57 210-211 212-220 221-228
NUMBER OR NUMBER OF DATA ELEMENTS 20, 21, & 22 AS A GROUP OCCUR 3 TIMES
STOLEN RECOVERED ESTIMATED
MOTOR MOTOR SUSPECTED DRUG TYPE DRUG
VEHICLES VEHICLES DRUG TYPE #1 QUANTITY #1 MEASUREMENT #1 THROUGH
(18) (19) (20) (21) (22)
229-230 231-232 233 234-245 246-247
DATA ELEMENTS 20,21, & 22
ESTIMATED
SUSPECTED DRUG TYPE DRUG
DRUG TYPE #3 QUANTITY #3 MEASUREMENT #3
(20) (21) (22)
263 264-275 276-277 278-307
Figure 2-3 Property Segment Layout (Level 3)
Note: Spaces 278-307 apply only when an agency submits or modifies a segment action type of
“W” segment.
2.2.4 Level 4–Victim Segment
The Victim Segment provides information about the victim(s) involved in the incident.
The data elements used in the Victim Segment are:
Data Element 1-ORI
Data Element 2-Incident Number
Data Element 23-Victim Sequence Number
Data Element 24-Victim Connected to UCR Offense Code
Data Element 25-Type of Victim
Data Element 25A-Type of Officer Activity/Circumstance
Data Element 25B-Officer Assignment Type
Data Element 25C-Officer–ORI Other Jurisdiction
Data Element 26-Age of Victim
Data Element 27-Sex of Victim
Data Element 28-Race of Victim
Data Element 29-Ethnicity of Victim
Data Element 30-Resident Status of Victim
6/30/2023 2023.0 NIBRS Technical Specification 18
Data Element 31-Aggravated Assault/Homicide Circumstances
Data Element 32-Additional Justifiable Homicide Circumstances
Data Element 33-Type Injury
Data Element 34-Offender Number to be Related
Data Element 35-Relationship of Victim to Offender
Victim Segment Layout (Level 4)
Segment Length: 0129 (without LEOKA)
0141 (with LEOKA)
VICTIM
SEGMENT INCIDENT SEQUENCE
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (23)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-40
DATA ELEMENT 24 OCCURS 10 TIMES
VICTIM VICTIM
CONNECTED TO CONNECTED TO TYPE OF AGE OF SEX OF RACE OF ETHNICITY
UCR OFFENSE #1 THROUGH UCR OFFENSE #10 VICTIM VICTIM VICTIM VICTIM OF VICTIM
(24) (24) (25) (26) (27) (28) (29)
41-43 68-70 71 72-75 76 77 78
RESIDENT DATA ELEMENT 31 OCCURS 2 TIMES ADDITIONAL DATA ELEMENT 33 OCCURS 5 TIMES
STATUS AGGRAVATED AGGRAVATED JUSTIFIABLE
OF ASSAULT/HOMICIDE ASSAULT/HOMICIDE HOMICIDE TYPE TYPE
VICTIM CIRCUMSTANCES #1 CIRCUMSTANCES #2 CIRCUMSTANCES INJURY #1 THROUGH INJURY #5
(30) (31) (31) (32) (33) (33)
79 80-81 82-83 84 85 89
DATA ELEMENTS 34 & 35 AS A GROUP OCCUR 10 TIMES LEOKA DATA ELEMENTS ARE OPTIONAL
OFFENDER RELATIONSHIP OFFENDER RELATIONSHIP TYPE OF OFFICER OFFICER OFFICER –
NUMBER TO BE OF VICTIM TO NUMBER TO BE OF VICTIM TO ACTIVITY/ ASSIGNMENT ORI OTHER
RELATED #1 OFFENDER #1 THROUGH RELATED #10 OFFENDER #10 CIRCUMSTANCE TYPE JURISDICTION
(34) (35) (34) (35) (25A) (25B) (25C)
90-91 92-93 126-127 128-129 130-131 132 133-141
Figure 2-4 Victim Segment Layout (Level 4)
2.2.5 Level 5–Offender Segment
The Offender Segment describes the offender involved in the incident (e.g., his/her age, sex,
race, and ethnicity).
The data elements used in the Offender Segment are:
Data Element 1-ORI
Data Element 2-Incident Number
Data Element 36-Offender Sequence Number
Data Element 37-Age of Offender
Data Element 38-Sex of Offender
Data Element 39-Race of Offender
Data Element 39A-Ethnicity of Offender
6/30/2023 2023.0 NIBRS Technical Specification 19
Offender Segment Layout (Level 5)
Segment Length: 0045 (without Offender Ethnicity)
0046 (with Offender Ethnicity)
SEGMENT INCIDENT
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2)
1-4 5 6 7-8 9-12 13-16 17-25 26-37
OFFENDER OPTIONAL
SEQUENCE AGE OF SEX OF RACE OF ETHNICITY OF
NUMBER OFFENDER OFFENDER OFFENDER OFFENDER
(36) (37) (38) (39) (39A)
38-39 40-43 44 45 46
Figure 2-5 Offender Segment Layout (Level 5)
2.2.6 Level 6–Arrestee Segment
The Arrestee Segment is used to report arrests involving Group A offenses and describe the
arrestees and circumstances of their arrests).
The data elements used in the Arrestee Segment are:
Data Element 1-ORI
Data Element 2-Incident Number
Data Element 40-Arrestee Sequence Number
Data Element 41-Arrest Transaction Number
Data Element 42-Arrest Date
Data Element 43-Type of Arrest
Data Element 44-Multiple Arrestee Segments Indicator
Data Element 45-UCR Arrest Offense Code
Data Element 46-Arrestee Was Armed With
Data Element 46-Automatic Weapon Indicator
Data Element 47-Age of Arrestee
Data Element 48-Sex of Arrestee
Data Element 49-Race of Arrestee
Data Element 50-Ethnicity of Arrestee
Data Element 51-Resident Status of Arrestee
Data Element 52-Disposition of Arrestee Under 18
Clearance Indicator-Place Holder (Deprecated)
• Only required if submitted as a Time-Window submission. Please refer to
Appendix D for further Time-Window guidance
Clearance Offense Codes-Place Holder (Deprecated)
• Only required if submitted as a Time-Window submission. Please refer to
Appendix D for further Time-Window guidance
6/30/2023 2023.0 NIBRS Technical Specification 20
Arrestee Segment Layout (Level 6)
Segment Length: 0110
ARRESTEE ARREST
SEGMENT INCIDENT SEQUENCE TRANSACTION
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (40) (41)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-51
MULTIPLE UCR DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE ARREST ARRESTEE AUTOMATIC ARRESTEE AUTOMATIC
ARREST TYPE OF SEGMENTS OFFENSE WAS ARMED WEAPON WAS ARMED WEAPON
DATE ARREST INDICATOR CODE WITH #1 INDICATOR #1 WITH #2 INDICATOR #2
(42) (43) (44) (45) (46) (46) (46) (46)
52-59 60 61 62-64 65-66 67 68-69 70
RESIDENT DISPOSITION CLEARANCE
AGE OF SEX OF RACE OF ETHNICITY OF STATUS OF OF ARRESTEE INDICATOR
ARRESTEE ARRESTEE ARRESTEE ARRESTEE ARRESTEE UNDER 18
(47) (48) (49) (50) (51) (52)
71-74 75 76 77 78 79 80
CLEARANCE OFFENSE CODE OCCURS 10 TIMES
CLEARANCE CLEARANCE
OFFENSE OFFENSE
THROUGH
CODE #1 CODE #10
81-83 108-110
Figure 2-6 Arrestee Segment Layout (Level 6)
2.3 Level 7–Group B Arrest Report Segment
The Group B Arrest Report is used to report arrests involving Group B offenses.
Note: Data Element 41, Arrest Transaction Number (positions 26 through 37) must be a unique
number the reporting agency assigns to the arrest report. Data Elements 40 and 41 are purposely
reversed in the Group B Arrest Report Segment.
The data elements for this segment are:
Data Element 1-ORI
Data Element 1A-Judicial District* (federal and tribal agency reporting only)
Data Element 41-Arrest Transaction Number
Data Element 40-Arrestee Sequence Number
Data Element 42-Arrest Date
Data Element 43-Type of Arrest
Data Element 45-UCR Arrest Offense Code
Data Element 46-Arrestee Was Armed With Automatic Weapon Indicator
Data Element 47-Age of Arrestee
Data Element 48-Sex of Arrestee
Data Element 49-Race of Arrestee
Data Element 50-Ethnicity of Arrestee
Data Element 51-Resident Status of Arrestee
Data Element 52-Disposition of Arrestee Under 18
6/30/2023 2023.0 NIBRS Technical Specification 21
2.3.1 Group B Arrest Report Segment Layout (Level 7)
Segment Length: 0066 (State, Local, and Tribal)
0066 (Federal Agency Reporting Only - Judicial District Code)
*NOTE: The Line Length for Federal Agency will be 69 characters long;
however, the Segment Length in the transaction will be 0066.
ARREST ARRESTEE
SEGMENT TRANSACTION SEQUENCE ARREST
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER DATE
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (41) (40) (42)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-47
DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
UCR
ARREST ARRESTEE AUTOMATIC ARRESTEE AUTOMATIC
TYPE OF OFFENSE WAS ARMED WEAPON WAS ARMED WEAPON AGE OF SEX OF
ARREST CODE WITH #1 INDICATOR #1 WITH #2 INDICATOR #2 ARRESTEE ARRESTEE
(43) (45) (46) (46) (46) (46) (47) (48)
48 49-51 52-53 54 55-56 57 58-61 62
FEDERAL
AGENCY
REPORTING
ONLY
RESIDENT DISPOSITION FEDERAL
RACE OF ETHNICITY OF STATUS OF OF ARRESTEE JUDICIAL
ARRESTEE ARRESTEE ARRESTEE UNDER 18 DISTRICT
(49) (50) (51) (52) CODE (A1)
63 64 65 66 67-69
Figure 2-7 Group B Arrest Report Segment Layout (Level 7)
Data Element 41-Arrest Transaction Number
Data Element 40-Arrestee Sequence Number
Data Element 42-Arrest Date
Data Element 43-Type of Arrest
Data Element 45-UCR Arrest Offense Code
Data Element 46-Arrestee Was Armed With Automatic Weapon Indicator
Data Element 47-Age of Arrestee
Data Element 48-Sex of Arrestee
Data Element 49-Race of Arrestee
Data Element 50-Ethnicity of Arrestee
Data Element 51-Resident Status of Arrestee
Data Element 52-Disposition of Arrestee Under 18
2.4 Level 0–Zero Report Segment
The Zero Report Segment is used when no criminal activity occurred in a law enforcement
agency’s (LEA’s) jurisdiction for the reporting month.
6/30/2023 2023.0 NIBRS Technical Specification 22
Note: A UCR program should not automatically generate the Zero Report Segment for a local
LEA that does not submit crime data for a particular month. A UCR program should only submit
the Zero Report Segment for a local LEA that communicates the fact that no criminal activity
(offense, arrest, or recovered property) occurred in its jurisdiction for the reporting period.
The absence of crime data does not mean that no crimes occurred. NIBRS must differentiate
between (1) a zero report–no crime occurred and (2) no crime information is being submitted.
The presence or absence of this record in conjunction with other available data will provide the
FBI with useful statistical information.
Refer to Section 4.7, Zero Reporting, for additional information pertaining to the handling of
zero reporting information. The data elements for this segment are:
1. Data Element 1-ORI
2. Data Element 2-Incident Number
Note: Must be all zeros in a zero report segment.
Zero Report Month
• Zero Report Month, while not a data element, it is required information for the
Zero Report Segment
• Zero Report Year
• Zero Report Year, while not a data element, it is required information for the Zero
Report Segment
2.4.1 Zero Report Segment Layout (Level 0)
Segment Length: 0043
SEGMENT INCIDENT ZERO ZERO
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER REPORT REPORT
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) MONTH YEAR
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-43
Figure 2-8 Zero Report Segment Layout (Level 0)
6/30/2023 2023.0 NIBRS Technical Specification 23
3 DATA ELEMENT DEFINITIONS
The data elements and data values identified in this section represent those required for
participating in the FBI’s UCR Program via NIBRS. LEAs should use these data elements and
data values to report incidents and arrests involving Group A offenses, reporting arrests
involving Group B offenses, and Zero Reports.
The FBI encourages participating agencies to include additional data elements and values in their
own Incident-Based Reporting (IBR) systems to satisfy their own informational needs. However,
agencies should report to the FBI only those data elements and data values that are listed in this
section.
3.1 Data Elements
LEAs must use a series of established data elements, i.e., data fields, within each segment of the
Group A Incident Report and in the Group B Arrest Report to describe the details of each
component of a crime. Examples of these details include Data Element 2 (Incident Number),
Data Element 6 (UCR Offense Code), and Data Element 25 (Type of Victim).
3.2 Data Values
For each data element, reporting agencies should choose the most appropriate data value(s), i.e.,
specific characteristics or types of the field being reported that have assigned codes. Although
some data values require a specific format, most are codes from an approved list, each followed
by an equal sign ( = ) and a description of the data value.
For example, for Data Element 3 (Incident Date), the specific format for the data value is
YYYYMMDD. For Data Element 27 (Sex of Victim), agencies may enter one of the codes
M = Male, F = Female, or U = Unknown to describe the gender of the victim; but for Data
Element 48 (Sex of Arrestee), agencies may enter only M = Male or F = Female to describe the
gender of the arrestee.
3.3 Data Element Descriptions
The data elements identified in the subsequent sections are grouped by the type of data they
represent, e.g., administrative data, offense data, arrestee data. Some data elements overlap and
are present throughout the various segments.
The format and definition of the attributes of the data elements are:
Group: This identifies whether a data element is used in only the Group A Incident Report or
both the Group A Incident Report and the Group B Arrest Report. A = Group A; B = Group B.
Format: This identifies the number of characters allowed for the data element in the segment
and whether the characters must be numeric, alphabetic, or alphanumeric.
Position: This identifies the physical position on the segment where the data element occurs. For
example, Positions 56–57 indicates the data must be written beginning in the 56th position and
ending in the 57th position in the segment.
Occurrence: This identifies how many times the data element occurs in a segment or incident.
6/30/2023 2023.0 NIBRS Technical Specification 24
Mandatory: Some data elements are required in order to have a complete/valid data submission,
i.e., they are mandatory. Others are conditional based on the data values submitted for other data
elements. Data elements that are reported at the discretion of the agency submitting the incident
are considered optional.
Edits: This identifies specific conditions that must be met in order for the data element to be
completed. The table includes a description of the edit as well as the associated error number. A
numerical listing of Error Numbers with the associated Error Message and Error Description are
located in Section 5: Errors.
Data Values: This identifies the specific data values that are allowed in completing the data
element.
3.3.1 Header Data Elements
Header data elements describe the type of data in a submission. They appear at the beginning of
each segment level to identify the segment and indicate the processing action required, as well as
to connect all of an agency’s data to a particular submission.
Segment Length
Segment length is used to indicate the number of characters submitted in the segment. It should
be noted that the segment lengths are different depending on the number and type of data
elements and corresponding values that are required.
Group: A, B
Format: 4-Character Numeric
Position: 1–4
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-1 Segment Length Edit Description
Associated Error
Edit Description
Code
The referenced data element in an incident must contain data when the 001, 101, 201,301,
referenced data element is mandatory or when the conditions are met for 401, 501,601, 701
data that must be entered into a conditionally mandatory field.
Data Values:
Level 1 Administrative Segment WITHOUT Cargo Theft (Data Element 2A) 0087
Level 1 Administrative Segment WITH Cargo Theft (Data Element 2A) 0088
Level 2 Offense Segment WITH Bias Motivation #1 (Data Element 8A) 0063
Level 2 Offense Segment WITH Bias Motivations #2–#5 (Data Element 8A) 0071
Level 3 Property Segment 0307
Level 4 Victim Segment WITHOUT LEOKA (Data Elements 25A–C) 0129
Level 4 Victim Segment WITH LEOKA (Data Elements 25A–C) 0141
Level 5 Offender Segment WITHOUT Offender Ethnicity (Data Element 39A) 0045
Level 5 Offender Segment WITH Offender Ethnicity (Data Element 39A) 0046
Level 6 Arrestee Segment 0110
6/30/2023 2023.0 NIBRS Technical Specification 25
Level 7 Group B Arrest Report Segment 0066
Level 0 Zero Report Segment 0043
Segment Level
Segment Level identifies the segment in a submission.
Group: A, B
Format: 1-Character Alphanumeric
Position: 5
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-2 Segment Level Edit Description
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
The referenced data element in an incident must contain data when the 001, 101, 201,301,
referenced data element is mandatory or when the conditions are met for 401, 501,601, 701
data that must be entered into a conditionally mandatory field.
The ORI already exists in the reference table for a different agency. Verify
931
that the ORI is accurate.
The ORI submitted was not found in the reference data table. Verification is
needed to ensure that the submitting agency is providing an accurate ORI 932
for the data submission.
The ORI submitted is currently in a covered by status. Verification is needed
to ensure that the information being provided is accurate and/or to ensure
933
that the submitting agency is now providing its own information and is no
longer in covered by status.
The ORI submitted is in delete status. Verification is needed to ensure this
934
is accurate.
Segment Levels in a Group A Incident Report must be organized in
numerical order. For example, an incident having segments 1, 2, 2, 3, 4, 4, 050
4, 5 must be written in that order, not as 1, 2, 2, 5, 3, 4, 4, 4.
Segment Level must contain a valid data value 0–7. 051
Segment Level 1 (Administrative Segment) with Segment Action Type
I = Incident Report must be the first segment submitted for each Group A 055
Incident Report.
Segment Level 2 (Offense Segment) must have at least one Segment Level
4 (Victim Segment) connected to it by entering the offense code identified in
065
Data Element 6 (UCR Offense Code) in Data Element 24 (Victim Connected
to UCR Offense Code).
Data Element 34 (Offender Numbers To Be Related) has a value that does
not have a corresponding Offender Segment. For example, if the field value
070
shown in Data Element 34 is 15, an Offender Segment does not exist with a
value of 15 in Data Element 36 (Offender Sequence Number).
6/30/2023 2023.0 NIBRS Technical Specification 26
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
Segment Level 6 (Arrestee Segment) with Segment Action Type I = Incident
Report cannot be submitted with Data Element 42 (Arrest Date) containing
an arrest date on or earlier than the date entered in Data Element 5
071
(Exceptional Clearance Date) when Data Element 4 (Cleared Exceptionally)
contains a data value other than N = Not Applicable (indicating the incident
is cleared exceptionally).
Segment Level 3 (Property Segment) must be submitted with Data Element
14 (Type Property Loss/Etc.) as 7 = Stolen/Etc. before it can be submitted
as 5 = Recovered for the same property in Data Element 15 (Property
Description). Any property being reported as recovered must first be
reported as stolen. Exceptions to this rule are:
1) When Data Element 6 (UCR Offense Code) contains an offense that
allows property to be recovered without first being stolen in that same 072
incident (i.e., 250 = Counterfeiting/Forgery and 280 = Stolen Property
Offenses, 58B = Export Violations*).
2) When a vehicle was stolen and the recovered property in Data Element
15 (Property Description) is 38 = Vehicle Parts/ Accessories.
*Denotes offenses for federal and tribal LEA reporting only
Segment Level 3 (Property Segment) with Segment Action Type I = Incident
Report must contain a data value in Data Element 18 (Number of Stolen
Motor Vehicles) greater than or equal to the data value entered in Data 073
Element 19 (Number of Recovered Motor Vehicles) within the same
incident.
Segment Level 3 (Property Segment) with Segment Action Type I = Incident
Report must be submitted when Data Element 6 (UCR Offense Code)
contains an offense of Crimes Against Property, 100 = 074
Kidnapping/Abduction, 35A = Drug/Narcotic Offenses, or Gambling
Offenses.
Segment Levels 1, 2, 4, and 5 (Administrative Segment, Offense Segment,
Victim Segment, and Offender Segment) with Segment Action Type
075
I = Incident Report must be submitted for each Group A Incident Report;
they are mandatory.
Segment Level 3 (Property Segment) with Segment Action Type I = Incident
Report cannot be submitted unless Data Element 6 (UCR Offense Code)
contains an offense of Crimes Against Property, 100 =
Kidnapping/Abduction, 35A = Drug/Narcotic Offenses, 521 = Violation of
National Firearm Act of 1934*, 522 = Weapons of Mass Destruction*, 526 = 076
Explosives*, 26H = Money Laundering*, Commerce Violations*, or
Gambling Offenses.
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 27
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
The Group A Incident Report submission contains only offense(s) that are
Crimes Against Society. When this is so, Data Element 25 (Type of Victim)
must be S = Society/Public, and only one victim may be submitted.
Exception - Type of Victim must be G = Government for offenses:
26H = Money Laundering*
521 = National Firearm Act 1934*
522 = Weapons of Mass Destruction* 080
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA reporting only
Segment Level 4 (Victim Segment) with a data value in Data Element 24
(Victim Connected to UCR Offense Code) of a Crime Against Person or
Robbery must contain at least two offender sequence numbers in Data
Element 34 (Offender Number to be Related) when there are two or more 085
Segment Level 5 (Offender Segment) records submitted for the incident,
and Data Element 25 (Type of Victim) is I = Individual or L = Law
Enforcement Officer.
Segment Level 6 (Arrestee Segment) and Segment Level 7 (Group B Arrest
Report Segment) cannot have the same data values entered in Data
088
Element 2 (Incident Number) and Data Element 41 (Arrest Transaction
Number), respectively, for the same ORI.
Segment Length for the Administrative Segment (Level 1) must be 87
characters (not reporting Cargo Theft) or 88 characters (reporting Cargo
Theft). Once an agency begins participation in reporting Cargo Theft,
indicated by 0088 in the Record Descriptor Word (RDW), then all future 178
Administrative Segments within that ORI must be formatted using 0088.
Note: The only exception would be that data prior to the agency starting to
report Cargo Theft could be submitted with the original 0087 RDW.
(Offense Segment) When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot contain duplicates. In
262
this case, two Offense Segments were submitted having the same offense
in Data Element 6 (UCR Offense Code).
(Offense Segment) May be submitted only 10 times for each Group A
263
Incident Report; 10 offense codes are allowed for each incident.
Segment Length for the Offense Segment (Level 2) must be 63 characters
(reporting only Bias Motivation #1) or 71 characters (reporting Bias
Motivations #2–#5). Once an agency begins participation in reporting Bias
Motivations #2-#5, indicated by 0071 in the RDW, then all future Offense
Segments within that ORI must be formatted using 0071. 284
Note: The only exception would be that data prior to the agency starting to
report Bias Motivations #2-#5 could be submitted with the original 0063
RDW.
6/30/2023 2023.0 NIBRS Technical Specification 28
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
(Property Segment) When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot contain duplicates.
376
Example, two property segments cannot be submitted having the same
entry in Data Element 14 (Type Property Loss/Etc.).
(Property Segment) Cannot be submitted with 10 = Drugs/Narcotics in Data
Element 15 (Property Description) and blanks in Data Element 16 (Value of
382
Property) unless Data Element 6 (UCR Offense Code) is 35A = Drug/
Narcotic Violations.
(Victim Segment) When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot contain duplicates. In
451
this case, two victim segments were submitted having the same entry in
Data Element 23 (Victim Sequence Number).
(Victim Segment) Each UCR Offense Code entered into Data Element 24
(Victim Connected to UCR Offense Codes) must have the Offense Segment
for the value. In this case, the victim was connected to offenses that were 466
not submitted as Offense Segments. A victim cannot be connected to an
offense when the offense itself is not present.
(Victim Segment) Data Element 35 (Relationship of Victim to Offender) has
a relationship of VO = Victim Was Offender. When this code is entered, a
minimum of two victim and two offender segments must be submitted. In
this case, only one victim and/or one offender segment was submitted. The 470
entry of VO on one or more of the victims indicates situations such as
brawls and domestic disputes. In the vast majority of cases, each victim is
also the offender; therefore, every victim record would contain a VO code.
(Victim Segment) Cannot be submitted multiple times with VO = Victim Was
Offender in Data Element 35 (Relationship of Victim to Offender) when Data
474
Element 34 (Offender Number to be Related) contains the same data value
(indicating the same offender).
(Victim Segment) An offender can only have one spousal relationship. In
this instance, two or more victims have a relationship of SE = Spouse to the 476
same offender.
Data Element 31 (Aggravated Assault/Homicide Circumstances) has
08 = Other Felony Involved but the incident has only one offense. For this
code to be used there must be an Other Felony. Either multiple entries for
480
Data Element 6 (UCR Offense Code) should have been submitted, or
multiple individual victims should have been submitted for the incident
report.
Segment Length for the Victim Segment (Level 4) must be 129 characters
(not reporting LEOKA) or 141 characters (reporting LEOKA). Once an
agency begins participation in reporting the LEOKA via NIBRS data
elements 25A/25B/25C, indicated by 0141 in the RDW, then all future Victim
Segments within that ORI must be formatted using 0141. 484
Note: The only exception would be that data prior to the agency starting to
report LEOKA via the NIBRS data elements, could be submitted with the
original 0129 RDW.
6/30/2023 2023.0 NIBRS Technical Specification 29
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
(Offender Segment) When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot contain duplicates. In
551
this case, two Offender Segments were submitted having the same entry in
Data Element 36 (Offender Sequence Number).
(Offender Segment) When multiple Offender Segments are submitted, none
can contain a 00 = Unknown value because the presence of 00 indicates
555
that the number of offenders is unknown. In this case, multiple offenders
were submitted, but one of the segments contains the 00 = Unknown value.
(Offender Segment) None of the Offender Segments contain all known
values for Age, Sex, and Race. When an incident is cleared exceptionally
558
(Data Element 4 contains an A through E), one offender must have all
known values.
(Offender Segment) The incident was submitted with Data Element 6 (UCR
Offense Code) value of 09C = Justifiable Homicide or 360 = Failure to
Register as a Sex Offender*, but unknown information was submitted for all
the offender(s). At least one of the offenders must have known information 559
for age, sex, and race.
*Denotes offenses for federal and tribal LEA reporting only
Segment Length for the Offender Segment (Level 5) must be 45 characters
(not reporting Offender Ethnicity) or 46 characters (reporting Offender
Ethnicity. Once an agency begins participation in reporting the Offender
Ethnicity, indicated by 0046 in the RDW, then all future Offender Segments 584
within that ORI must be formatted using 0046.
Note: The only exception would be that data prior to the agency starting to
report Offender Ethnicity could be submitted with the original 0045 RDW.
(Arrestee Segment) A Group A Incident Report was submitted with more
arrestees than offenders. The number (nn) of offenders is shown within the
message. The incident must be resubmitted with additional Offender
Segments. This message will also occur if an arrestee was submitted and
Data Element 36 (Offender Sequence Number) was 00 = Unknown.
An exception is when an additional arrest is reported for a pre-NIBRS 656
incident. In this case, Segment Level 6 (Arrestee Segment) will contain A =
Add, but the data value in Data Element 2 (Incident Number) will not match
an incident already on file in the national UCR database. The segment will
be processed, but used only for SRS purposes and will not be included in
the agency’s NIBRS figures.
(Arrestee Segment) Segment Level 6 (Arrestee Segment) cannot contain
duplicate data values in Data Element 40 (Arrestee Sequence Number)
when two or more Arrestee Segments are submitted for the same incident.
The Data Element 41 (Arrest Transaction Number) is the number assigned
by the reporting agency to an arrest report to identify it uniquely. If multiple 661
arrestees are reported, each having the same data value in Data Element
40 (Arrestee Sequence Number), ensure that Data Element 41 (Arrest
Transaction Number) is unique for each arrestee submitted to ensure that
duplication does not occur.
6/30/2023 2023.0 NIBRS Technical Specification 30
Segment Level Edit Descriptions
Associated Error
Edit Description
Code
(Arrestee Segment) Group A Incident Reports cannot have arrests when
Data Element 6 (UCR Offense Code) is 09C = Justifiable Homicide. By
669
definition, a justifiable homicide never involves an arrest of the offender (the
person who committed the justifiable homicide).
(Group B Arrest Report Segment) When a Group B Arrest Report (Level 7)
has two or more arrestees, the individual segments comprising the report
cannot contain duplicates. In this case, two arrestee segments were
submitted having the same entry in Data Element 40 (Arrestee Sequence
Number). Error should only be thrown when the action type is A = Add.
The Data Element 41 (Arrest Transaction Number) is the number assigned 751
by the reporting agency to an arrest report to identify it uniquely. If multiple
arrestees are reported, each having the same data value in Data Element
40 (Arrestee Sequence Number), ensure that Data Element 41 (Arrest
Transaction Number) is unique for each arrestee submitted to ensure that
duplication does not occur.
(Group B Arrest Report Segment) The Group B Arrest Report (Level 7)
submitted as an A = Add is currently active in the FBI’s database; therefore,
it was rejected. If multiple arrestees are involved in the incident, ensure that 759
Data Element 40 (Arrestee Sequence Number) is unique for each Arrestee
Segment submitted so that duplication does not occur.
Data Values: 0 = Level 0 (Zero Report Segment)
1 = Level 1 (Administrative Segment)
2 = Level 2 (Offense Segment)
3 = Level 3 (Property Segment)
4 = Level 4 (Victim Segment)
5 = Level 5 (Offender Segment)
6 = Level 6 (Arrestee Segment)
7 = Level 7 (Group B Arrest Report Segment)
Segment Action Type
Segment Action Type determines the kind of database activity that is to be performed. See
Section 4.6: Segment Action Types for definitions of the Segment Action Type data values.
Group: A, B
Format: 1-Character Alphabetic
Position: 6
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-3 Segment Action Type Edit Description
Edit Description Associated Error Code
The referenced data element in an incident must contain data when
the referenced data element is mandatory or when the conditions are 001, 101, 201, 301, 401,
met for data that must be entered into a conditionally mandatory 501, 601, 701
field.
6/30/2023 2023.0 NIBRS Technical Specification 31
Data Values: Segment 1–Administrative Segment
• I = Incident Report
• D = Delete
Segment 2–Offense Segment
• I = Incident Report
Segment 3–Property Segment
• I = Incident Report
Segment 4–Victim Segment
• I = Incident Report
Segment 5–Offender Segment
• I = Incident Report
Segment 6–Arrestee Segment
• I = Incident Report
Segment 7–Group B Arrest Report Segment
• A = Add
• D = Delete
Segment 0–Zero Report Segment
• A = Add
• D = Delete
Month of Submission
Month of Submission is defined as the month the submission is created. Each segment in a
submission must have the same Month of Submission and Year of Submission.
Group: A, B
Format: 2-Character Numeric (MM)
Position: 7–8
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-4 Month of Submission Edit Description
Associated Error
Edit Description
Code
The referenced data element in an incident must contain data when the
001, 101, 201, 301,
referenced data element is mandatory or when the conditions are met for
401, 501, 601, 701
data that must be entered into a conditionally mandatory field.
Month of Submission and Year of Submission must contain the same data
values for each segment in a NIBRS submission. The first segment
058
processed will be compared with all other segments to check for this
condition.
Month of Submission and Year of Submission cannot be after the date the
FBI receives and processes a NIBRS submission. This edit checks for data 060
submitted for a future month/year.
Data Values: 01 = January
02 = February
03 = March
6/30/2023 2023.0 NIBRS Technical Specification 32
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
Year of Submission
Year of Submission is the year in which the Month of Submission occurs. Each segment in a
submission must have the same Month of Submission and Year of Submission.
Group: A, B
Format: 4-Character Numeric (YYYY)
Position: 9–12
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-5 Year of Submission Edit Description
Associated Error
Edit Description
Code
The referenced data element in an incident must contain data when the 001, 101, 201,
referenced data element is mandatory or when the conditions are met for data 301, 401, 501,
that must be entered into a conditionally mandatory field. 601,701
Month of Submission and Year of Submission must contain the same data
values for each segment in a NIBRS submission. The first segment processed 058
will be compared with all other segments to check for this condition.
Month of Submission and Year of Submission cannot be after the date the FBI
receives and processes a NIBRS submission. This edit checks for data 060
submitted for a future month/year.
Data Values: 1991–Current Year
City Indicator
The FBI assigns a City Indicator code to cities that submit directly to the FBI because their UCR
program does not participate in NIBRS.
Group: A, B
Format: 4-Character Alphanumeric
Position: 13–16
Occurrence: Once per Segment
Mandatory: Conditional
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 33
Table 3-6 City Indicator Edit Description
Edit Description Associated Error Code
The referenced data element must contain a valid data value when it 104, 204, 304, 404, 504, 604,
is entered; blank is permissible on nonmandatory fields. 704
Data Values: The FBI’s UCR Program assigns Data Values on an individual agency basis.
For example, GAA7 = Anytown, GA.
3.3.2 Administrative Segment
The Administrative Segment is the master segment and contains identifying data information for
organizational purposes that are applicable to the entire incident report (e.g., the unique case
number assigned to the incident and the date and hour that the incident occurred). A single
Administrative Segment should be submitted for each incident report.
Data Element 1-ORI
ORI is a unique nine-character National Crime Information Center (NCIC) Originating Agency
Identifier (ORI) that has been assigned to each LEA. The NCIC assigns all ORI numbers to any
agency that is going to be participating in Uniform Crime Reporting. This ORI might not be the
same as the ORI assigned to the same agency for NCIC reporting. Please work with the Crime
Statistics Management Unit (CSMU) Statistical Assistant to address ORI discrepancies.
Note: Although the details regarding ORI are provided only once here, this data element must be
included in each segment of the Group A Incident Report, in addition to the Group B Arrest
Report Segment and Zero Report Segment. The edits and associated errors listed include edits
and errors for each segment to which the information applies.
Group: A, B
Format: 9-Character Alphanumeric
Position: 17–25
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-7 ORI Edit Description
ORI Data Element Edits
Associated
Data Element Edit Description
Error Code
(ORI) The referenced data element in an incident must contain
001, 101, 201,
data when the referenced data element is mandatory or when
Data Element 1 301, 401, 501,
the conditions are met for data that must be entered into a
601, 701
conditionally mandatory field.
Data Element 1 (ORI) Must be a valid nine-character NCIC ORI. 952, 931-934
(ORI) First two positions must be the code of the state (e.g., SC,
Data Element 1 MD) in which the incident occurred. For nonfederal participants, 059
every record must have the same code.
Data Values: Valid ORI values are assigned by the NCIC and contain the characters A–Z
(capital letters only) and 0–9.
6/30/2023 2023.0 NIBRS Technical Specification 34
Data Element 1A-Federal Judicial District (JD) [Federal Submissions Only]
A Federal Judicial District is a defined legal district that denotes a territory for which a federal
court has jurisdiction. The JD describes what court will hear a federal case. There are currently
95 federal judicial districts across the United States and its territories. This data element in
NIBRS describes where the crime(s) took place by designating what JD the incident occurred.
Review the area of the NIBRS User Manual “Definition of an Incident” in order to understand
time and place requirements. In NIBRS, federal agencies can reflect the incident location as the
JD code to give a better geographical location of the incident.
Note: This data element is mandatory for federal submitters.
Group: A, B
Format: 3-Character Alphanumeric
Position: 89-91 in Level 1 – Administrative Segment
Position: 67-69 in Level 7 – Group B Arrest Report Segment
Occurrence: Once per Segment
Mandatory: Yes (Mandatory for federal agencies only)
Edits:
Table 3-8 Judicial District Edit Description
Judicial District Data Element Edits
Associated
Data Element Edit Description
Error Code
(JD) The referenced data element in an incident must contain
Data Element data when the referenced data element is mandatory or when
101, 701
1A the conditions are met for data that must be entered into a
conditionally mandatory field.
Data Values:
001 = Alabama, Northern District
002 = Alabama, Middle District
003 = Alabama, Southern District
004 = Florida, Southern District
005 = Northern Mariana Islands
006 = Alaska
008 = Arizona
009 = Arkansas, Eastern District
010 = Arkansas, Western District
011 = California, Northern District
012= California, Central District
013 = Colorado
014 = Connecticut
015 = Delaware
016 = District of Columbia
017 = Florida, Northern District
018 = Florida, Middle District
019 = Georgia, Northern District
6/30/2023 2023.0 NIBRS Technical Specification 35
020 = Georgia, Middle District
021 = Georgia, Southern District
022 = Hawaii
023 = Idaho
024 = Illinois, Northern District
025 = Illinois, Southern District
026 = Illinois, Central District
027 = Indiana, Northern District
028 = Indiana, Southern District
029 = Iowa, Northern District
030 = Iowa, Southern District
031 = Kansas
032 = Kentucky, Eastern District
033 = Kentucky, Western District
034 = Louisiana, Eastern District
035 = Louisiana, Western District
036 = Maine
037 = Maryland
038 = Massachusetts
039 = Michigan, Eastern District
040 = Michigan, Western District
041 = Minnesota
042 = Mississippi, Northern District
043 = Mississippi, Southern District
044 = Missouri, Eastern District
045 = Missouri, Western District
046 = Montana
047 = Nebraska
048 = Nevada
049 = New Hampshire
050 = New Jersey
051 = New Mexico
052 = New York, Northern District
053 = New York, Eastern District
054 = New York, Southern District
055 = New York, Western District
056 = North Carolina, Eastern District
057 = North Carolina, Middle District
058 = North Carolina, Western District
059 = North Dakota
060 = Ohio, Northern District
061 = Ohio, Southern District
062 = Oklahoma, Northern District
063 = Oklahoma, Eastern District
064 = Oklahoma, Western District
065 = Oregon
6/30/2023 2023.0 NIBRS Technical Specification 36
066 = Pennsylvania, Eastern District
067 = Pennsylvania, Middle District
068 = Pennsylvania, Western District
069= Puerto Rico
070 = Rhode Island
071 = South Carolina
073 = South Dakota
074 = Tennessee, Eastern
075 = Tennessee, Middle
076 = Tennessee, Western
077 = Texas, Northern
078 = Texas, Eastern
079 = Texas, Southern
080 = Texas, Western
081 = Utah
082 = Vermont
083 = Virginia, Eastern
084 = Virginia, Western
085 = Washington, Eastern
086 = Washington, Western
087 = West Virginia, Northern
088 = West Virginia, Southern
089 = Wisconsin, Eastern
090 = Wisconsin, Western
091 = Wyoming
093 = Guam
094 = Virgin Islands
095 = Louisiana, Middle District
097 = California, Eastern District
098 = California, Southern District
Data Element 2-Incident Number
Incident Number is the number assigned by the reporting agency to each Group A Incident
Report to uniquely identify the incident (e.g., the LEA’s Case Number). Incident Number can be
up to 12 characters long.
Note: Although the details regarding Incident Number are provided only once here, this data
element must be included in each segment of the Group A Incident Report, in addition to the
Zero Report Segment. Incident Number is not used in the Group B Arrest Report Segment,
where it is replaced by Data Element 41 (Arrest Transaction Number). The edits and associated
errors listed include edits and errors for each segment to which the information applies.
As stated below in the table, see Associated Error Code 056, No incident numbers should ever
repeat even if the year in which the incident number is generated is different. A simple fix is to
append the year to the end of the incident number so that you will always have unique incident
numbers every year. NIBRS allots for 12 characters to be used for the incident number; this
allows an agency to have or store more than 999 billion unique incidents.
6/30/2023 2023.0 NIBRS Technical Specification 37
Group: A
Format: 12-Character Alphanumeric
Position: 26–37
Occurrence: Once per Segment
Mandatory: Yes
Edits:
Table 3-9 Incident Number Edit Description
Incident Number Data Element Edits
Associated Error
Data Element Edit Description
Code
(Incident Number) The referenced data element in an
Incident must contain data when the referenced data element 001, 101, 201, 301,
Data Element 2
is mandatory or when the conditions are met for data that 401, 501, 601
must be entered into a conditionally mandatory field.
(Incident Number) For each submitting agency, as identified
in Section 3.3.2.1, the value must be a unique number. This
means that no two incidents can have the same incident
Data Element 2 number. Some agencies ensure uniqueness by prefixing 056
every incident number with a two-digit year followed by a
number starting with 1, while others just increment the
number by 1 for each new incident.
A Group A Incident Number and a Group B Arrest Report
Data Element 2 Arrest Transaction Number cannot have the same number 088
within the same ORI.
(Incident Number) Zero-Reporting Segment (Level 0) must
Data Element 2 092
contain 12 zeros as the Incident Number.
(Incident Number) Must be blank right-fill if under 12
115, 215, 315, 415,
Data Element 2 characters in length. Cannot have embedded blanks between
515, 615
the first and last characters entered.
(Incident Number) Must be left-justified with blank right-fill if 116, 216, 316, 416,
Data Element 2
under 12 characters in length. 516, 616
(Incident Number) Must contain a valid character combination
of the following:
• A–Z (capital letters only) 117, 217, 317, 417,
Data Element 2
• 0–9 517, 617
• Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not valid.
Data Values: Administrative Segment (Level 1)
Offense Segment (Level 2)
Property Segment (Level 3)
Victim Segment (Level 4)
Offender Segment (Level 5)
Arrestee Segment (Level 6)
A–Z (capital letters only)
0–9
Hyphen
6/30/2023 2023.0 NIBRS Technical Specification 38
Group B Arrest Report Segment (Level 7)
Data Element 2 (Incident Number) is not used in the Group B Arrest Report. Data Element 41
(Arrest Transaction Number) is used in its place. See Section 3.3.7, Arrestee Segment/Group B
Arrest Report Segment, Arrest Transaction Number, for more information.
Zero Report Segment (Level 0)
Data Element 2 (Incident Number) is not used in the Zero Report Segment. Record Positions 26–
37 should default to all zeros.
Data Element 2A-Cargo Theft
This data element indicates whether or not the incident involved a Cargo Theft. Although it is an
optional data element, once added to a submission, it becomes conditional and must be populated
with a valid data value or left blank depending on the offenses in the incident. By incorporating
the Segment Length of “0088” for Cargo Theft, incidents with a Cargo Theft-related offense
must contain a valid data value in record position 88. Conversely, any incident without one of
these offenses must contain a blank in position 88. Cargo Theft-related offenses are:
• 120 = Robbery
• 210 = Extortion/Blackmail
• 220 = Burglary/Breaking & Entering
• 23D = Theft From Building
• 23F = Theft From Motor Vehicle
• 23H = All Other Larceny
• 240 = Motor Vehicle Theft
• 26A = False Pretenses/Swindle/Confidence Game
• 26B = Credit Card/Automated Teller Machine Fraud
• 26C = Impersonation
• 26E = Wire Fraud
• 26F = Identity Theft
• 26G = Hacking/Computer Invasion
• 510 = Bribery
• 270 = Embezzlement
Group: A
Format: 1-Character Alphabetic
Position: 88
Occurrence: Once per Administrative Segment
Mandatory: Optional/Conditional
Edits:
Table 3-10 Cargo Theft Edit Description
Incident Number Data Element Edits
Associated
Data Element Edit Description
Error Code
(Cargo Theft) The referenced data element must contain a valid data
Data Element 2A 104
value when it is entered; blank is permissible on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 39
Incident Number Data Element Edits
Associated
Data Element Edit Description
Error Code
(Cargo Theft) must be blank, unless Data Element 6 (UCR Offense
Code) includes at least one of the following:
120 = Robbery
210 = Extortion/Blackmail
220 = Burglary/Breaking & Entering
23D = Theft From Building
23F = Theft From Motor Vehicle
23H = All Other Larceny
Data Element 2A 240 = Motor Vehicle Theft 119
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C = Impersonation
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
270 = Embezzlement
510 = Bribery
(Cargo Theft) must be populated with a Y = Yes or N = No only when
Data Element 6 (UCR Offense Code) includes at least one of the
following:
120 = Robbery
210 = Extortion/Blackmail
220 = Burglary/Breaking & Entering
23D = Theft From Building
23F = Theft From Motor Vehicle
23H = All Other Larceny
Data Element 2A 122
240 = Motor Vehicle Theft
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C = Impersonation
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
270 = Embezzlement
510 = Bribery
Data Values: Y = Yes
N = No
(Blank) = Not a Cargo Theft offense
Data Element 3-Incident Date
Incident Date is used to enter the year, month, and day (YYYYMMDD) when the incident
occurred or the beginning of the time-period in which it occurred, as appropriate.
6/30/2023 2023.0 NIBRS Technical Specification 40
Note: When the date of the incident is unknown, then enter the date the incident was reported
and enter R = Report Date in Report Date Indicator (Record Position 46).
Group: A
Format: 8-Character Numeric (YYYYMMDD)
Position: 38–45
Occurrence: Once per Administrative Segment
Mandatory: Yes
Edits:
Table 3-11 Incident Date Edit Description
Incident Date Data Element Edits
Associated Error
Data Element Edit Description
Code
The referenced data element in an incident must contain
data when the referenced data element is mandatory or
Data Element 3 101
when the conditions are met for data that must be entered
into a conditionally mandatory field.
(Incident Date) The data element in error contains a date
that is not entered correctly. Each component of the date
must be valid; that is, months must be 01 through 12, days
Data Element 3 must be 01 through 31, and year must include the century 105
(i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days).
Also, the date cannot exceed the current date.
(Incident Date) The UCR Program has determined that an
ORI will no longer be submitting data to the FBI as of an
Data Element 3 118
inactive date. The UCR Program will not accept data from
the ORI after this date.
(Incident Date) The date cannot be later than the year and
month the electronic submission represents. For example,
Data Element 3 170
the May 1999 electronic submission cannot contain
incidents happening after this date.
(Incident Date) cannot be earlier than 01/01/1991. This edit
Data Element 3 will preclude dates that are obviously incorrect since the 172
FBI began accepting NIBRS data on this date.
(Incident Date) is missing for a Group A Incident Report
Data Element 3 with a Segment Action Type of D = Delete; must be 197
populated with a valid data value and cannot be blank.
(Incident Date) is missing for a Group A Incident Report
with a Segment Action Type of D = Delete; at least one
Data Element 3 Group A Incident Report is on file that matches Data 198
Element 2 (Incident Number) with an Incident Date outside
the two year window.
(Incident Date) is missing for a Group A Incident Report
with a Segment Action Type of D = Delete; must be
Data Element 3 populated with a valid data value and cannot be blank. 199
Incident Number matches multiple Group A Incident
Reports.
6/30/2023 2023.0 NIBRS Technical Specification 41
Data Values: Data Element 3 (Incident Date) must be a valid date in YYYYMMDD format:
Year (YYYY): 1991–Current
Month (MM): 01 = January
02 = February
03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
Day of the Month (DD): 01–31 (depending on the month).
Data Element 3-Report Date Indicator
Report Date Indicator is used to designate that the date entered in Data Element 3 (Incident Date)
is the Report Date rather than the Incident Date.
Group: A
Format: 1-Character Alphabetic
Position: 46
Occurrence: Once per Administrative Segment
Mandatory: Conditional
Edits:
Table 3-12 Report Date Indicator Edit Description
Report Date Indicator Element Edits
Data
Data Element Data Element
Element
(Report Date Indicator) The referenced data element must contain
Data Element 3 a valid data value when it is entered; blank is permissible on 104
nonmandatory fields.
(Report Date Indicator) This field must be blank if the Incident Date
is known. If the Incident Date is unknown, then the Report Date
Data Element 3 151
would be entered instead and must be indicated with an “R” in the
Report Indicator field within the Administrative Segment.
Data Values: R = Report Date
Data Element 3-Incident Hour
Incident Hour is used to enter the hour when the incident occurred or the beginning of the time
period in which it occurred, as appropriate.
Group: A
Format: 2-Character Numeric (HH)
Position: 47–48
Occurrence: Once per Administrative Segment
6/30/2023 2023.0 NIBRS Technical Specification 42
Mandatory: Conditional, if known it must be entered
Edits:
Table 3-13 Incident Hour Edit Description
Incident Hour Data Element Edits
Associated Error
Data Element Edit Description
Code
(Incident Hour) The referenced data element must contain a
Data Element 3 valid data value when it is entered; blank is permissible on 104
nonmandatory fields.
(Incident Hour) If Hour is entered within Data Element 3
(Incident Date/Hour), it must be 00 through 23.
If 00 = Midnight is entered, be careful that the Incident Date is
entered as if the time was 1 minute past midnight.
Data Element 3 Note: When an incident occurs exactly at midnight, Data 152
Element 3 (Incident Date) would be entered as if the time is 1
minute past midnight. For example, when a crime occurred
exactly at midnight on Thursday, Friday’s date would be
entered.
(Incident Hour) For Offenses of 09A, 13A, 13B and 13C ONLY
- When Data Element 25 (Type of Victim) is L = Law
Data Element 3 Enforcement Officer then Data Element 3 (Incident Date/Hour) 106
must be populated with a valid hour (00-23). Incident Hour
Unknown (Blank) is not a valid entry.
Data Values: 00–23
Data Element 4-Cleared Exceptionally
Cleared Exceptionally is used to indicate whether or not the incident is cleared by exceptional
means. In a multiple-offense incident, the exceptional clearance of one offense clears the entire
incident. An incident cannot be cleared exceptionally if it was previously or concurrently cleared
by an arrest, i.e., if an Arrestee Segment (Level 6) is submitted.
Group: A
Format: 1-Character Alphabetic
Position: 49
Occurrence: Once per Administrative Segment
Mandatory: Yes
Edits:
Table 3-14 Cleared Exceptionally Edit Description
Cleared Exceptionally Data Element Edits
Associated Error
Data Element Edit Description
Code
Segment Level 6 (Arrestee Segment) with Segment Action
Type I = Incident Report cannot be submitted with Data
Element 42 (Arrest Date) containing an arrest date on or
Data Element 4 earlier than the date entered in Data Element 5 (Exceptional 071
Clearance Date) when Data Element 4 (Cleared Exceptionally)
contains a data value other than N = Not Applicable (indicating
the incident is cleared exceptionally).
6/30/2023 2023.0 NIBRS Technical Specification 43
Cleared Exceptionally Data Element Edits
Associated Error
Data Element Edit Description
Code
(Cleared Exceptionally) The referenced data element in an
incident must contain data when the referenced data element
Data Element 4 101
is mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
(Cleared Exceptionally) The referenced data element must
Data Element 4 contain a valid data value when it is entered; blank is 104
permissible on nonmandatory fields.
(Cleared Exceptionally) Cannot be N = Not Applicable if Data
Data Element 4 153
Element 5 (Exceptional Clearance Date) is entered.
Data Values: A = Death of Offender
B = Prosecution Declined (by the prosecutor for a reason other than lack of
probable cause)
C = In Custody of Other Jurisdiction (includes extradition denied)
D = Victim Refused to Cooperate (in the prosecution)
E = Juvenile/No Custody (the handling of a juvenile without taking him/her into
custody, but rather by oral or written notice given to the parents or legal
guardian in a case involving a minor offense, such as petty larceny).
N = Not Applicable (not cleared exceptionally).
Data Element 5-Exceptional Clearance Date
Exceptional Clearance Date is used to enter the date the incident is cleared by exceptional means
(i.e., a code other than N = Not Applicable is entered in Data Element 4 (Cleared Exceptionally).
Group: A
Format: 8-Character Numeric (YYYYMMDD)
Position: 50–57
Occurrence: Once per Administrative Segment
Mandatory: Conditional
This data element is mandatory when Data Element 4 (Cleared Exceptionally) contains data
values A–E (the incident is cleared by exceptional means).
Edits:
Table 3-15 Exceptional Clearance Date Edit Description
Incident Hour Data Element Edits
Associated Error
Data Element Edit Description
Code
(Exceptional Clearance Date) The referenced data element
Data Element 5 must contain a valid data value when it is entered; blank is 104
permissible on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 44
Incident Hour Data Element Edits
Associated Error
Data Element Edit Description
Code
(Exceptional Clearance Date) The data element in error
contains a date that is not entered correctly. Each component
of the date must be valid; that is, months must be 01 through
12, days must be 01 through 31, and year must include the
century (i.e., 19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31 days).
Data Element 5 105
The date cannot be later than that entered within the Month
of Electronic submission and Year of Electronic submission
fields on the data record. For example, if Month of Electronic
submission and Year of Electronic submission are 06/1999,
the recovered date cannot contain any date 07/01/1999 or
later. Also, the date cannot exceed the current date.
(Exceptional Clearance Date) is earlier than Data Element 3
Data Element 5 155
(Incident Date/Hour).
(Exceptional Clearance Date) must be present if the case
was cleared exceptionally. Data Element 4 (Cleared
Data Element 5 156
Exceptionally) has an entry of A through E; therefore, the
date must also be entered.
Data Values: Data Element 5 (Exceptional Clearance Date) must be a valid date in
YYYYMMDD format:
Year (YYYY): 1991–Current
Month (MM): 01 = January
02 = February
03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
Day of the Month (DD): 01–31 (depending on the month).
Data Values: Refer to Appendix A–Group A Offenses
3.3.3 Offense Segment
The Offense Segment describes the various types of offenses involved in the incident and is
submitted for up to ten of the most serious Group A offenses in the incident (as determined by
the reporting agency). Only one Offense Segment should be submitted for each reported UCR
Offense Code (Data Element 6) even though there may have been more than one victim of the
crime. At least one Offense Segment must be submitted for each Group A Incident Report.
6/30/2023 2023.0 NIBRS Technical Specification 45
Each offense must be reported if it is a separate, distinct crime, rather than just a part of another
offense. For example, every robbery includes some type of assault; but because the assault is an
element that makes up the crime of Robbery, only Robbery should be reported. On the other
hand, if during a robbery the victim is forced to engage in sexual relations, both Robbery and a
Sex Offense should be reported, because sexual intercourse without the consent of the victim is
not an element of Robbery.
Note: In addition to the data elements specified, the Offense Segment also contains the Header
Data Elements identified in Section 3.3.1, as well as Data Element 1 (ORI) and Data Element 2
(Incident Number) included in the Administrative Segment, Section 3.3.2.
Data Element 6-UCR Offense Code
UCR Offense Code is used to enter the data values of the Group A offenses that occurred in the
incident.
Group: A
Format: 3-Character Alphanumeric
Position: 38–40
Occurrence: Once per Offense Segment
Mandatory: Yes
Edits:
Table 3-16 UCR Offense Code Edit Description
UCR Offense Code Data Element Edits
Associated Error
Data Element Edit Description
Code
(UCR Offense Code) The referenced data element in an
incident must contain data when the referenced data element
Data Element 6 201
is mandatory or when the conditions are met for data that
must be entered into a conditionally mandatory field.
(UCR Offense Code) The referenced data element must
Data Element 6 contain a valid data value when it is entered; blank is 204
permissible on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 46
UCR Offense Code Data Element Edits
Associated Error
Data Element Edit Description
Code
The following values for Data Element 6 (UCR Offense Code)
are only valid for use by federal and tribal agencies:
26H = Money Laundering
101 = Treason
103 = Espionage
30A = Illegal Entry into the United States
30B = False Citizenship
30C = Smuggling Aliens
30D = Re-entry after Deportation
360 = Failure to Register as a Sex Offender
Data Element 6 49A = Harboring Escapee/Concealing from Arrest 250
49B = Flight to Avoid Prosecution
49C = Flight to Avoid Deportation
521 = Violation of National Firearm Act of 1934
522 = Weapons of Mass Destruction
526 = Explosives
58A = Import Violations
58B = Export Violations
61A = Federal Liquor Offenses
61B = Federal Tobacco Offenses
620 = Wildlife Trafficking
When a Group A Incident Report is submitted, the individual
segments comprising the incident cannot contain duplicates.
Data Element 6 262
In this case, two Offense Segments were submitted having
the same offense in Data Element 6 (UCR Offense Code).
(UCR Offense Code) Data Element 6 (UCR Offense Code)
Data Element 6 must be a Group A UCR Offense Code, not a Group B 264
Offense Code.
When a Justifiable Homicide is reported, no other offense may
Data Element 6 be reported in the Group A Incident Report. These should be 266
submitted on another Group A Incident Report.
Data Element 6 (UCR Offense Code) is a (23A-23H) =
Larceny/Theft Offenses and a Property Segment exists with
Data Element 14 (Type Property Loss/Etc.) of 7 = Stolen/Etc.
and Data Element 15 (Property Description) of
03 = Automobiles, 05 = Buses, 24 = Other Motor Vehicles,
Data Element 6 268
28 = Recreational Vehicles, or 37 = Trucks; then the incident
must contain another Offense Segment with Data Element 6
(UCR Offense Code) containing a Crime Against Property
other than a Larceny/Theft offense (refer to Appendix E:
Mandatories for each Crime Against Property offense)
Data Values: Refer to Appendix A–Group A Offenses
Data Element 7-Offense Attempted/Completed
Offense Attempted/Completed is used to indicate whether each offense in the incident was
attempted or completed. When an offense occurs more than once within an incident and one of
the offenses are completed, then C = Completed must be entered.
6/30/2023 2023.0 NIBRS Technical Specification 47
Note: Attempted Murder should be reported as Aggravated Assault and all Assault Offenses
should be classified as C = Completed.
Group: A
Format: 1-Character Alphabetic
Position: 41
Occurrence: Once per Offense Segment
Mandatory: Yes
Edits:
Table 3-17 Offense Attempted/Completed Edit Description
Offense Attempted/Completed Data Element Edits
Associated Error
Data Element Edit Description
Code
(Offense Attempted/Completed) The referenced data element
in an incident must contain data when the referenced data
Data Element 7 201
element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
(Offense Attempted/Completed) Must be a valid code of
Data Element 7 251
A = Attempted or C = Completed.
(Offense Attempted/Completed) Code must be
C = Completed if Data Element 6 (UCR Offense Code) is an
Data Element 7 Assault, Homicide, or 360 = Failure to Register as a Sex 256
Offender*.
*Denotes offenses for federal and tribal LEA reporting only
Data Values: A = Attempted
C = Completed
Data Element 8-Offender Suspected of Using
Offender Suspected of Using is used to indicate whether any of the offenders in the incident were
suspected of consuming alcohol or using drugs/narcotics during or shortly before the incident, or
of using computer equipment to perpetrate the crime.
Group: A
Format: 1-Character Alphabetic
Position: 42-Activity 1
43-Activity 2
44-Activity 3
Occurrence: 3 times per Offense Segment
Mandatory: Yes
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 48
Table 3-18 Offender Suspected of Using Edit Description
Offender(s) Suspected of Using Data Element Edits
Associated Error
Data Element Edit Description
Code
(Offender Suspected of Using) The referenced data element in
an incident must contain data when the referenced data
Data Element 8 201
element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
(Offender Suspected of Using) The referenced data element
Data Element 8 must contain a valid data value when it is entered; blank is 204
permissible on nonmandatory fields.
(Offender Suspected of Using) The referenced data element in
Data Element 8 error is one that contains multiple data values. When more 206
than one code is entered, none can be duplicate codes.
(Offender Suspected of Using) The data element in error can
have multiple data values and was entered with multiple
values. However, mutually exclusive values cannot be entered
with any other data value. Refer to individual data elements for
mutually exclusive data values.
• 207A ERROR MUTUALLY EXCLUSIVE VALUE -
Data Element 8 SUSPECTED OF USING 207
• 207B ERROR MUTUALLY EXCLUSIVE VALUE -
BIAS MOTIVATION
• 207C ERROR MUTUALLY EXCLUSIVE VALUE -
CRIMINAL ACTIVITY / GANG INFORMATION
• 207D ERROR MUTUALLY EXCLUSIVE VALUE -
WEAPON CODE
Data Values: A = Alcohol
C = Computer Equipment (Handheld Devices)
D = Drugs/Narcotics
N = Not Applicable (Mutually Exclusive)
Data Element 8A-Bias Motivation
Bias Motivation is used to indicate whether or not the offense was motivated by the offender’s
bias and, if so, what kind.
Group: A
Format: 2-Character Numeric
Position: 62–63 Bias Motivation 1
64–65 Bias Motivation 2
66–67 Bias Motivation 3
68–69 Bias Motivation 4
70–71 Bias Motivation 5
Occurrence: Once to 5 times per Offense Segment
Mandatory: Yes Bias Motivation 1
Optional Bias Motivations 2–5
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 49
Table 3-19 Bias Motivation Edit Description
Bias Motivation Data Element Edits
Associated Error
Data Element Edit Description
Code
(Bias Motivation) The referenced data element in an Incident
must contain data when the referenced data element is
Data Element 8A 201
mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
(Bias Motivation) The referenced data element must contain
Data Element 8A a valid data value when it is entered; blank is permissible on 204
nonmandatory fields.
(Bias Motivation) The referenced data element in error is one
Data Element 8A that contains multiple data values. When more than one 206
code is entered, none can be duplicate codes.
(Bias Motivation) The data element in error can have
multiple data values and was entered with multiple values.
However, mutually exclusive values cannot be entered with
any other data value. Refer to individual data elements for
mutually exclusive data values.
• 207A ERROR MUTUALLY EXCLUSIVE VALUE –
Data Element 8A SUSPECTED OF USING 207
• 207B ERROR MUTUALLY EXCLUSIVE VALUE –
BIAS MOTIVATION
• 207C ERROR MUTUALLY EXCLUSIVE VALUE –
CRIMINAL ACTIVITY/GANG INFORMATION
• 207D ERROR MUTUALLY EXCLUSIVE VALUE –
WEAPON CODE
(Bias Motivation) Must be 88 = None when Data Element 6
Data Element 8A 270
(UCR Offense Code) is 09C = Justifiable Homicide.
Data Values: Race/Ethnicity/Ancestry
11 = Anti-White
12 = Anti-Black or African American
13 = Anti-American Indian or Alaska Native
14 = Anti-Asian
15 = Anti-Multiple Races, Group
16 = Anti-Native Hawaiian or Other Pacific Islander
31 = Anti-Arab
32 = Anti-Hispanic or Latino
33 = Anti-Other Race/Ethnicity/Ancestry
Religion:
21 = Anti-Jewish
22 = Anti-Catholic
23 = Anti-Protestant
24 = Anti-Islamic (Muslim)
25 = Anti-Other Religion
26 = Anti-Multiple Religions, Group
27 = Anti-Atheism/Agnosticism
6/30/2023 2023.0 NIBRS Technical Specification 50
28 = Anti-Church of Jesus Christ
29 = Anti-Jehovah’s Witness
81 = Anti-Eastern Orthodox (Russian, Greek, Other)
82 = Anti-Other Christian
83 = Anti-Buddhist
84 = Anti-Hindu
85 = Anti-Sikh
Sexual Orientation:
41 = Anti-Gay (Male)
42 = Anti-Lesbian (Female)
43 = Anti-Lesbian, Gay, Bisexual, or Transgender (Mixed Group)
44 = Anti-Heterosexual
45 = Anti-Bisexual
Disability:
51 = Anti-Physical Disability
52 = Anti-Mental Disability
Gender:
61 = Anti-Male
62 = Anti-Female
Gender Identity:
71 = Anti-Transgender
72 = Anti-Gender Non-Conforming
None/Unknown:
88 = None (no bias) (mutually exclusive)
99 = Unknown (offender’s motivation not known) (mutually exclusive)
Data Element 9-Location Type
Location Type is used to report the type of location/premises where each offense took place.
Only one location type may be entered for each offense.
Group: A
Format: 2-Character Numeric
Position: 45–46
Occurrence: Once per Offense Segment
Mandatory: Yes
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 51
Table 3-20 Location Type Edit Description
Location Type Data Element Edits
Associated Error
Data Element Edit Description
Code
(Location Type) The referenced data element in an Incident
must contain data when the referenced data element is
Data Element 9 201
mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
(Location Type) The referenced data element must contain a
Data Element 9 valid data value when it is entered; blank is permissible on 204
nonmandatory fields.
Data Element 9 (Location Type) of 58 = Cyberspace can only
be entered when Data Element 6 Offense Code is one of the
violations listed below:
210 = Extortion/Blackmail
250 = Counterfeiting/Forgery
270 = Embezzlement
280 = Stolen Property Offenses
290 = Destruction/Damage/Vandalism of Property
370 = Pornography/Obscene Material
510 = Bribery
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C = Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
Data Element 9 26H = Money Laundering* 205
39A = Betting/Wagering
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment Violations
13C = Intimidation
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
40A = Prostitution
40B = Assisting or Promoting Prostitution
40C = Purchasing Prostitution
101 = Treason*
103 = Espionage*
*Denotes offenses for federal and tribal LEA reporting only
Data Values: 01 = Air/Bus/Train Terminal
02 = Bank/Savings and Loan
03 = Bar/Nightclub
04 = Church/Synagogue/Temple/Mosque
05 = Commercial/Office Building
06 = Construction Site
6/30/2023 2023.0 NIBRS Technical Specification 52
07 = Convenience Store
08 = Department/Discount Store
09 = Drug Store/Doctor’s Office/Hospital
10 = Field/Woods
11 = Government/Public Building
12 = Grocery/Supermarket
13 = Highway/Road/Alley/Street/Sidewalk
14 = Hotel/Motel/Etc.
15 = Jail/Prison/Penitentiary/Corrections Facility
16 = Lake/Waterway/Beach
17 = Liquor Store
18 = Parking/Drop Lot/Garage
19 = Rental Storage Facility
20 = Residence/Home
21 = Restaurant
23 = Service/Gas Station
24 = Specialty Store
25 = Other/Unknown
37 = Abandoned/Condemned Structure
38 = Amusement Park
39 = Arena/Stadium/Fairgrounds/Coliseum
40 = ATM Separate from Bank
41 = Auto Dealership New/Used
42 = Camp/Campground
44 = Daycare Facility
45 = Dock/Wharf/Freight/Modal Terminal
46 = Farm Facility
47 = Gambling Facility/Casino/Race Track
48 = Industrial Site
49 = Military Installation
50 = Park/Playground
51 = Rest Area
52 = School–College/University
53 = School–Elementary/Secondary
54 = Shelter–Mission/Homeless
55 = Shopping Mall
56 = Tribal Lands
57 = Community Center
58 = Cyberspace
Data Element 10-Number of Premises Entered
Number of Premises Entered is used to enter the total number of structures (premises) entered
when Data Element 6 (UCR Offense Code) is 220 = Burglary/Breaking & Entering and Data
Element 9 (Location Type) is 14 = Hotel/Motel/Etc. or 19 = Rental Storage Facility. Premises
may be the number of individual rooms, units, suites, storage compartments, etc. entered.
6/30/2023 2023.0 NIBRS Technical Specification 53
Group: A
Format: 2-Character Numeric
Position: 47–48
Occurrence: Once per Offense Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is 220 =
Burglary/Breaking & Entering and Data Element 9 (Location Type) is 14 = Hotel/Motel/Etc. or
19 = Rental Storage Facility.
Edits:
Table 3-21 Number of Premises Entered Edit Description
Number of Premises Entered Data Element Edits
Associated
Data Element Edit Description
Error Code
Data Element 10 (Number of Premises Entered) is not a numeric
Data Element 10 202
entry of 01 through 99.
(Number of Premises Entered) When Data Element 10 (Number of
Premises Entered) is entered, Data Element 9 (Location Type) must
Data Element 10 be 14 = Hotel/Motel/Etc. or 19 = Rental Storage Facility, and Data 252
Element 6 (UCR Offense Code) must be 220 = Burglary/Breaking &
Entering.
(Number of Premises Entered) Must be entered if offense code is
Data Element 10 220 = Burglary/Breaking & Entering and if Data Element 9 (Location 257
Type) contains 14 = Hotel/Motel/Etc. or 19 = Rental Storage Facility.
Data Values: 01–99
Data Element 11-Method of Entry
Method of Entry is used when Data Element 6 (UCR Offense Code) is 220 = Burglary/Breaking
& Entering to report whether Force or No Force was used by the burglar to enter the structure.
Group: A
Format: 1-Character Alphabetic
Position: 49
Occurrence: Once per Offense Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is 220 =
Burglary/Breaking & Entering.
Edits:
Table 3-22 Method of Entry Edit Description
Method of Entry Data Element Edits
Associated
Data Element Edit Description
Error Code
(Method of Entry) The referenced data element must contain a
Data Element 11 valid data value when it is entered; blank is permissible on 204
nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 54
Method of Entry Data Element Edits
Associated
Data Element Edit Description
Error Code
(Method of Entry) Data element was not entered; it must be
Data Element 11 entered when UCR Offense Code of 220 = Burglary/Breaking & 253
Entering has been entered.
(Method of Entry) Data element only applies to UCR Offense
Code of 220 = Burglary/Breaking & Entering. Since a Burglary
Data Element 11 254
offense was not entered, the Method of Entry should not have
been entered.
Data Values: F = Force
N = No Force
Data Element 12-Type Criminal Activity/Gang Information
Type Criminal Activity/Gang Information is used to indicate the criminal activity/gang
information of the offenders for certain offenses.
Group: A
Format: 1-Character Alphabetic
Position: 50-Activity 1
51-Activity 2
52-Activity 3
Occurrence: 3 times per Offense Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is:
• 250 = Counterfeiting/Forgery
• 280 = Stolen Property Offenses
• 30C = Smuggling Illegal Aliens*
• 35A = Drug/Narcotic Violations
• 35B = Drug Equipment Violations
• 39C = Gambling Equipment Violations
• 370 = Pornography/Obscene Material
• 49A = Harboring Escapee/Concealing Arrest*
• 520 = Weapon Law Violations
• 521 = Violation of National Firearms Act of 1934*
• 522 = Weapons of Mass Destruction*
• 526 = Explosives*
• 58A = Import Violations*
• 58B = Export Violations*
• 61A = Federal Liquor Offenses*
• 61B = Federal Tobacco Offenses*
• 620 = Wildlife Trafficking*
• 720 = Animal Cruelty
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 55
Edits:
Table 3-23 Type Criminal Activity/Gang Information Edit Description
Type of Criminal Activity/Gang Information Element Edits
Associated Error
Data Element Edit Description
Code
(Type Criminal Activity/Gang Information) The referenced
Data Element 12 data element must contain a valid data value when it is 204
entered; blank is permissible on nonmandatory fields.
(Type Criminal Activity/Gang Information) The referenced
data element in error is one that contains multiple data
Data Element 12 206
values. When more than one code is entered, none can be
duplicate codes.
(Type Criminal Activity/Gang Information) The data element
in error can have multiple data values and was entered with
Data Element 12 multiple values. However, mutually exclusive values cannot 207
be entered with any other data value. Refer to individual
data elements for mutually exclusive data values.
6/30/2023 2023.0 NIBRS Technical Specification 56
Type of Criminal Activity/Gang Information Element Edits
Associated Error
Data Element Edit Description
Code
(Type Criminal Activity/Gang Information) Type Criminal
Activity codes of B, C, D, E, O, P, T, or U can only be
entered when the UCR Offense Code is:
250 = Counterfeiting/Forgery
280 = Stolen Property Offenses
30C = Smuggling Illegal Aliens*
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
39C = Gambling Equipment Violations
370 = Pornography/Obscene Material
49A = Harboring Escapee/Concealing Arrest*
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
Data Element 12 *Denotes offenses for federal and tribal LEA reporting only 219
(Type Criminal Activity/Gang Information) Gang information
codes of J, G, and N can only be entered
when the UCR Offense Code is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
11D = Fondling
120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
(Type Criminal Activity/Gang Information) Criminal Activity
codes of A, F, I, and S can only be entered when the UCR
Offense Code is:
720 = Animal Cruelty
6/30/2023 2023.0 NIBRS Technical Specification 57
Type of Criminal Activity/Gang Information Element Edits
Associated Error
Data Element Edit Description
Code
Data Element 12 (Type Criminal Activity/Gang Information)
must be populated with a valid data value and cannot be
blank when Data Element 6 (UCR Offense Code) is:
250 = Counterfeiting/Forgery
280 = Stolen Property Offenses
30C = Smuggling Illegal Aliens*
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
39C = Gambling Equipment Violations
370 = Pornography/Obscene Material
Data Element 12 49A = Harboring Escapee/Concealing Arrest* 220
520 = Weapon Law Violations
521 = Violation of National Firearms Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
720 = Animal Cruelty
*Denotes offenses for federal and tribal LEA reporting only
Data Values: Criminal Activity
A = Simple/Gross Neglect (unintentionally, intentionally, or knowingly failing to
provide food, water, shelter, veterinary care, hoarding, etc.)
B = Buying/Receiving
C = Cultivating/Manufacturing/Publishing (i.e., production of any type)
D = Distributing/Selling
F = Organized Abuse (Dog Fighting and Cock Fighting)
E = Exploiting Children
I = Intentional Abuse and Torture (tormenting, mutilating, maiming, poisoning, or
abandonment)
O = Operating/Promoting/Assisting
P = Possessing/Concealing
S = Animal Sexual Abuse (Bestiality)
T = Transporting/Transmitting/Importing
U = Using/Consuming
Gang Information
J = Juvenile Gang
G = Other Gang
N = None/Unknown (Mutually Exclusive)
Data Element 13-Type Weapon/Force Involved
Type Weapon/Force Involved is used to enter the type of weapon or force used by the offender.
6/30/2023 2023.0 NIBRS Technical Specification 58
Group: A
Format: 2-Character Numeric
Position: 53–54 Weapon 1
56–57 Weapon 2
59–60 Weapon 3
Occurrence: 3 times per Offense Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is:
• 09A = Murder and Nonnegligent Manslaughter
• 09B = Negligent Manslaughter
• 09C = Justifiable Homicide
• 100 = Kidnapping/Abduction
• 11A = Rape
• 11B = Sodomy
• 11C = Sexual Assault With An Object
• 11D = Fondling
• 120 = Robbery
• 13A = Aggravated Assault
• 13B = Simple Assault
• 210 = Extortion
• 520 = Weapon Law Violations
• 521 = Violation of National Firearm Act of 1934*
• 522 = Weapons of Mass Destruction*
• 526 = Explosives*
• 64A = Human Trafficking, Commercial Sex Acts
• 64B = Human Trafficking, Involuntary Servitude
*Denotes offenses for federal and tribal LEA reporting only
Edits:
Table 3-24 Type Weapon/Force Involved Edit Description
Type Weapon/Force Involved Element Edits
Associated Error
Data Element Edit Description
Code
(Type Weapon/Force Involved) The referenced data element
Data Element 13 must contain a valid data value when it is entered; blank is 204
permissible on nonmandatory fields.
(Type Weapon/Force Involved) The referenced data element
Data Element 13 in error is one that contains multiple data values. When more 206
than one code is entered, none can be duplicate codes.
(Type Weapon/Force Involved) The data element in error can
have multiple data values and was entered with multiple
Data Element 13 values. However, mutually exclusive values cannot be 207
entered with any other data value. Refer to individual data
elements for mutually exclusive data values.
6/30/2023 2023.0 NIBRS Technical Specification 59
Type Weapon/Force Involved Element Edits
Associated Error
Data Element Edit Description
Code
(Type Weapon/Force Involved) must be populated with a
valid data value and cannot be blank when Data Element 6
(UCR Offense Code) is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
09C = Justifiable Homicide
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
Data Element 13 11D = Fondling 221
120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
*Denotes offenses for federal and tribal LEA reporting only
(Type of Weapon/Force Involved) Type of Weapon/Force
Involved can only be entered when the UCR Offense Code is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
09C = Justifiable Homicide
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
11D = Fondling
Data Element 13 120 = Robbery 222
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
*Denotes offenses for federal and tribal LEA reporting only
(Type Weapon/Force Involved) If an Offense Segment (Level
2) was submitted for 13B = Simple Assault, Data Element 13
(Type Weapon/Force Involved) can only have codes of
Data Element 13 265
40 = Personal Weapons, 90 = Other, 95 = Unknown, and
99 = None. All other codes are not valid because they do not
relate to a simple assault.
6/30/2023 2023.0 NIBRS Technical Specification 60
Type Weapon/Force Involved Element Edits
Associated Error
Data Element Edit Description
Code
(Type Weapon/Force Involved) If a homicide offense is
submitted, Data Element 13 (Type Weapon/Force Involved)
Data Element 13 267
cannot have 99 = None. Some type of weapon/force must be
used in a homicide offense.
(Type Weapon/Force Involved) If Data Element 6 (UCR
Offense Code) is 13B = Simple Assault and the weapon
Data Element 13 involved is 11 = Firearm, 12 = Handgun, 13 = Rifle, 269
14 = Shotgun, or 15 = Other Firearm, then the offense should
instead be classified as 13A = Aggravated Assault.
Data Values: 11 = Firearm
12 = Handgun
13 = Rifle
14 = Shotgun
15 = Other Firearm
20 = Knife/Cutting Instrument (knives, razors, hatchets, axes, cleavers, scissors,
glass, broken bottles, ice picks, etc.)
30 = Blunt Object (baseball bats, butt of handgun, clubs, bricks, jack handles, tire
irons, bottles, etc.)
35 = Motor Vehicle/Vessel
40 = Personal Weapons (hands, fist, feet, arms, teeth, etc.)
50 = Poison
60 = Explosives
65 = Fire/Incendiary Device
70 = Drugs/Narcotics/Sleeping Pills
85 = Asphyxiation
90 = Other (BB guns, pellet guns, tasers, pepper spray, stun guns, etc.)
95 = Unknown
99 = None (Mutually Exclusive)
Data Element 13-Automatic Weapon Indicator
Automatic Weapon Indicator is used to indicate whether a firearm identified in Data Element 13
(Type Weapons/Force Involved) is an automatic firearm (i.e., any firearm that shoots or is
designed to shoot more than one shot at a time by a single pull of the trigger without manual
reloading).
Group: A
Format: 1-Character Alphabetic
Position: 55 Indicator 1
58 Indicator 2
61 Indicator 3
Occurrence: 3 times per Offense Segment
Mandatory: Conditional
6/30/2023 2023.0 NIBRS Technical Specification 61
Note: Reporting agencies should insert the letter “A” in this data element to indicate an
automatic weapon was involved in an incident. Reporting agencies should leave this data
element blank if an automatic weapon was not involved in the incident.
Edits:
Table 3-25 Automatic Weapon Indicator Edit Description
Automatic Weapon Indicator Element Edits
Associated
Data Element Edit Description
Error Code
(Automatic Weapon Indicator) The referenced data element must
Data Element 13 contain a valid data value when it is entered; blank is permissible 204
on nonmandatory fields.
(Automatic Weapon Indicator) Must be A = Automatic or
Data Element 13 255
blank = Not Automatic.
(Automatic Weapon Indicator) In Data Element 13 (Type of
Weapon/Force Involved), A = Automatic is the third character of
code. It is valid only with the following codes:
11 = Firearm (Type Not Stated)
12 = Handgun
Data Element 13 13 = Rifle 258
14 = Shotgun
15 = Other Firearm
A weapon code other than those mentioned was entered with the
automatic indicator. An automatic weapon is, by definition, a
firearm.
Data Values: A = Automatic
(blank) = Not Automatic
3.3.4 Property Segment
The Property Segment is used to describe the type, value, and (for drugs and narcotics seized in
drug cases) quantity of property involved in the incident and is only submitted for
Kidnapping/Abduction, Crimes against Property, Drug/Narcotic Offenses, and Gambling
Offenses. A separate Property Segment must be submitted for each type of property loss,
recovery, seizure, etc., that occurred in the incident.
Note: In addition to the data elements specified, the Property Segment also contains the Header
Data Elements identified in Section 3.3.1, as well as Data Element 1 (ORI) and Data Element 2
(Incident Number) included in the Administrative Segment, Section 3.3.2.
Data Element 14-Type Property Loss/Etc.
Type Property Loss/Etc. is used to describe the type of property loss, recovery, seizure, etc.,
which occurred in the incident.
Group: A
Format: 1-Character Numeric
Position: 38
Occurrence: Once per Property Segment
Mandatory: Conditional
6/30/2023 2023.0 NIBRS Technical Specification 62
This data element is mandatory when Data Element 6 (UCR Offense Code) contains
Kidnapping/Abduction, Crimes against Property, Drug/Narcotic Offenses, Liquor and Tobacco
Violations*, Violation of National Firearm Act of 1934*, Weapons of Mass Destruction*,
Explosives Violation*, Money Laundering*, Commerce Violations*, Gambling Offenses, or
Wildlife Trafficking*.
*Denotes offenses for federal and tribal LEA reporting only
Edits:
Table 3-26 Type Property Loss/Etc. Edit Description
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
Segment Level 3 (Property Segment) must be submitted with
Data Element 14 (Type Property Loss/Etc.) as 7 = Stolen/Etc.
before it can be submitted as 5 = Recovered for the same
property in Data Element 15 (Property Description). Any
property being reported as recovered must first be reported as
stolen. Exceptions to this rule are:
1) When Data Element 6 (UCR Offense Code) contains an
Data Element 14 offense that allows property to be recovered without first 072
being stolen in that same incident (i.e.,
250 = Counterfeiting/Forgery and 280 = Stolen Property
Offenses, 58B = Export Violations*).
2) When a vehicle was stolen and the recovered property in
Data Element 15 (Property Description) is 38 = Vehicle
Parts/ Accessories.
*Denotes offenses for federal and tribal LEA reporting only
(Type Property Loss/Etc.) Must be 1 = None or 8 = Unknown
when Data Element 6 (UCR Offense Code) contains an offense
of Crimes Against Property, 100 = Kidnapping/Abduction,
Drug/Narcotic Offenses, 521 = Violation of National Firearms
Data Element 14 Act of 1934*, 522 = Weapons of Mass Destruction*, 526 = 077
Explosives*, 26H = Money Laundering*, Commerce Violations*,
or Gambling Offenses and Data Element 7 (Offense
Attempted/Completed) is A = Attempted.
*Denotes offenses for federal and tribal LEA reporting only
(Type Property Loss/Etc.) Must be 1 = None or 5 = Recovered 078
when Data Element 6 (UCR Offense Code) is 280 = Stolen
Data Element 14
Property Offenses and Data Element 7 (Offense Attempted/
Completed) is C = Completed.
(Type Property Loss/Etc.) Must be 1 = None, 5 = Recovered, 078
7 = Stolen/Etc., or 8 = Unknown when Data Element 6 (UCR
Data Element 14 Offense Code) is 100 = Kidnapping/Abduction, 220 = Burglary/
Breaking & Entering, or 510 = Bribery and Data Element 7
(Offense Attempted/Completed) is C = Completed.
6/30/2023 2023.0 NIBRS Technical Specification 63
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
(Type Property Loss/Etc.) Must be 1 = None or 6 = Seized when 078
Data Element 6 (UCR Offense Code) is 35A = Drug/Narcotic
Offenses or 35B = Drug Equipment Violations, 521 = Violation of
National Firearm Act of 1934*, 522 = Weapons of Mass
Data Element 14 Destruction*, 526 = Explosives*, 58A = Import Violations*, 61A =
Federal Liquor Offenses*, 61B = Tobacco Offenses*, 620 =
Wildlife Trafficking*, and Data Element 7 (Offense
Attempted/Completed) is Completed.
*Denotes offenses for federal and tribal LEA reporting only
(Type Property Loss/Etc.) Must be 2 = Burned when Data 078
Data Element 14 Element 6 (UCR Offense Code) is 200 = Arson and Data
Element 7 (Offense Attempted/Completed) is C = Completed.
(Type Property Loss/Etc.) Must be 3 = Counterfeited/Forged, 078
5 = Recovered, or 6 = Seized when Data Element 6 (UCR
Offense Code) is 250 = Counterfeiting/Forgery, 58B = Export
Data Element 14 Violations*, and Data Element 7 (Offense Attempted/Completed)
is C = Completed.
*Denotes offenses for federal and tribal LEA reporting only
(Type Property Loss/Etc.) Must be 4 = Destroyed/Damaged/ 078
Vandalized when Data Element 6 (UCR Offense Code) is
Data Element 14
290 = Destruction/Damage/Vandalism of Property and Data
Element 7 (Offense Attempted/Completed) is C = Completed.
(Type Property Loss/Etc.) Must be 5 = Recovered or 7 = Stolen/
Etc. when Data Element 6 (UCR Offense Code) is any of the
following and Data Element 7 (Offense Attempted/Completed) is
C = Completed:
120 = Robbery
210 = Extortion/Blackmail
23A = Pocket-picking
23B = Purse-snatching
23C = Shoplifting
23D = Theft from Building
23E = Theft from Coin-Operated Machine or Device
23F = Theft from Motor Vehicle
Data Element 14 23G = Theft of Motor Vehicle Parts or Accessories 078
23H = All Other Larceny
240 = Motor Vehicle Theft
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C = Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
270 = Embezzlement
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 64
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
Data Element 14 (Type Property Loss/Etc.) must be 6 = Seized
when Data Element 6 (UCR Offense Code) is any of the
following and Data Element 7 (Offense Attempted/Completed) is
C = Completed:
Data Element 14 078
39A = Betting/Wagering
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment Violation
39D = Sports Tampering
6/30/2023 2023.0 NIBRS Technical Specification 65
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 1 = None, then an Offense Segment
must be submitted in which Data Element 6 (UCR Offense
Code) contains a valid offense for Type Loss 1 = None and an
applicable Data Element 7 (Offense Attempted/Completed) must
exist for that offense.
The following offense/attempted-completed combinations are
valid for Type Loss 1 = None:
200 = Arson-Attempted
510 = Bribery-Attempted/Completed
220 = Burglary/Breaking & Entering-Attempted/Completed
250 = Counterfeiting/Forgery-Attempted
290 = Destruction/Damage/Vandalism of Property-Attempted
35A = Drug/Narcotic Violations-Attempted/Completed
35B = Drug Equipment Violations-Attempted/Completed
270 = Embezzlement-Attempted
210 = Extortion/Blackmail-Attempted
26A = False Pretenses/Swindle/Confidence Game-Attempted
26B = Credit Card/Automated Teller Machine Fraud- Attempted
26C = Impersonation-Attempted
26D = Welfare Fraud-Attempted
26E = Wire Fraud-Attempted
26F = Identity Theft-Attempted
26G = Hacking/Computer Invasion-Attempted
39A = Betting/Wagering-Attempted
Data Element 14 39B = Operating/Promoting/Assisting Gambling-Attempted 081
39C = Gambling Equipment Violations- Attempted
39D = Sports Tampering-Attempted
100 = Kidnapping/Abduction-Attempted/Completed
23A = Pocket-picking-Attempted
23B = Purse-snatching-Attempted
23C = Shoplifting-Attempted
23D = Theft From Building-Attempted
23E = Theft From Coin-Operated Machine or Device-Attempted
23F = Theft From Motor Vehicle-Attempted
23G = Theft of Motor Vehicle Parts or Accessories-Attempted
23H = All Other Larceny- Attempted
240 = Motor Vehicle Theft-Attempted
120 = Robbery-Attempted
280 = Stolen Property Offenses-Attempted/Completed
26H = Money Laundering*-Attempted
521 = Violation of National Firearms Act of 1934*-
Attempted/Completed
522 = Weapons of Mass Destruction*-Attempted/Completed
526 = Explosives*-Attempted/Completed
58A = Import Violations*-Attempted/Completed
58B = Export Violations*-Attempted
61A = Federal Liquor Offenses*-Attempted/Completed
61B = Federal Tobacco Offenses*-Attempted/Completed
620 = Wildlife Trafficking*-Attempted/Completed
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 66
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 2 = Burned, then an Offense Segment
must be submitted in which Data Element 6 (UCR Offense
Data Element 14 081
Code) contains an offense of 200 = Arson, and Data Element
7(Offense Attempted/Completed) must be C = Completed.
If Type Property Loss is 3 = Counterfeiting/Forgery, then an
Offense Segment must be submitted in which Data Element 6
(UCR Offense Code) contains an offense of
Data Element 14 250 = Counterfeiting/Forgery, 58B = Export Violations*, and 081
Data Element 7(Offense Attempted/Completed) must be C =
Completed.
*Denotes offenses for federal and tribal LEA reporting only
If Type Property Loss is 4 = Damaged/Destroyed, then an
Offense Segment must be submitted in which Data Element 6
Data Element 14 (UCR Offense Code) contains an offense of 290 = Destruction/ 081
Damage/Vandalism of Property, and Data Element 7 (Offense
Attempted/Completed) must be C = Completed.
6/30/2023 2023.0 NIBRS Technical Specification 67
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 5 = Recovered, then an Offense
Segment must be submitted in which Data Element 6 (UCR
Offense Code) contains a valid offense for Type Loss 5 =
Recovered and Data Element 7 (Offense Attempted/Completed)
must be C = Completed.
The following completed offenses are valid for Type Loss
5 = Recovered:
510 = Bribery
220 = Burglary/Breaking & Entering
250 = Counterfeiting/Forgery
270 = Embezzlement
210 = Extortion/Blackmail
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C= Impersonation
26D = Welfare Fraud
Data Element 14 081
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
100 = Kidnapping/Abduction
23A = Pocket-picking
23B = Purse-snatching
23C = Shoplifting
23D = Theft From Building
23E = Theft From Coin Operated Machine
23F = Theft From Motor Vehicle
23G = Theft of Motor Vehicle Parts or Accessories
23H = All Other Larceny
58B = Export Violations*
240 = Motor Vehicle Theft
120 = Robbery
280 = Stolen Property Offenses
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 68
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 6 = Seized, then an Offense Segment
must be submitted in which Data Element 6 (UCR Offense
Code) contains a valid offense for Type Loss 6 = Seized and
Data Element 7 (Offense Attempted/Completed) must be
C = Completed.
The following completed offenses are valid for Type Loss
6 = Seized:
250 = Counterfeiting/Forgery
35A = Drug/Narcotics Violations
35B = Drug Equipment Violations
Data Element 14 39A = Betting/Wagering 081
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment
39D = Sports Tampering
521 = Violation of National Firearms Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 69
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 7 = Stolen/Etc., then an Offense
Segment must be submitted in which Data Element 6 (UCR
Offense Code) contains a valid offense for Type Loss 7 =
Stolen/Etc. and Data Element 7 (Offense Attempted/Completed)
must be C = Completed.
The following completed offenses are valid for Type Loss
7 = Stolen/Etc.:
510 = Bribery
220 = Burglary/Breaking & Entering
270 = Embezzlement
210 = Extortion/Blackmail
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine Fraud
26C= Impersonation
Data Element 14 26D = Welfare Fraud 081
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
100 = Kidnapping/Abduction
23A = Pocket-picking
23B = Purse-snatching
23C = Shoplifting
23D = Theft From Building
23E = Theft From Coin Operated Machine
23F = Theft From Motor Vehicle
23G = Theft of Motor Vehicle Parts or Accessories
23H = All Other Larceny
240 = Motor Vehicle Theft
120 = Robbery
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 70
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
If Type Property Loss is 8 = Unknown, then an Offense
Segment must be submitted in which Data Element 6 (UCR
Offense Code) contains a valid offense for Type Loss
8 = Unknown and an applicable Data Element 7 (Offense
Attempted/Completed) must exist for that offense.
The following Offense/Attempted-Completed combinations are
valid for Type Loss 8 = Unknown:
200 = Arson-Attempted
510 = Bribery-Attempted/Completed
220 = Burglary/Breaking & Entering-Attempted/Completed
250 = Counterfeiting/Forgery-Attempted
290 = Destruction/Damage/Vandalism of Property-Attempted
35A = Drug/Narcotic Violations-Attempted
35B = Drug Equipment Violations-Attempted
270 = Embezzlement-Attempted
210 = Extortion/Blackmail-Attempted
26A = False Pretenses/Swindle/Confidence Game-Attempted
26B = Credit Card/Automated Teller Machine Fraud- Attempted
26C = Impersonation-Attempted
26D = Welfare Fraud-Attempted
26E = Wire Fraud-Attempted
26F = Identity Theft-Attempted
26G = Hacking/Computer Invasion- Attempted
Data Element 14 39A = Betting/Wagering-Attempted 081
39B = Operating/Promoting/Assisting Gambling-Attempted
39C = Gambling Equipment Violations- Attempted
39D = Sports Tampering-Attempted
100 = Kidnapping/Abduction-Attempted/Completed
23A = Pocket-picking-Attempted
23B = Purse-snatching-Attempted
23C = Shoplifting-Attempted
23D = Theft From Building-Attempted
23E = Theft From Coin-Operated Machine or Device-Attempted
23F = Theft From Motor Vehicle-Attempted
23G = Theft of Motor Vehicle Parts or Accessories-Attempted
23H = All Other Larceny- Attempted
240 = Motor Vehicle Theft- Attempted
120 = Robbery-Attempted
280 = Stolen Property Offenses-Attempted
26H = Money Laundering*-Attempted
521 = Violation of National Firearms Act of 1934*-Attempted
522 = Weapons of Mass Destruction*-Attempted
526 = Explosives*-Attempted
58A = Import Violations*-Attempted
58B = Export Violations*-Attempted
61A = Federal Liquor Offenses*-Attempted
61B = Federal Tobacco Offenses*-Attempted
620 = Wildlife Trafficking*-Attempted
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 71
Type Property Loss Element Edits
Associated
Data Element Edit Description
Error Code
The referenced data element in an incident must contain data
when the referenced data element is mandatory or when the
Data Element 14 301
conditions are met for data that must be entered into a
conditionally mandatory field.
(Type Property Loss/Etc.) The referenced data element must
Data Element 14 contain a valid data value when it is entered; blank is 304
permissible on nonmandatory fields.
(Type Property Loss/Etc.) Referenced data elements must be
blank when one of the following criteria is met:
1) If Data Element 14 (Type Property Loss/Etc.) is
8 = Unknown, then Data Elements 15 through 22 must be
blank.
2) If Data Element 14 (Type Property Loss/Etc.) is
1 = None and Data Element 6 (UCR Offense Code) is
35A = Drug/ Narcotic Violations, then Data Elements 15
through 19 and 21 through 22 must be blank, and Data
Data Element 14 Element 20 (Suspected Drug Type) must be entered. 352
• Data Element 20 Exception-The incident consists of
multiple offense segments where at least one offense
code is not 35A = Drug/Narcotic Violations and requires
property to be entered.
3) If Data Element 14 (Type Property Loss/Etc.) is
1 = None and the incident has no Offense Segments with a
Data Element 6 (UCR Offense Code) of 35A = Drug/
Narcotic Violations, then Data Elements 15 through 22 must
be blank.
(Type Property Loss/Etc.) is 2 = Burned, 3 = Counterfeited/
Forged, 4 = Destroyed/Damaged/Vandalized, 5 = Recovered,
Data Element 14 372
6 = Seized, or 7 = Stolen/Etc., Data Elements 15 through 22
must have applicable entries in the segment.
Data Values: 1 = None
2 = Burned (includes damage caused in fighting the fire)
3 = Counterfeited/Forged
4 = Destroyed/Damaged/Vandalized
5 = Recovered (to impound property that was previously stolen)
6 = Seized (to impound property that was not previously stolen)
7 = Stolen/Etc. (includes bribed, defrauded, embezzled, extorted, ransomed,
robbed, etc.)
8 = Unknown
Data Element 15-Property Description
Property Description is used to enter description of the property that was burned, counterfeited,
destroyed/damaged/vandalized, etc., as a result of the incident.
When more than 10 types of property are involved, enter the data values and values of property
for the 9 most valuable in Data Element 15 (Property Description) and Data Element 16 (Value
6/30/2023 2023.0 NIBRS Technical Specification 72
of Property), respectively, and enter 77 = Other in Description 10 (Data Element 15) along with
the remaining property’s total value in Value 10 (Data Element 16).
Group: A
Format: 2-Character Numeric
Position: 39–40 Description 1
58–59 Description 2
77–78 Description 3
96–97 Description 4
115–116 Description 5
134–135 Description 6
153–154 Description 7
172–173 Description 8
191–192 Description 9
210–211 Description 10
Occurrence: 10 times per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 14 (Type Property Loss/Etc.) is 2 = Burned,
3 = Counterfeited/Forged, 4 = Destroyed/ Damaged/Vandalized, 5 = Recovered, 6 = Seized, or 7
= Stolen/Etc.
Edits:
Note: Multiple values of the same Property Description are not allowed, i.e., only enter aircraft
or automobile one time as property description. Do not enter multiples of a single property
description.
Table 3-27 Property Description Edit Description
Property Description Element Edits
Associated Error
Data Element Edit Description
Code
Segment Level 3 (Property Segment) must be submitted with
Data Element 14 (Type Property Loss/Etc.) as 7=
Stolen/Etc. before it can be submitted as 5 = Recovered for
the same property in Data Element 15 (Property Description).
Any property being reported as recovered must first be
reported as stolen. There are exceptions to this rule:
1) When Data Element 6 (UCR Offense Code) contains an
offense that allows property to be recovered without first
Data Element 15 072
being stolen in that same incident (i.e., 250 =
Counterfeiting/Forgery and 280 = Stolen Property Offenses,
58B = Export Violations*).
2) When a vehicle was stolen and the recovered property in
Data Element 15 (Property Description) is 38 = Vehicle
Parts/Accessories.
*Denotes offenses for federal and tribal LEA reporting only
(Property Description) The referenced data element must
Data Element 15 contain a valid data value when it is entered; blank is 304
permissible on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 73
Property Description Element Edits
Associated Error
Data Element Edit Description
Code
(Property Description) The referenced data element in error is
one that contains multiple data values. When more than one
Data Element 15 code is entered, none can be duplicate codes. Refer to 306
individual data elements for exceptions.
Data Element 15 (Property Description) is 88 = Pending
Data Element 15 Inventory, but Data Element 16 (Value of Property) is not $1. 353
(Property Description) Must be one of the following:
03 = Automobiles
05 = Buses
24 = Other Motor Vehicles
Data Element 15 28 = Recreational Vehicles 359
37 = Trucks
When Data Element 6 (UCR Offense Code) is 240 = Motor
Vehicle Theft, and Data Element 18 (Number of Stolen Motor
Vehicles) or Data Element 19 (Number of Recovered Motor
Vehicles) contains a data value of 01-99.
(Property Description) At least one Data Element 15 (Property
Description) code must be entered when Data Element 14
(Type Property Loss/Etc.) contains Property Segment(s) for:
2 = Burned
Data Element 15 3 = Counterfeited/Forged 375
4 = Destroyed/Damaged/Vandalized
5 = Recovered
6 = Seized
7 = Stolen/Etc.
(Property Description)
1) If 35A = Drug/Narcotic Violation Offense exists without a
35B = Drug Equipment Violation Offense and a Property
Type of 6 = Seized and Property Description of 11 =
Drug/Narcotic Equipment and no other crimes requiring a
Data Element 15 Property Segment exist. 387
2) If 35B = Drug Equipment Violation Offense exists without
35A = Drug/Narcotic Violation Offense and a Property
Type of 6 = Seized and Property Description of 10 =
Drugs/ Narcotics and no other crimes requiring a Property
Segment exist.
(Property Description) must contain a data value that is logical
for one or more of the Crime Against Property offenses
entered in Data Element 6 (UCR Offense Code). See Table 3-
28: Illogical Property Description for the Offense(s) Submitted.
Illogical combinations include:
1) Property descriptions for structures are illogical with
Data Element 15 220 = Burglary/Breaking & Entering or 240 = Motor 390
Vehicle Theft
2) Property descriptions for items that would not fit in a
purse
or pocket (aircraft, vehicles, structures, a person’s
identity, watercraft, etc.) are illogical with 23A = Pocket-
picking or 23B = Purse-snatching
6/30/2023 2023.0 NIBRS Technical Specification 74
Property Description Element Edits
Associated Error
Data Element Edit Description
Code
3) Property descriptions that cannot be shoplifted due to
other UCR definitions (aircraft, vehicles, structures, a
person’s identity, watercraft, etc.) are illogical with
23C = Shoplifting
4) Property descriptions for vehicles and structures are
illogical with 23D = Theft from Building, 23E = Theft from
Coin-Operated Machine or Device, 23F = Theft from
Motor Vehicle, and 23G = Theft of Motor Vehicle Parts or
Accessories
5) Property descriptions for vehicles are illogical with
23H = All Other Larceny
Data Values: 01 = Aircraft
02 = Alcohol
03 = Automobiles
04 = Bicycles
05 = Buses
06 = Clothes/Furs
07 = Computer Hardware/Software
08 = Consumable Goods
09 = Credit/Debit Cards
10 = Drugs/Narcotics
11 = Drug/Narcotic Equipment
12 = Farm Equipment
13 = Firearms
14 = Gambling Equipment
15 = Heavy Construction/Industrial Equipment
16 = Household Goods
17 = Jewelry/Precious Metals/Gems
18 = Livestock
19 = Merchandise
20 = Money
21 = Negotiable Instruments
22 = Nonnegotiable Instruments
23 = Office-type Equipment
24 = Other Motor Vehicles
25 = Purses/Handbags/Wallets
26 = Radios/TVs/VCRs/DVD Players
27 = Recordings–Audio/Visual
28 = Recreational Vehicles
29 = Structures–Single Occupancy Dwellings
30 = Structures–Other Dwellings
31 = Structures–Other Commercial/Business
32 = Structures–Industrial/Manufacturing
33 = Structures–Public/Community
34 = Structures–Storage
6/30/2023 2023.0 NIBRS Technical Specification 75
35 = Structures–Other
36 = Tools
37 = Trucks
38 = Vehicle Parts/Accessories
39 = Watercraft
41 = Aircraft Parts/Accessories
42 = Artistic Supplies/Accessories
43 = Building Materials
44 = Camping/Hunting/Fishing Equipment/Supplies
45 = Chemicals
46 = Collections/Collectibles
47 = Crops
48 = Documents/Personal or Business
49 = Explosives
59 = Firearm Accessories
64 = Fuel
65 = Identity Documents
66 = Identity–Intangible
67 = Law Enforcement Equipment
68 = Lawn/Yard/Garden Equipment
69 = Logging Equipment
70 = Medical/Medical Lab Equipment
71 = Metals, Non-Precious
72 = Musical Instruments
73 = Pets
74 = Photographic/Optical Equipment
75 = Portable Electronic Communications
76 = Recreational/Sports Equipment
77 = Other
78 = Trailers
79 = Watercraft Equipment/Parts/Accessories
80 = Weapons–Other
88 = Pending Inventory
3.3.4.2.1 Illogical Property Description for the Offense(s) Submitted
Property offenses identified below cannot have illogical property descriptions for stolen and/or
recovered property. This includes Window submissions of recovered property. When the offense
has fewer allowable values than not allowed, the allowable values are shown instead. These are
indicated by YES or NO under the Allowed column. If multiple property offenses are submitted
in an incident and one or more property offenses not listed below are present (e.g.,
embezzlement), then this edit is bypassed.
Table 3-28 Illogical Property Description by Offense
Offense Allowed Property Descriptions
220 BURGLARY 29-Structures-Single Occupancy
NO
240 MOTOR VEHICLE THEFT Dwellings
6/30/2023 2023.0 NIBRS Technical Specification 76
Offense Allowed Property Descriptions
NO 30-Structures-Other Dwellings
NO 31-Structures-Commercial/Business
NO 32-Structures-Industrial/Manufacturing
NO 33-Structures-Public/Community
NO 34-Structures- Storage
NO 35-Structures-Other
NO 01-Aircraft
NO 03-Automobiles
NO 04-Bicycles
NO 05-Buses
NO 12-Farm Equipment
15-Heavy Construction/Industrial
NO
Equipment
NO 18-Livestock
NO 24-Other Motor Vehicles
NO 28-Recreational Vehicles
23A LARCENY/POCKET-PICKING 29-Structures-Single Occupancy
NO
23B LARCENY/PURSE-SNATCHING Dwellings
NO 30-Structures-Other Dwellings
NO 31-Structures-Commercial/Business
NO 32-Structures-Industrial/Manufacturing
NO 33-Structures-Public/Community
NO 34-Structures-Storage
NO 35-Structures-Other
NO 37-Trucks
NO 39-Watercraft
NO 66 - Identity–Intangible
NO 78-Trailers
NO 01-Aircraft
NO 03-Automobiles
NO 05-Buses
NO 12-Farm Equipment
15-Heavy Construction/Industrial
NO
Equipment
NO 18-Livestock
23C LARCENY/SHOPLIFTING
NO 24-Other Motor Vehicles
NO 28-Recreational Vehicles
29-Structures-Single Occupancy
NO
Dwellings
NO 30-Structures-Other Dwellings
NO 31-Structures-Commercial/Business
NO 32-Structures-Industrial/Manufacturing
NO 33-Structures-Public/Community
6/30/2023 2023.0 NIBRS Technical Specification 77
Offense Allowed Property Descriptions
NO 34-Structures-Storage
NO 35-Structures-Other
NO 37-Trucks
NO 39-Watercraft
NO 03-Automobiles
NO 05-Buses
NO 24-Other Motor Vehicles
NO 28-Recreational Vehicles
23D LARCENY/THEFT FROM BUILDING
29-Structures-Single Occupancy
23E LARCENY/THEFT FROM COIN-OPERATED NO
Dwellings
MACHINE OR DEVICE
NO 30-Structures-Other Dwellings
23F LARCENY/THEFT FROM MOTOR VEHICLE
NO 31-Structures-Commercial/Business
23G LARCENY/THEFT OF MOTOR VEHICLE
NO 32-Structures-Industrial/Manufacturing
PARTS/ACCESSORIES
NO 33-Structures-Public/Community
NO 34-Structures-Storage
NO 35-Structures-Other
NO 37-Trucks
NO 03-Automobiles
NO 05-Buses
23H LARCENY/ALL OTHER LARCENY NO 24-Other Motor Vehicles
NO 28-Recreational Vehicles
NO 37-Trucks
Data Element 16-Value of Property
Value of Property is used to enter the total dollar value (in whole dollars) of the property that
was burned (includes damage caused in fighting the fire), counterfeited,
destroyed/damaged/vandalized, recovered, seized, stolen, etc., as a result of the incident.
When more than 10 types of property are involved, enter the data values and values of property
for the 9 most valuable in Data Element 15 (Property Description) and Data Element 16 (Value
of Property), respectively, and enter 77 = Other in Description 10 (Data Element 15) along with
the remaining property’s total value in Value 10 (Data Element 16).
Group: A
Format: 9-Character Numeric
Position: 41–49 Value 1
60–68 Value 2
79–87 Value 3
98–106 Value 4
117–125 Value 5
136–144 Value 6
155–163 Value 7
174–182 Value 8
193–201 Value 9
212–220 Value 10
6/30/2023 2023.0 NIBRS Technical Specification 78
Occurrence: 10 times per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 14 (Type Property Loss/Etc.) is 2 = Burned,
3 = Counterfeited/Forged, 4 = Destroyed/ Damaged/Vandalized, 5 = Recovered, 6 = Seized, or 7
= Stolen/Etc.
Edits:
Table 3-29 Value of Property Edit Description
Value of Property Element Edits
Associated
Data Element Edit Description
Error Code
(Value of Property) When Data Element 14 (Type Property
Loss/Etc.) entries are made for both 7 = Stolen/Etc. and
5 = Recovered, the recovered property cannot have property
value(s) greater than corresponding property value(s) reported
stolen.
Note: An exception occurs when Data Element 6 (UCR Offense
Code) contains an offense that allows property to be recovered
Data Element 16 084
without first being stolen in that same incident (i.e.,
250 = Counterfeiting/Forgery and 280 = Stolen Property
Offenses)
Note: This edit also applies when a vehicle was stolen and the
recovered property in Data Element 15 (Property Description) is
38 = Vehicle Parts/Accessories. The value of recovered parts
cannot exceed the value of stolen vehicles.
(Value of Property) Must be numeric entry with zero left-fill. Refer
Data Element 16 302
to individual data element for specific formatting instructions.
(Value of Property) cannot be zero unless Data Element 15
(Property Description) is:
Mandatory zero
09 = Credit/Debit Cards
22 = Nonnegotiable Instruments
Data Element 16 351
48 = Documents–Personal or Business
65 = Identity Documents
66 = Identity–Intangible
Optional zero
77 = Other
Data Element 15 (Property Description) is 88 = Pending
Data Element 16 353
Inventory, but Data Element 16 (Value of Property) is not $1.
(Property Description) Data Element 16 (Value of Property)
Data Element 16 contains a value, but Data Element 15 (Property Description) was 354
not entered.
(Value of Property) Must be blank when Data Element 15
Data Element 16 (Property Description) code is 10 = Drugs/Narcotics and the only 383
offense submitted is a 35A = Drug/Narcotic Violations.
6/30/2023 2023.0 NIBRS Technical Specification 79
Value of Property Element Edits
Associated
Data Element Edit Description
Error Code
(Value of Property) has a code that requires a zero value in Data
Element 16 (Value of Property). Either the wrong property
description code was entered or the property value was not
entered. (This error was formerly error number 340, a warning
message.) Data Element 16 (Value of Property) must be zero
Data Element 16 when Data Element 15 (Property Description) is: 391
09 = Credit/Debit Cards
22 = Nonnegotiable Instruments
48 = Documents–Personal or Business
65 = Identity Documents
66 = Identity–Intangible
Data Values: $0–$999,999,999
Note: When the value is unknown, one dollar ($1.00) which means unknown, i.e., 000000001 =
Unknown, should be entered.
A zero value is mandatory (blanks are acceptable) when Data Element 15 (Property Description)
is:
• 09 = Credit/Debit Cards
• 22 = Nonnegotiable Instruments
• 48 = Documents–Personal or Business
• 65 = Identity Documents
• 66 = Identity–Intangible
A zero value is optional (blanks are acceptable) when Data Element 15 (Property Description) is:
1) 77 = Other
Data Element 17-Date Recovered
Date Recovered is used to record the date property was recovered when it was previously stolen
within the LEA’s jurisdiction. When the recovery date is unknown, enter the date the recovery
was reported. When there is more than one date of recovery for the same property description,
enter the earliest date.
Group: A
Format: 8-Character Numeric (YYYYMMDD)
Position: 50–57 Date 1
69–76 Date 2
88–95 Date 3
107–114 Date 4
126–133 Date 5
145–152 Date 6
164–171 Date 7
183–190 Date 8
202–209 Date 9
221–228 Date 10
6/30/2023 2023.0 NIBRS Technical Specification 80
Occurrence: 10 times per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 14 (Type Property Loss/Etc.) is: 5 =
Recovered.
Edits:
Table 3-30 Date Recovered Edit Description
Date Recovered Element Edits
Associated
Data Element Edit Description
Error Code
(Date Recovered) Each component of the date must be valid;
that is, months must be 01 through 12, days must be 01 through
31, and year must include the century (i.e., 19xx, 20xx). In
addition, days cannot exceed maximum for the month (e.g., June
cannot have 31 days). The date cannot be later than that entered
Data Element 17 within the Month of Electronic submission and Year of Electronic 305
submission fields on the data record. For example, if Month of
Electronic submission and Year of Electronic submission are
06/1999, the recovered date cannot contain any date 07/01/1999
or later. Cannot be earlier than Data Element 3 (Incident
Date/Hour).
(Type Property Loss/Etc.) Must be 5 = Recovered for Data
Data Element 17 355
Element 17 (Date Recovered) to be entered.
Data Element 17 (Date Recovered) was entered, but Data
Data Element 17 Elements 15 (Property Description) and/or 16 (Value of Property) 356
were not entered.
Data Values: Year (YYYY): 1991–Current
Month (MM): 01 = January
02 = February
03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
Day of the Month (DD): 01–31 (depending on the month)
Data Element 18-Number of Stolen Motor Vehicles
Number of Stolen Motor Vehicles is used to indicate how many motor vehicles were stolen when
Data Element 6 (UCR Offense Code) is 240 = Motor Vehicle Theft.
Group: A
Format: 2-Character Numeric
Position: 229–230
6/30/2023 2023.0 NIBRS Technical Specification 81
Occurrence: Once per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is 240 = Motor
Vehicle Theft, Data Element 14 (Type Property Loss/Etc.) is 7 = Stolen/Etc., and Data Element 7
(Offense Attempted/ Completed) is C = Completed. Data Element 15 (Property Description)
must = 03, 05, 24, 28, or 37.
Edits:
Table 3-31 Number of Stolen Motor Vehicles Edit Description
Number of Stolen Vehicles Element Edits
Associated
Data Element Edit Description
Error Code
(Number of Stolen Motor Vehicles) Must be numeric entry with zero
Data Element 18 left-fill. Refer to individual data element for specific formatting 302
instructions.
(Number of Stolen Motor Vehicles) was entered. However, Data
Element 14 (Type Property Loss/Etc.) 7 = Stolen/Etc. was not
Data Element 18 entered, and/or Data Element 6 (UCR Offense Code) of 357
240 = Motor Vehicle Theft was not entered, and/or Data Element 7
(Offense Attempted/Completed) was A = Attempted.
(Number of Stolen Motor Vehicles) Entry must be made for Data
Element 18 (Number of Stolen Motor Vehicles) when Data Element
Data Element 18 6 (UCR Offense Code) is 240 = Motor Vehicle Theft, Data Element 358
7 (Offense Attempted/Completed) is C = Completed, and Data
Element 14 (Type Property Loss/Etc.) is 7 = Stolen/Etc.
(Number of Stolen Motor Vehicles) More than one vehicle code was
entered in Data Element 15 (Property Description), but the number
stolen in Data Element 18 (Number of Stolen Motor Vehicles) is
less than this number. For example, if vehicle codes of
Data Element 18 03 = Automobiles and 05 = Buses were entered as being stolen, 388
then the number stolen must be at least 2, unless the number
stolen was 00 = Unknown.
The exception to this rule is when 00 = Unknown is entered in Data
Element 18.
Data Values: 01 - 99
00 = Unknown
Data Element 19-Number of Recovered Motor Vehicles
Number of Recovered Motor Vehicles is used to indicate how many of the motor vehicles
reported stolen in Data Element 18 (Number of Stolen Motor Vehicles) were recovered. Motor
vehicles recovered that are not first reported stolen by submitting offense 240 = Motor Vehicle
Theft in Data Element 6 (UCR Offense Code) should not be entered.
Group: A
Format: 2-Character Numeric
Position: 231–232
Occurrence: Once per Property Segment
Mandatory: Conditional
6/30/2023 2023.0 NIBRS Technical Specification 82
This data element is mandatory when Data Element 6 (UCR Offense Code) is 240 = Motor
Vehicle Theft, Data Element 14 (Type Property Loss/Etc.) is 5 = Recovered, and Data Element 7
(Offense Attempted/Completed) is C = Completed. Data Element 15 (Property Description) must
= 03, 05, 24, 28, or 37.
Edits:
Table 3-32 Number of Recovered Motor Vehicles Edit Description
Number of Recovered Motor Vehicles Element Edits
Associated
Data Element Edit Description
Error Code
Segment Level 3 (Property Segment) with Segment Action Type
I = Incident Report must contain a data value in Data Element 18
Data Element 19 (Number of Stolen Motor Vehicles) greater than or equal to the data 073
value entered in Data Element 19 (Number of Recovered Motor
Vehicles) within the same incident.
(Number of Recovered Motor Vehicles) Must be numeric entry with
Data Element 19 zero left-fill. Refer to individual data element for specific formatting 302
instructions.
(Number of Recovered Motor Vehicles) was entered. However,
Data Element 14 (Type Property Loss/Etc.) 5 = Recovered was not
entered, and/or Data Element 6 (UCR Offense Code) of
240 = Motor Vehicle Theft was not entered, and/or Data Element 7
(Offense Attempted/Completed) was A = Attempted. The exception
to this rule is when recovered property is reported for a pre-NIBRS
Data Element 19 360
incident. In this case, Segment Level 3 (Property Segment) will
contain I = Incident Report, but the data value in Data Element 2
(Incident Number) will not match an incident already on file in the
national UCR database. The segment will be processed, but used
only for SRS purposes and will not be included in the agency’s
NIBRS figures.
(Number of Recovered Motor Vehicles) must be entered when Data
Element 6 (UCR Offense Code) is 240 = Motor Vehicle Theft, Data
Data Element 19 Element 7 (Offense Attempted/Completed) is C = Completed, Data 361
Element 14 (Type Property Loss/Etc.) is 5 = Recovered, and
vehicle codes were recovered.
(Number of Recovered Motor Vehicles) More than one vehicle code
was entered in Data Element 15 (Property Description), but the
number recovered in Data Element 19 (Number of Recovered
Motor Vehicles) was less than this number. For example, if vehicle
Data Element 19 codes of 03 = Automobiles and 05 = Buses were entered as being 389
recovered, then the number recovered must be at least 2, unless
the number recovered was 00 = Unknown.
The exception to this rule is when 00 = Unknown is entered in Data
Element 19.
Data Values: 01-99
00 = Unknown
Data Element 20-Suspected Drug Type
Suspected Drug Type is used to identify the types of drugs or narcotics that were seized in a drug
case.
6/30/2023 2023.0 NIBRS Technical Specification 83
This data element should not be used when drugs or narcotics were burned, stolen, etc., in
connection with offenses other than 35A = Drug/Narcotic Violations such as 200 = Arson, 220 =
Burglary/Breaking & Entering, or 23 (A-H) = Larceny/Theft Offenses.
When a substance is sent to a laboratory for analysis, and a response has not yet been received,
then data value U = Unknown Drug Type must be entered. The drug type would then be updated
when the laboratory results are received.
Note: When more than three types of drugs are involved, the two most important drugs (as
determined by the reporting agency based on the quantity, value, and deadliness of the
drugs/narcotics) should be reported in Drug Type 1 and Drug Type 2; X = Over 3 Drug Types
should be entered in Drug Type 3.
Group: A
Format: 1-Character Alphabetic
Position: 233 Drug Type 1
248 Drug Type 2
263 Drug Type 3
Occurrence: 3 times per Property Segment
Mandatory: Conditional
This data element is mandatory when one of the following conditions exist:
1) One of the offenses entered in Data Element 6 (UCR Offense Code) is 35A =
Drug/Narcotic Violations, Data Element 14 (Type Property Loss/Etc.) is 6 = Seized, and
Data Element 15 (Property Description) is 10 = Drugs/Narcotics.
2) One of the offenses entered in Data Element 6 (UCR Offense Code) is 35A =
Drug/Narcotic Violations and Data Element 14 (Type Property Loss/Etc.) is 1 = None.
Exceptions:
• Exception-The incident consists of multiple offense segments where at least one offense
code is not 35A.
Edits:
Table 3-33 Suspected Drug Type Edit Description
Suspected Drug Type Element Edits
Associated
Data Element Edit Description
Error Code
The referenced data element in an incident must contain data when
the referenced data element is mandatory or when the conditions
Data Element 20 301
are met for data that must be entered into a conditionally mandatory
field.
(Suspected Drug Type) The referenced data element must contain
Data Element 20 a valid data value when it is entered; blank is permissible on 304
nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 84
Suspected Drug Type Element Edits
Associated
Data Element Edit Description
Error Code
(Suspected Drug Type) The referenced data element in error is one
that contains multiple data values. When more than one code is
entered, none can be duplicate codes.
There are two exceptions to this rule:
1) When a data value is entered in both Drug Type 1 and Drug
Data Element 20 Type 2, but different measurement categories are entered in 306
Data Element 22 (Type Drug Measurement); this is allowed.
Refer to Data Element 22, Data Values, for the measurement
categories.
2) When the data value is U = Unknown; it can be entered only
once.
(Suspected Drug Type) Since X = Over 3 Drug Types was entered
Data Element 20 in Data Element 20 (Suspected Drug Type), two other codes must 362
also be entered. Less than three codes are present.
(Estimated Drug Quantity) Since Data Element 20 (Suspected Drug
Data Element 20 Type) contains X = Over 3 Drug Types, Data Element 21 363
(Estimated Quantity) and 22 (Type Measurement) must be blank.
(Estimated Drug Quantity) When Data Element 6 (UCR Offense
Code) is 35A = Drug/Narcotic Violations, Data Element 14 (Type
Property Loss/Etc.) is 6 = Seized, Data Element 15 (Property
Description) is 10 = Drugs, and Data Element 20 (Suspected Drug
Data Element 20 364
Type) is entered, both Data Element 21 (Estimated Drug Quantity)
and Data Element 22 (Type Drug Measurement) must also be
entered, unless Data Element 20 (Suspected Drug Type) contains
X = Over 3 Drug Types.
Data Element 20 (Suspected Drug Type) was entered, but one or
more required data elements were not entered. Data Element 6
(UCR Offense Code) must be 35A = Drug/Narcotic Violations, Data
Data Element 20 365
Element 14 (Type Property Loss/Etc.) must be 6 = Seized, or
1 = None and if seized Data Element 15 (Property Description)
must be 10 = Drugs/Narcotics.
(Suspected Drug Type) An offense of 35A = Drug/Narcotic
Violations and Data Element 14 (Type Property Loss/Etc.) with
1 = None were entered but Data Element 20 (Suspected Drug
Type) was not submitted. Since a drug seizure did not occur, the
Data Element 20 suspected drug type must also be entered. 392
Exception - The incident consists of multiple offense
segments where at least one offense code is not
35A = Drug/Narcotic Violations.
Data Values:
A = Crack Cocaine
B = Cocaine (all forms except Crack)
C = Hashish
D = Heroin
E = Marijuana
6/30/2023 2023.0 NIBRS Technical Specification 85
F = Morphine
G = Opium
H = Other Narcotics: Codeine; Demerol; Dihydromorphinone or Dilaudid; Hydrocodone or
Percodan; Methadone; Pentazocine; Propoxyphene or Darvon; etc.
I = LSD
J = PCP
K = Other Hallucinogens: BMDA or White Acid; DMT; MDA; MDMA; Mescaline or Peyote;
Psilocybin; STP; Spice; Dronabinol or Marinol; etc.
L = Amphetamines/Methamphetamines (includes Methcathinone)
M = Other Stimulants: Adipex, Fastine, and Ionamin (Derivatives of Phentermine); Benzedrine;
Didrex; Khat; Bath Salts; Methylphenidate or Ritalin; Phenmetrazine or Preludin; Tenuate;
etc.
N = Barbiturates
O = Other Depressants: Glutethimide or Doriden, Methaqualone or Quaalude, or Talwin; etc.
P = Other Drugs: Antidepressants (Elavil, Triavil, Tofranil, etc.); Aromatic Hydrocarbons;
Tranquilizers (Chlordiazepoxide or Librium, Diazepam or Valium, etc.); Steroids; etc.
U = Unknown Type Drug
X = Over 3 Drug Types
Data Element 21-Estimated Drug Quantity
Estimated Drug Quantity is used to indicate the quantity of drugs or narcotics seized in a drug
case.
This data element should not be used when drugs or narcotics were burned, stolen, etc., in
connection with offenses other than 35A = Drug/Narcotic Violations such as 200 = Arson, 220 =
Burglary/Breaking & Entering, or 23 (A-H) = Larceny/Theft Offenses.
When a substance is sent to a laboratory for analysis, and a response has not yet been received,
then data value 1 = None, i.e., 000000001000, must be entered. This quantity would then be
updated with the true quantity when the laboratory results are received.
Note: When more than three types of drugs are involved, the quantity of the two most important
drugs (as determined by the reporting agency based on the quantity, value, and deadliness of the
drugs/narcotics) should be reported in Quantity 1 and Quantity 2; Quantity 3 should be left
blank.
Group: A
Format: 12-Character Numeric
Position: 234–245 Quantity 1
249–260 Quantity 2
264–275 Quantity 3
Occurrence: Once per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is 35A =
Drug/Narcotic Violations, Data Element 14 (Type Property Loss/Etc.) is 6 = Seized, and Data
Element 15 (Property Description) Is 10 = Drugs/Narcotics.
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 86
Table 3-34 Estimated Drug Quantity Edit Description
Estimated Drug Quantity Type Element Edits
Associated
Data Element Edit Description
Error Code
(Estimated Drug Quantity) Must be numeric entry with zero left-fill.
Data Element 21 Refer to individual data element for specific formatting 302
instructions.
(Estimated Drug Quantity) Since Data Element 20 (Suspected
Data Element 21 Drug Type) contains X = Over 3 Drug Types, Data Element 21 363
(Estimated Quantity) and 22 (Type Measurement) must be blank.
(Estimated Drug Quantity) When Data Element 6 (UCR Offense
Code) is 35A = Drug/Narcotic Violations, Data Element 14 (Type
Property Loss/Etc.) is 6 = Seized, Data Element 15 (Property
Description) is 10 = Drugs, and Data Element 20 (Suspected Drug
Data Element 21 364
Type) is entered, both Data Element 21 (Estimated Drug Quantity)
and Data Element 22 (Type Drug Measurement) must also be
entered, unless Data Element 20 (Suspected Drug Type) contains
X = Over 3 Drug Types
Data Element 21 (Estimated Quantity) was entered, but 20
Data Element 21 (Suspected Drug Type) and/or 22 (Type Measurement) were not 366
entered; both must be entered.
(Estimated Drug Quantity) Data Element 21 must be
000000001000 = None (i.e., 1) when Data Element 22 (Type Drug
Measurement) is XX = Not Reported indicating the drugs were
Data Element 21 384
sent to a laboratory for analysis. When the LEA receives the drug
analysis, it should update Data Element 21 and Data Element 22
with the correct data.
Data Values: 000000000000-999999999999
000000001000 = None
Note: The first nine characters of the data value represent the quantity in whole units and the
remaining three characters designate the fractional unit expressed in thousandths with no
decimals, i.e., 1/2 ounce would be entered as 000000000500 and 1/4 gram would be entered as
000000000250. When the quantity is in whole units (no fractional unit in the last three
characters), the last three characters must be 000 (blanks are acceptable). When the quantity is a
fraction (no whole units in the first nine characters), the first nine characters must be 000000000
(blanks are acceptable).
Data Element 22-Type Drug Measurement
Type Drug Measurement is used to indicate the type of measurement used in quantifying drugs
or narcotics seized in a drug case.
This data element should not be used when drugs or narcotics were burned, stolen, etc., in
connection with offenses other than 35A = Drug/Narcotic Violations such as 200 = Arson, 220 =
Burglary/Breaking & Entering, or 23 (A-H) = Larceny/Theft Offenses.
When a substance is sent to a laboratory for analysis, and a response has not yet been received,
then data value XX = Not Reported must be entered. The measurement type would then be
updated when the laboratory results are received.
6/30/2023 2023.0 NIBRS Technical Specification 87
Note: When more than three types of drugs are involved, the type of measurement for the two
most important drugs (as determined by the reporting agency based on the quantity, value, and
deadliness of the drugs/narcotics) should be reported in Measurement Type 1 and Measurement
Type 2; Measurement Type 3 should be left blank.
Group: A
Format: 2-Character Alphabetic
Position: 246–247 Measurement Type 1
261–262 Measurement Type 2
276–277 Measurement Type 3
Occurrence: Once per Property Segment
Mandatory: Conditional
This data element is mandatory when Data Element 6 (UCR Offense Code) is 35A =
Drug/Narcotic Violations, Data Element 14 (Type Property Loss/Etc.) is 6 = Seized, and Data
Element 15 (Property Description) Is 10 = Drugs/Narcotics.
Edits:
Table 3-35 Type Drug Measurement Edit Description
Drug Type Measurement Element Edits
Associated
Data Element Edit Description
Error Code
(Type Drug Measurement) The referenced data element must
Data Element 22 contain a valid data value when it is entered; blank is permissible on 304
nonmandatory fields.
(Type Drug Measurement) Since Data Element 20 (Suspected Drug
Data Element 22 Type) contains X = Over 3 Drug Types, Data Element 21 (Estimated 363
Quantity) and 22 (Type Measurement) must be blank.
(Type Drug Measurement) When Data Element 6 (UCR Offense
Code) is 35A = Drug/Narcotic Violations, Data Element 14 (Type
Property Loss/Etc.) is 6 = Seized, Data Element 15 (Property
Description) is 10 = Drugs, and Data Element 20 (Suspected Drug
Data Element 22 364
Type) is entered, both Data Element 21 (Estimated Drug Quantity)
and Data Element 22 (Type Drug Measurement) must also be
entered, unless Data Element 20 (Suspected Drug Type) contains
X = Over 3 Drug Types.
(Type Measurement) Data Element 22 was entered with
NP = Number of Plants in combination with an illogical drug type.
Based upon the various ways a drug can be measured, very few
edits can be done to check for illogical combinations of drug type
and measurement. The only restriction will be to limit NP = Number
of Plants to the following drugs:
Data Element 22 DRUG MEASUREMENT 367
E = Marijuana NP
G = Opium NP
K = Other Hallucinogens NP
All other Data Element 22 (Type Measurement) codes are
applicable to any Data Element 20 (Suspected Drug Type) code.
6/30/2023 2023.0 NIBRS Technical Specification 88
Drug Type Measurement Element Edits
Associated
Data Element Edit Description
Error Code
Data Element 22 (Type Drug Measurement) was entered, but Data
Data Element 22 Elements 20 (Suspected Drug Type) and/or 21 (Estimated Quantity) 368
were not entered; both must be entered.
(Estimated Drug Quantity) Data Element 21 (Estimated Drug
Quantity) must be 000000001000 = None (i.e., 1) when Data
Element 22 (Type Drug Measurement) is XX = Not Reported
Data Element 22 384
indicating the drugs were sent to a laboratory for analysis. When the
LEA receives the drug analysis it should update Data Elements 21
and 22 with the correct data values.
Data Values: Weights
GM = Gram
KG = Kilogram
LB = Pound
OZ = Ounce
Capacity
FO = Fluid Ounce
GL = Gallon
LT = Liter
ML = Milliliter
Units
DU = Dosage Units/Items
NP = Number of Plants
Not Reported
XX = Not Reported
3.3.5 Victim Segment
The Victim Segment is used to describe the victims involved in the incident (e.g., their age, sex,
race, and ethnicity). A separate Victim Segment should be submitted for each victim (up to 999)
involved in the incident and there must be at least one Victim Segment submitted for each
incident.
Note: In addition to the data elements specified, the Victim Segment also contains the Header
Data Elements identified in Section 3.3.1, as well as Data Element 1 (ORI) and Data Element 2
(Incident Number) included in the Administrative Segment, Section 3.3.2.Data Element 23-
Victim Sequence Number.
Data Element 23-Victim Sequence Number
Victim Sequence Number is used to assign a sequence number to each victim in an incident. A
separate Victim Segment must be submitted for each numbered victim.
Group: A
Format: 3-Character Numeric
6/30/2023 2023.0 NIBRS Technical Specification 89
Position: 38–40
Occurrence: Once per Victim Segment
Mandatory: Yes
Edits:
Table 3-36 Victim Sequence Number Edit Description
Victim Sequence Number Element Edits
Associated
Data Element Edit Description
Error Code
(Victim Sequence Number) The referenced data element in an
Incident must contain data when the referenced data element is
Data Element 23 401
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
Data Element 23 Must contain numeric entry with zero left-fill. 402
(Victim Sequence Number) The referenced data element must
Data Element 23 contain a valid data value when it is entered; blank is 404
permissible on nonmandatory fields.
(Victim Segment) When a Group A Incident Report is submitted,
the individual segments comprising the incident cannot contain
Data Element 23 duplicates. In this case, two victim segments were submitted 451
having the same entry in Data Element 23 (Victim Sequence
Number).
Data Values: 001-999
Data Element 24-Victim Connected to UCR Offense Code
Victim Connected to UCR Offense Code is used to link each victim to up to ten of the most
serious Group A offenses (as determined by the reporting agency) of which they were a victim.
Note: When an offense did not affect a specific victim, do not enter the offense in connection
with that victim. Every offense must have a victim or victims, but not every victim was affected
by each offense within an incident.
Group: A
Format: 3-Character Alphanumeric
Position: 41–43 Offense 1
44–46 Offense 2
47–49 Offense 3
50–52 Offense 4
53–55 Offense 5
56–58 Offense 6
59–61 Offense 7
62–64 Offense 8
65–67 Offense 9
68–70 Offense 10
Occurrence: 10 per Victim Segment
Mandatory: Yes
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 90
Table 3-37 Victim Connected to UCR Offense Code Edit Description
Victim Connected to UCR Code(s) Element Edits
Associated
Data Element Edit Description
Error Code
(Victim Connected to UCR Offense Code) The referenced data
element in an incident must contain data when the referenced
Data Element 24 401
data element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
(Victim Connected to UCR Offense Code) The referenced data
Data Element 24 element must contain a valid data value when it is entered; blank 404
is permissible on nonmandatory fields.
(Victim Connected to UCR Offense Code) The referenced data
Data Element 24 element in error is one that contains multiple data values. When 406
more than one code is entered, none can be duplicate codes.
(Victim Connected to UCR Offense Code) Each UCR Offense
Code entered into Data Element 24 (Victim Connected to UCR
Offense Code) must have the Offense Segment for the value. In
Data Element 24 466
this case, the victim was connected to offenses that were not
submitted as Offense Segments. A victim cannot be connected to
an offense when the offense itself is not present.
6/30/2023 2023.0 NIBRS Technical Specification 91
Victim Connected to UCR Code(s) Element Edits
Associated
Data Element Edit Description
Error Code
Mutually Exclusive offenses are ones that cannot occur to the
same victim by UCR definitions. A Lesser Included offense is one
that is an element of another offense and should not be reported
as having happened to the victim along with the other offense.
Lesser Included and Mutually Exclusive offenses are defined as
follows:
1) Murder – Aggravated Assault, Simple Assault, and
Intimidation are all Lesser Included offenses of Murder.
Negligent Manslaughter is Mutually Exclusive.
2) Aggravated Assault – Simple Assault and Intimidation are
Lesser Included. Note: Aggravated Assault is a Lesser
Included offense of Murder, Rape, Sodomy, Sexual Assault
With An Object, and Robbery.
3) Simple Assault – Intimidation is a Lesser Included offense of
Simple Assault. Note: Simple Assault is a Lesser Included
offense of Murder, Aggravated Assault, Rape, Sodomy,
Sexual Assault With An Object, Fondling, and Robbery.
4) Intimidation – Intimidation is a Lesser Included offense of
Murder, Aggravated Assault, Rape, Sodomy, Sexual Assault
With An Object, Fondling, and Robbery.
5) Negligent Manslaughter – Murder, Aggravated Assault,
Data Element 24 478
Simple Assault, and Intimidation are Mutually Exclusive
offenses. Negligent Manslaughter is defined as the killing of
another person through negligence, while assault offenses
are characterized by unlawful attack(s).
6) Rape – Aggravated Assault, Simple Assault, Intimidation, and
Fondling are Lesser Included offenses of Rape. Incest and
Statutory Rape are Mutually Exclusive offenses and cannot
occur with Rape. The prior two offenses involve consent,
while the latter involves action against the victim’s will.
7) Sodomy – Aggravated Assault, Simple Assault, Intimidation,
and Fondling are Lesser Included offenses of Sodomy. Incest
and Statutory Rape are Mutually Exclusive offenses and
cannot occur with Sodomy. The prior two offenses involve
consent, while the latter involves action against the victim’s
will.
8) Sexual Assault With An Object – Aggravated Assault, Simple
Assault, Intimidation, and Fondling are Lesser Included
offenses of Sexual Assault with an Object. Incest and
Statutory Rape are Mutually Exclusive offenses and cannot
occur with Sexual Assault With An Object. The prior two
offenses involve consent, while the latter involves action
against the victim’s will.
6/30/2023 2023.0 NIBRS Technical Specification 92
Victim Connected to UCR Code(s) Element Edits
Associated
Data Element Edit Description
Error Code
9) Fondling – Simple Assault and Intimidation are Lesser
Included offenses of Fondling. Incest and Statutory Rape are
Mutually Exclusive offenses and cannot occur with Fondling.
The prior two offenses involve consent, while the latter
involves forced action against the victim’s will. Note: Fondling
is a Lesser Included offense of Rape, Sodomy, and Sexual
Assault With An Object.
10) Incest – Rape, Sodomy, Sexual Assault with an Object, and
Fondling are Mutually Exclusive offenses. Incest involves
Data Element 24 consent, while the prior offenses involve sexual relations 478
against the victim’s will.
11) Statutory Rape – Rape, Sodomy, Sexual Assault With An
Object, and Fondling are Mutually Exclusive offenses.
Statutory Rape involves consent, while the prior offenses
involve sexual relations against the victim’s will.
12) Robbery – Aggravated Assault, Simple Assault, Intimidation,
and all Theft offenses (including Motor Vehicle Theft) are
Lesser Included offenses of Robbery.
Data Values: Refer to 6.10Appendix A: Offense Codes
Mutually Exclusive and Lesser Included offenses:
09A = Murder & Nonnegligent Manslaughter
• Mutually Exclusive: 09B = Negligent Manslaughter
• Lesser Included: 13A = Aggravated Assault, 13B = Simple Assault, and 13C =
Intimidation
09B = Negligent Manslaughter
• Mutually Exclusive: 09A = Murder & Nonnegligent Manslaughter, 13A = Aggravated
Assault, 13B = Simple Assault, and 13C = Intimidation
11A = Rape
• Mutually Exclusive: 36A = Incest and 36B = Statutory Rape
Lesser Included: 13A = Aggravated Assault, 13B = Simple Assault, 13C = Intimidation,
and 11D = Fondling
11B = Sodomy:
• Mutually Exclusive: 36A = Incest and 36B = Statutory Rape
• Lesser Included: 13A = Aggravated Assault, 13B = Simple Assault, 13C = Intimidation,
and 11D = Fondling
11C = Sexual Assault With An Object
• Mutually Exclusive: 36A = Incest and 36B = Statutory Rape
• Lesser Included: 13A = Aggravated Assault, 13B = Simple Assault, 13C = Intimidation,
and 11D = Fondling
11D = Fondling
• Mutually Exclusive: 36A = Incest and 36B = Statutory Rape
• Lesser Included: 13B = Simple Assault and 13C = Intimidation
6/30/2023 2023.0 NIBRS Technical Specification 93
Note: Fondling is a lesser included offense of rape, sodomy, and sexual assault with an
object.
120 = Robbery
• Lesser Included: 13A = Aggravated Assault, 13B = Simple Assault, 13C = Intimidation,
23A – 23H = Larceny/Theft Offenses, and 240 = Motor Vehicle Theft
13A = Aggravated Assault
• Lesser Included: 13B = Simple Assault and 13C = Intimidation
Note: Aggravated assault is a lesser included offense of murder, rape, sodomy, sexual
assault with an object, and robbery.
13B = Simple Assault
• Lesser Included: 13C = Intimidation
Note: Simple assault is a lesser included offense of murder, aggravated assault, rape,
sodomy, sexual assault with an object, fondling, and robbery.
36A = Incest
• Mutually Exclusive: 11A = Rape, 11B = Sodomy, 11C = Sexual Assault With An Object,
and 11D = Fondling
36B = Statutory Rape
• Mutually Exclusive: 11A = Rape, 11B = Sodomy, 11C = Sexual Assault With An Object,
and 11D = Fondling
Data Element 25-Type of Victim
Type of Victim is used to categorize the victim associated with the incident.
Group: A
Format: 1-Character Alphabetic
Position: 71
Occurrence: Once per Victim Segment
Mandatory: Yes
Edits:
Table 3-38 Type of Victim Edit Description
Type of Victim Element Edits
Associated
Data Element Edit Description
Error Code
The Group A Incident Report submission contains only offense(s)
that are Crimes Against Society. When this is so, Data Element 25
(Type of Victim) must be S = Society/Public, and only one victim
may be submitted.
Exception - Type of Victim must be G = Government for offenses:
26H = Money Laundering*
521 = National Firearm Act 1934*
Data Element 25 522 = Weapons of Mass Destruction* 080
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification 94
Type of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Type of Victim) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
Data Element 25 401
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Type of Victim) The referenced data element must contain a valid
Data Element 25 data value when it is entered; blank is permissible on nonmandatory 404
fields.
(Type of Victim) Must have a value of G = Government when Data
Element 24 (Victim Connected to UCR Offense Code) contains one
of the following:
26H = Money Laundering*
521 = National Firearm Act 1934*
522 = Weapons of Mass Destruction*
Data Element 25 526 = Explosives* 461
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA reporting only
(Type of Victim) Must have a value of I = Individual or L = Law
Data Element 25 Enforcement Officer when Data Element 24 (Victim Connected to 464
UCR Offense Code) contains a Crime Against Person.
(Type of Victim) Must have a value of S = Society/Public when Data
Element 24 (Victim Connected to UCR Offense Code) contains a
Crime Against Society.
Exception - Type of Victim must be G = Government for offenses
26H = Money Laundering*
521 = National Firearm Act 1934*
Data Element 25 522 = Weapons of Mass Destruction* 465
526 = Explosives*
58A = Import Violations
58B = Export Violations
61A = Federal Liquor Offenses
61B = Federal Tobacco Offenses
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA reporting only
(Type of Victim) Cannot have a value of S = Society/Public when
Data Element 25 Data Element 24 (Victim Connected to UCR Offense Code) contains 467
a Crime Against Property.
(Type of Victim) cannot be L = Law Enforcement Officer unless Data
Element 24 (Victim Connected to UCR Offense Code) is one of the
following:
Data Element 25 09A = Murder & Nonnegligent Manslaughter 482
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
6/30/2023 2023.0 NIBRS Technical Specification 95
Type of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Type of Victim) when Type of Victim is L = Law Enforcement Officer
and Data Element 24 (Victim Connected to UCR Offense Code) is
one of the following:
09A = Murder & Nonnegligent Manslaughter
Data Element 25 13A = Aggravated Assault 490
13B = Simple Assault
13C = Intimidation
Data Element 3 (Incident Date/Hour) must be populated with a valid
hour (00-23) and cannot be blank.
Data Values: B = Business
F = Financial Institution
G = Government
I = Individual
L = Law Enforcement Officer
O = Other
R = Religious Organization
S = Society/Public
U = Unknown
Data Element 25A-Type of Officer Activity/Circumstance
Type of Officer Activity/Circumstance is used to indicate the type of activity in which the law
enforcement officer was engaged at the time the officer was killed or assaulted in the line of
duty.
Group: A
Format: 2-Character Numeric
Position: 130–131
Occurrence: Once per Victim Segment
Mandatory: Optional
Edits:
Table 3-39 Type of Officer Activity/Circumstance Edit Description
Type of Officer Activity/Circumstance Element Edits
Associated
Data Element Edit Description
Error Code
(Type of Officer Activity/Circumstance) The referenced data
Data Element 25A element must contain a valid data value when it is entered; blank is 404
permissible on nonmandatory fields.
(Type of Officer Activity/Circumstance), Data Element 25B (Officer
Assignment Type), Data Element 26 (Age of Victim), Data Element
Data Element 25A 27 (Sex of Victim), and Data Element 28 (Race of Victim) must be 454
entered when Data Element 25 (Type of Victim) is L = Law
Enforcement Officer.
(Type of Officer Activity/Circumstance) Data Element 25B (Officer
Data Element 25A 483
Assignment Type), Data Element 25C (Officer–ORI Other
6/30/2023 2023.0 NIBRS Technical Specification 96
Type of Officer Activity/Circumstance Element Edits
Associated
Data Element Edit Description
Error Code
Jurisdiction), may only be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
Data Values: 01 = Responding to Disturbance Call
(Family Quarrels, Person with Firearm, Etc.)
02 = Burglaries in Progress or Pursuing Burglary Suspects
03 = Robberies in Progress or Pursuing Robbery Suspects
04 = Attempting Other Arrests
05 = Civil Disorder (Riot, Mass Disobedience)
06 = Handling, Transporting, Custody of Prisoners
07 = Investigating Suspicious Persons or Circumstances
08 = Ambush–No Warning
09 = Handling Persons with Mental Illness
10 = Traffic Pursuits and Stops
11 = All Other
Data Element 25B-Officer Assignment Type
Officer Assignment Type is used to report the victim officer’s type of assignment when the
LEOKA offense occurred.
Group: A
Format: 1-Character Alphabetic
Position: 132
Occurrence: Once per Victim Segment
Mandatory: Optional
Edits:
Table 3-40 Officer Assignment Type Edit Description
Officer Assignment Type Element Edits
Associated
Data Element Edit Description
Error Code
(Officer Assignment Type) The referenced data element must
Data Element 25B contain a valid data value when it is entered; blank is permissible 404
on nonmandatory fields.
Data Element 25A (Type of Officer Activity/Circumstance), Data
Element 25B (Officer Assignment Type), Data Element 26 (Age
Data Element 25B of Victim), Data Element 27 (Sex of Victim), and Data Element 28 454
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
Data Element 25A (Type of Officer Activity/Circumstance), Data
Element 25B (Officer Assignment Type), Data Element 25C
Data Element 25B 483
(Officer–ORI Other Jurisdiction), may only be entered when Data
Element 25 (Type of Victim) is L = Law Enforcement Officer.
Data Values: For Uniformed Law Enforcement Officers:
F = Two-Officer Vehicle
6/30/2023 2023.0 NIBRS Technical Specification 97
G = One-Officer Vehicle (Alone)
H = One-Officer Vehicle (Assisted)
For Non-Uniformed Officers:
I = Detective or Special Assignment (Alone)
J = Detective or Special Assignment (Assisted)
For Law Enforcement Officers Serving in Other Capacities (Foot patrol, Off duty,
etc.):
K = Other (Alone)
L = Other (Assisted)
Note: The term “assisted” refers only to law enforcement assistance.
Data Element 25C-Officer-ORI Other Jurisdiction
(Officer–ORI Other Jurisdiction) is used to report the ORI of the law enforcement officer’s
agency when an officer from another jurisdiction is killed or assaulted in the line of duty in the
reporting agency’s jurisdiction. No entry is required in this data element when an officer is killed
or assaulted in his/her own jurisdiction.
Group: A
Format: 9-Character Alphanumeric
Position: 133–141
Occurrence: Once per Victim Segment
Mandatory: Optional
Edits:
Table 3-41 Jurisdiction Edit Description
Officer ORI Jurisdiction Element Edits
Associated
Data Element Edit Description
Error Code
(Officer–ORI Other Jurisdiction) Must be a valid nine-character
Data Element 25C 952
NCIC ORI.
(Officer–ORI Other Jurisdiction) Data Element 25A (Type of
Officer Activity/Circumstance), Data Element 25B (Officer
Data Element 25C Assignment Type), Data Element 25C (Officer–ORI Other 483
Jurisdiction), may only be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
Data Values: A–Z (Capital letters only)
0–9
Data Element 26-Age of Victim
Age of Victim is used to indicate the age of an individual victim when the reported crime
occurred. The data value for Age of Victim can be an exact age, a range of years, or unknown.
For an exact age, use only record positions 72 and 73 (leave positions 74 and 75 blank). To enter
an age range, enter the beginning age in the range in positions 72 and 73 and the ending age in
the range in positions 74 and 75.
6/30/2023 2023.0 NIBRS Technical Specification 98
When Age of Victim is populated with an age range (i.e., 16 through 19), then the system will
store the average age, decimal value truncated. For example, when the age range is 16 through
19, the average is 17.5 years old and is stored as 17 years.
Group: A
Format: 4-Character Alphanumeric
Position: 72–75
Occurrence: Once per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 25 (Type of Victim) is I = Individual or L =
Law Enforcement Officer.
Edits:
Table 3-42 Age of Victim Edit Description
Age of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Age of Victim) The referenced data element must contain a valid
Data Element 26 data value when it is entered; blank is permissible on nonmandatory 404
fields.
(Age of Victim) contains data, but is not left-justified. A single two-
Data Element 26 408
character age must be in positions 1 and 2 of the field.
(Age of Victim) contains more than two characters indicating a
Data Element 26 possible age-range was being attempted. If so, the field must 409
contain numeric entry of four digits.
(Age of Victim) was entered as an age-range. Accordingly, the first
Data Element 26 410
age component must be less than the second age.
(Age of Victim) was entered as an age-range. Therefore, the first
Data Element 26 422
age component cannot be 00 = Unknown.
(Age of Victim) cannot be less than 13 years old when Data Element
Data Element 26 35 (Relationship of Victim to Offender) contains a relationship of 450
SE = Spouse.
(Age of Victim) must be 17 or greater and less than or equal to 98 or
00 = Unknown, when Data Element 25 (Type of Victim) is L = Law
Data Element 26 452
Enforcement Officer. (Data Element 26 must be >=17 & <=98 or
Data Element 26 = 00)
(Age of Victim) The data element associated with this error must be
Data Element 26 453
present when Data Element 25 (Type of Victim) is I = Individual.
Data Element 25A (Type of Officer Activity/Circumstance), Data
Element 25B (Officer Assignment Type), Data Element 26 (Age of
Data Element 26 Victim), Data Element 27 (Sex of Victim), and Data Element 28 454
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
The Data Element associated with this error cannot be entered
Data Element 26 when Data Element 25 (Type of Victim) is not I = Individual or 458
L = Law Enforcement Officer.
Data Element 26 (Age of Victim) should be under 18 when Data
Data Element 26 Element 24 (Victim Connected to UCR Offense Code) is 481
36B = Statutory Rape.
6/30/2023 2023.0 NIBRS Technical Specification 99
Data Values: NN = Under 24 Hours
NB = 1–6 Days Old
BB = 7–364 Days Old
01–98 = Years Old
99 = Over 98 Years Old
00 = Unknown
Note: Any combination of years is valid for an age range. The younger age must be listed first in
the range. For example, “2530” is a valid age range.
Data Element 27-Sex of Victim
Sex of Victim is used to indicate the sex of an individual victim.
Group: A
Format: 1-Character Alphabetic
Position: 76
Occurrence: Once per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 25 (Type of Victim) is I = Individual or
L = Law Enforcement Officer.
Edits:
Table 3-43 Sex of Victim Edit Description
Sex of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Sex of Victim) The referenced data element must contain a valid
Data Element 27 data value when it is entered; blank is permissible on nonmandatory 404
fields.
(Sex of Victim) The data element associated with this error must be
Data Element 27 453
present when Data Element 25 (Type of Victim) is I = Individual.
(Sex of Victim) Data Element 25A (Type of Officer
Activity/Circumstance), Data Element 25B (Officer Assignment
Type), Data Element 26 (Age of Victim), Data Element 27 (Sex of
Data Element 27 454
Victim), and Data Element 28 (Race of Victim) must be entered
when Data Element 25 (Type of Victim) is L = Law Enforcement
Officer.
(Sex of Victim) The data element associated with this error cannot
Data Element 27 be entered when Data Element 25 (Type of Victim) is not 458
I = Individual or L = Law Enforcement Officer.
(Sex of Victim) Data Element 27 (Sex of Victim) must be M = Male
Data Element 27 or F = Female to be connected to offense codes of 11A = Rape and 469
36B = Statutory Rape.
Data Values: F = Female
M = Male
U = Unknown
6/30/2023 2023.0 NIBRS Technical Specification 100
Data Element 28-Race of Victim
Race of Victim is used to indicate the race of an individual victim.
Group: A
Format: 1-Character Alphabetic
Position: 77
Occurrence: Once per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 25 (Type of Victim) is I = Individual or L =
Law Enforcement Officer.
Edits:
Table 3-44 Race of Victim Edit Description
Race of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Race of Victim) The referenced data element must contain a valid
Data Element 28 data value when it is entered; blank is permissible on nonmandatory 404
fields.
(Race of Victim) The data element associated with this error must be
Data Element 28 453
present when Data Element 25 (Type of Victim) is I = Individual.
Data Element 25A (Type of Officer Activity/Circumstance), Data
Element 25B (Officer Assignment Type), Data Element 26 (Age of
Data Element 28 Victim), Data Element 27 (Sex of Victim), and Data Element 28 454
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
(Race of Victim) The data element associated with this error cannot
Data Element 28 be entered when Data Element 25 (Type of Victim) is not I = 458
Individual or L = Law Enforcement Officer.
Data Values: W = White
B = Black or African American
I = American Indian or Alaska Native
A = Asian
P = Native Hawaiian or Other Pacific Islander
U = Unknown
Data Element 29-Ethnicity of Victim
Ethnicity of Victim is used to indicate the ethnicity of an individual victim when Data Element
25 (Type of Victim) is I = Individual or L = Law Enforcement Officer.
This is an optional data element. The victim’s ethnicity is reported at the discretion of the
reporting agency.
Group: A
Format: 1-Character Alphabetic
Position: 78
Occurrence: Once per Victim Segment
Mandatory: Optional
6/30/2023 2023.0 NIBRS Technical Specification 101
Edits:
Table 3-45 Ethnicity of Victim Edit Description
Ethnicity of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Ethnicity of Victim) The referenced data element must contain a
Data Element 29 valid data value when it is entered; blank is permissible on 404
nonmandatory fields.
(Ethnicity of Victim) The data element associated with this error
Data Element 29 cannot be entered when Data Element 25 (Type of Victim) is not 458
I = Individual or L = Law Enforcement Officer
Data Values: H = Hispanic or Latino
N = Not Hispanic or Latino
U = Unknown
Data Element 30-Resident Status of Victim
Resident Status of Victim is used to indicate if the victim was a resident in the reporting
agency’s jurisdiction at the time of the incident.
Group: A
Format: 1-Character Alphabetic
Position: 79
Occurrence: Once per Victim Segment
Mandatory: Optional
Edits:
Table 3-46 Resident Status of Victim Edit Description
Resident Status of Victim Element Edits
Associated
Data Element Edit Description
Error Code
(Resident Status of Victim) The referenced data element must
Data Element 30 contain a valid data value when it is entered; blank is permissible 404
on nonmandatory fields.
(Resident Status of Victim) The Data Element associated with this
Data Element 30 error cannot be entered when Data Element 25 (Type of Victim) is 458
not I = Individual or L = Law Enforcement Officer.
Data Values: N = Nonresident
R = Resident
U = Unknown
Data Element 31-Aggravated Assault/Homicide Circumstances
Aggravated Assault/Homicide Circumstances is used to describe the circumstances of either an
aggravated assault or a homicide.
Group: A
Format: 2-Character Numeric
Position: 80–81 Circumstance 1
6/30/2023 2023.0 NIBRS Technical Specification 102
82–83 Circumstance 2
Occurrence: 2 times per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 24 (Victim Connected to UCR Offense
Code) is 09A = Murder and Nonnegligent Manslaughter, 09B = Negligent Manslaughter, 09C =
Justifiable Homicide, or 13A = Aggravated Assault.
Edits:
Table 3-47 Aggravated Assault/Homicide Circumstances Edit Description
Aggravated Assault/Homicide Circumstances Element Edits
Associated
Data Element Edit Description
Error Code
(Aggravated Assault/Homicide Circumstances) The referenced data
element in an incident must contain data when the referenced data
Data Element 31 401
element is mandatory or when the conditions are met for data that
must be entered into a conditionally mandatory field.
Data Element 31 Must contain numeric entry with zero left-fill. 402
(Aggravated Assault/Homicide Circumstances) The referenced data
Data Element 31 element must contain a valid data value when it is entered; blank is 404
permissible on nonmandatory fields.
(Aggravated Assault/Homicide Circumstances) The referenced data
Data Element 31 element in error is one that contains multiple data values. When 406
more than one code is entered, none can be duplicate codes.
(Aggravated Assault/Homicide Circumstances) may only be entered
when one or more of the offenses in Data Element 24 (Victim
Connected to UCR Offense Code) are:
Data Element 31 09A = Murder and Nonnegligent Manslaughter 419
09B = Negligent Manslaughter
09C = Justifiable Homicide
13A = Aggravated Assault
(Aggravated Assault/Homicide Circumstances) was entered with
two entries, but was rejected for one of the following reasons:
1) 10 = Unknown Circumstances is mutually exclusive with any
other value.
Data Element 31 2) Multiple values from more than one category were entered. 456
3) Values from the category 09B = Negligent Manslaughter are
mutually exclusive with any other value.
4) Values from the category 09C = Justifiable Homicide are
mutually exclusive with any other value.
(Aggravated Assault/Homicide Circumstances) may only have
codes of 01 through 06 and 08 through 10 when Data Element 24
Data Element 31 (Victim Connected To UCR Offense) is 13A = Aggravated Assault. 462
All other codes, including 07 = Mercy Killing, are not valid because
they do not relate to an Aggravated Assault.
(Aggravated Assault/Homicide Circumstances) When a Justifiable
Homicide is reported, Data Element 31 (Aggravated Assault/
Data Element 31 Homicide Circumstances) may only have codes of 20 = Criminal 463
Killed by Private Citizen or 21 = Criminal Killed by Police Officer. In
this case, a code other than the two mentioned was entered.
6/30/2023 2023.0 NIBRS Technical Specification 103
Aggravated Assault/Homicide Circumstances Element Edits
Associated
Data Element Edit Description
Error Code
(Aggravated Assault/Homicide Circumstances) A victim segment
was submitted with Data Element 24 (Victim Connected to UCR
Data Element 31 Offense Code) having an offense that does not have a permitted 477
code for Data Element 31 (Aggravated Assault/Homicide
Circumstances).
Data Element 31 (Aggravated Assault/Homicide Circumstances)
has 08 = Other Felony Involved but the incident has only one
offense. For this code to be used, there must be an Other Felony.
Data Element 31 480
Either multiple entries for Data Element 6 (UCR Offense Code)
should have been submitted, or multiple individual victims should
have been submitted for the incident report.
Data Values:
For: 13A = Aggravated Assault
09A = Murder and Nonnegligent Manslaughter (enter up to two)
01 = Argument
02 = Assault on Law Enforcement Officer
03 = Drug Dealing
04 = Gangland (Organized Crime Involvement)
05 = Juvenile Gang
06 = Domestic Violence
07 = Mercy Killing (Not applicable to Aggravated Assault)
08 = Other Felony Involved
09 = Other Circumstances
10 = Unknown Circumstances
For: 09B = Negligent Manslaughter (enter only one)
30 = Child Playing With Weapon
31 = Gun-Cleaning Accident
32 = Hunting Accident
33 = Other Negligent Weapon Handling
34 = Other Negligent Killing
For: 09C = Justifiable Homicide (enter only one)
20 = Criminal Killed by Private Citizen
21 = Criminal Killed by Police Officer
Data Element 32-Additional Justifiable Homicide Circumstances
Additional Justifiable Homicide Circumstances is used to describe the circumstances of a
justifiable homicide. When more than one data value applies, enter the one that is most
descriptive.
Group: A
Format: 1-Character Alphabetic
Position: 84
6/30/2023 2023.0 NIBRS Technical Specification 104
Occurrence: Once per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 24 (Victim Connected to UCR Offense
Code) is 09C = Justifiable Homicide.
Edits:
Table 3-48 Additional Justifiable Homicide Circumstances Edit Description
Additional Justifiable Homicide Circumstances Element Edits
Associated
Data Element Edit Description
Error Code
(Additional Justifiable Homicide Circumstances) The referenced
Data Element 32 data element must contain a valid data value when it is entered; 404
blank is permissible on nonmandatory fields.
Data Element 31 (Aggravated Assault/Homicide Circumstances)
contains: 20 = Criminal Killed by Private Citizen or 21 = Criminal
Data Element 32 455
Killed by Police Officer, but Data Element 32 (Additional Justifiable
Homicide Circumstances) was not entered.
(Additional Justifiable Homicide Circumstances) was entered, but
Data Element 32 Data Element 31 (Aggravated Assault/Homicide Circumstances) 457
does not reflect a justifiable homicide circumstance.
Data Values: A = Criminal Attacked Police Officer and That Officer Killed Criminal
B = Criminal Attacked Police Officer and Criminal Killed by Another Police
Officer
C = Criminal Attacked a Civilian
D = Criminal Attempted Flight from a Crime
E = Criminal Killed in Commission of a Crime
F = Criminal Resisted Arrest
G = Unable to Determine/Not Enough Information
Data Element 33-Type Injury
Type Injury is used to describe the type of bodily injury sustained by the victim.
Group: A
Format: 1-Character Alphabetic
Position: 85 Injury 1
86 Injury 2
87 Injury 3
88 Injury 4
89 Injury 5
Occurrence: 5 times per Victim Segment
Mandatory: Conditional
This data element is mandatory when Data Element 24 (Victim Connected to UCR Offense
Code) is:
• 100 = Kidnapping/Abduction
• 11A = Rape
• 11B = Sodomy
6/30/2023 2023.0 NIBRS Technical Specification 105
• 11C = Sexual Assault With An Object
• 11D = Fondling
• 120 = Robbery
• 13A = Aggravated Assault
• 13B = Simple Assault
• 210 = Extortion/Blackmail
• 64A = Human Trafficking, Commercial Sex Acts
• 64B = Human Trafficking, Involuntary Servitude
Note: For the offense of Robbery, Data Element 33 (Type Injury) is only mandatory when Data
Element 25 (Type of Victim) is I = Individual.
Edits:
Table 3-49 Type of Injury Edit Description
Type of Injury Element Edits
Associated
Data Element Edit Description
Error Code
(Type Injury) The referenced data element in an Incident must
contain data when the referenced data element is mandatory or
Data Element 33 401
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Type Injury) The referenced data element must contain a valid
Data Element 33 data value when it is entered; blank is permissible on 404
nonmandatory fields.
(Type Injury) The referenced data element in error is one that
Data Element 33 contains multiple data values. When more than one code is 406
entered, none can be duplicate codes.
(Type Injury) Can have multiple data values and was entered with
Data Element 33 multiple values. However, the entry shown between the brackets in 407
[value] above cannot be entered with any other data value.
Data Element 33 (Type Injury) may only be entered when one or
more of the offenses in Data Element 24 (Victim Connected to UCR
Offense Code) are:
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
Data Element 33 11C = Sexual Assault With An Object 419
11D = Fondling
120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
(Type Injury) The data element associated with this error cannot be
Data Element 33 entered when Data Element 25 (Type of Victim) is not 458
I = Individual or L = Law Enforcement Officer.
6/30/2023 2023.0 NIBRS Technical Specification 106
Type of Injury Element Edits
Associated
Data Element Edit Description
Error Code
(Type Injury) A Simple Assault (13B) was the only crime against
person offense committed against a victim, but the victim had
major injuries/trauma entered for Data Element 33 (Type Injury).
Data Element 33 479
Either the offense should have been classified as an 13A =
Aggravated Assault or the victim’s injury should not have been
entered as major.
Data Values: N = None
B = Apparent Broken Bones
I = Possible Internal Injury
L = Severe Laceration
M = Apparent Minor Injury
O = Other Major Injury
T = Loss of Teeth
U = Unconsciousness
Data Element 34-Offender Number to be Related
Offender Number to be Related is used to enter the Offender Sequence Number (found in Data
Element 36) of each offender to be identified in Data Element 35 (Relationship of Victim to
Offender). Enter 00 = Unknown Offender when Data Element 36 (Offender Sequence Number)
is 00 = Unknown Offender.
Group: A
Format: 2-Character Numeric
Position: 90–91 Offender Number 1
94–95 Offender Number 2
98–99 Offender Number 3
102–103 Offender Number 4
106–107 Offender Number 5
110–111 Offender Number 6
114–115 Offender Number 7
118–119 Offender Number 8
122–123 Offender Number 9
126–127 Offender Number 10
Occurrence: 10 times per Victim Segment
Mandatory: Conditional
Edits:
• This data element is mandatory when one of the offenses entered in Data Element 24
(Victim Connected to UCR Offense Code) is a Crime Against Person or a Crime Against
Property (in case of Robbery), when Data Element 25 (Type of Victim) is I = Individual
or L = Law Enforcement.
o Reporting the relationship of victim to offender for Crime Against Property
offenses is optional for victims of I = Individual, other than 120 = Robbery.
6/30/2023 2023.0 NIBRS Technical Specification 107
Table 3-50 Offender Number to be Related Edit Description
Offender Number(s) to be Related Element Edits
Associated
Data Element Edit Description
Error Code
Data Element 34 (Offender Number to be Related) has a value that
does not have a corresponding Offender Segment. For example, if
Data Element 34 the field value shown in Data Element 34 is 15, an Offender 070
Segment does not exist with a value of 15 in Data Element 36
(Offender Sequence Number).
(Offender Number to be Related) The referenced data element in an
Incident must contain data when the referenced data element is
Data Element 34 401
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
Data Element 34 Must contain numeric entry with zero left-fill. 402
(Offender Number to be Related) The referenced data element in
Data Element 34 error is one that contains multiple data values. When more than one 406
code is entered, none can be duplicate codes.
(Offender Number to be Related) The data element associated with
Data Element 34 this error cannot be entered when Data Element 25 (Type of Victim) 458
is not I = Individual or L = Law Enforcement Officer.
(Offender Number to be Related) has relationships of VO = Victim
Data Element 34 Was Offender that point to multiple offenders, which is an 471
impossible situation. A single victim cannot be two offenders.
(Offender Number to be Related) A victim may only have one
Data Element 34 spousal relationship. In this instance, the victim has a relationship of 475
SE = Spouse to two or more offenders.
(Offender Number to be Related) cannot be 00 = Unknown when
Data Element 24 (Victim Connected to UCR Offense Code) is 360 =
Data Element 34 Failure to Register as a Sex Offender*. 485
*Denotes offenses for federal and tribal LEA reporting only
Data Values: 00 = Unknown Offender
01–99
Data Element 35-Relationship of Victim to Offender
Relationship of Victim to Offender is used, along with Data Element 34 (Offender Number to be
Related), to report the relationship of the victim to the offender(s) who perpetrated a Crime
Against Person or a Crime Against Property against the victim.
When more than 10 offenders are identified in Data Element 36 (Offender Sequence Number),
enter the relationship of the 10 most closely related to the victim. For example, when one of the
offenders is the brother of the victim and the other 15 offenders were acquaintances of the
victim, enter the information for the brother and 9 of the offenders who were acquaintances.
Note: Leave this data element blank when Data Element 36 (Offender Sequence Number) is
00 = Unknown Offender.
Group: A
Format: 2-Character Alphabetic
Position: 92–93 Relationship 1
96–97 Relationship 2
6/30/2023 2023.0 NIBRS Technical Specification 108
100–101 Relationship 3
104–105 Relationship 4
108–109 Relationship 5
112–113 Relationship 6
116–117 Relationship 7
120–121 Relationship 8
124–125 Relationship 9
128–129 Relationship 10
Occurrence: 10 times per Victim Segment
Mandatory: Conditional
This data element must be relaxed to accept all other Crime Against Property offenses, other than
robbery, when Data Element 36 (Offender Sequence Number) is other than 00 = Unknown
Offender.
Edits:
Table 3-51 Relationship of Victim to Offender Edit Description
Relationship(s) of Victim to Offender(s) Element Edits
Associated
Data Element Edit Description
Error Code
(Relationship of Victim to Offender) The referenced data element
Data Element 35 must contain a valid data value when it is entered; blank is 404
permissible on nonmandatory fields.
(Relationship of Victim to Offender) Corresponding Data Element 35
(Relationship of Victim to Offender) data must be entered when
Data Element 35 460
Data Element 34 (Offender Number to be Related) is entered with a
value greater than 00.
(Relationship of Victim to Offender) cannot be entered when Data
Element 34 (Offender Number to be Related) is zero. Zero means
Data Element 35 468
that the number of offenders is unknown; therefore, the relationship
cannot be entered.
(Relationship of Victim to Offender) has a relationship of VO =
Victim Was Offender. When this code is entered, a minimum of two
victim and two offender segments must be submitted. In this case,
only one victim and/or one offender segment was submitted. The
Data Element 35 470
entry of VO on one or more of the victims indicates situations such
as brawls and domestic disputes. In the vast majority of cases, each
victim is also the offender; therefore, every victim record would
contain a VO code.
(Relationship of Victim to Offender) has relationships of VO = Victim
Data Element 35 Was Offender that point to multiple offenders, which is an 471
impossible situation. A single victim cannot be two offenders.
(Relationship of Victim to Offender) If Data Element 37 (Age of
Offender) is 00 = Unknown, Data Element 38 (Sex of Offender) is
Data Element 35 U = Unknown, and Data Element 39 (Race of Offender) is 472
U = Unknown, then Data Element 35 (Relationship of Victim to
Offender) must be RU = Relationship Unknown.
6/30/2023 2023.0 NIBRS Technical Specification 109
Relationship(s) of Victim to Offender(s) Element Edits
Associated
Data Element Edit Description
Error Code
(Relationship of Victim to Offender) Segment Level 4 (Victim
Segment) cannot be submitted multiple times with VO = Victim Was
Data Element 35 Offender in Data Element 35 (Relationship of Victim to Offender) 474
when Data Element 34 (Offender Number to be Related) contains
the same data value (indicating the same offender).
(Relationship of Victim to Offender) A victim can only have one
Data Element 35 spousal relationship. In this instance, the victim has a relationship of 475
SE = Spouse to two or more offenders.
(Relationship of Victim to Offender) An offender can only have one
Data Element 35 spousal relationship. In this instance, two or more victims have a 476
relationship of SE = Spouse to the same offender.
Data Values: SE = Victim Was Spouse
CS = Victim Was Common-Law Spouse
PA = Victim Was Parent
SB = Victim Was Sibling
CH = Victim Was Child
GP = Victim Was Grandparent
GC = Victim Was Grandchild
IL = Victim Was In-law
SP = Victim Was Step-parent
SC = Victim Was Step-child
SS = Victim Was Step-sibling
OF = Victim Was Other Family Member
AQ = Victim Was Acquaintance
FR = Victim Was Friend
NE = Victim Was Neighbor
BE = Victim Was Babysittee the Baby/Child in the Care of a Babysitter
BG = Victim Was Boyfriend/Girlfriend
CF = Victim Was Child of Boyfriend/Girlfriend
XR = Victim Was Ex-Relationship (Ex-boyfriend/ex-girlfriend)
XS = Victim Was Ex-Spouse
EE = Victim Was Employee
ER = Victim Was Employer
OK = Victim Was Otherwise Known
RU = Relationship Unknown
ST = Victim Was Stranger
VO = Victim Was Offender
3.3.6 Offender Segment
The Offender Segment is used to describe the offenders in the incident (e.g., their age, sex, race,
and ethnicity). An Offender Segment should be submitted for each of the offenders (up to 99)
involved in the incident. There must be at least one Offender Segment in each incident report.
6/30/2023 2023.0 NIBRS Technical Specification 110
When nothing is known about the offender, then 00 = Unknown Offender must be entered in
Data Element 36 (Offender Sequence Number) and Data Elements 37 through 39 should be left
blank. For example, when a corpse is found in a ditch and there were no eyewitnesses or other
information that would provide data about possible offenders, 00 = Unknown Offender should be
entered. However, when witnesses report five offenders were running from the scene, and their
age, sex, or race are not known, five Offender Segments should be submitted indicating the
appropriate data elements are unknown.
Note: In addition to the data elements specified, the Offender Segment also contains the Header
Data Elements identified in Section 3.3.1, as well as Data Element 1 (ORI) and Data Element 2
(Incident Number) included in the Administrative Segment, Section 3.3.2.
Data Element 36-Offender Sequence Number
Offender Sequence Number is used to assign a sequence number from 01–99 for each offender
in an incident.
Group: A
Format: 2-Character Numeric
Position: 38–39
Occurrence: Once per Offender Segment
Mandatory: Yes
Edits:
Table 3-52 Offender Sequence Number Edit Description
Offender Sequence Number Element Edits
Associated
Data Element Edit Description
Error Code
(Offender Sequence Number) The referenced data element in an
incident must contain data when the referenced data element is
Data Element 36 501
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
Data Element 36 (Offender Sequence Number) must contain
Data Element 36 502
numeric entry (00 through 99) with zero left-fill.
(Offender Sequence Number) When multiple Offender Segments
are submitted, none can contain a 00 = Unknown value because the
Data Element 36 presence of 00 indicates that the number of offenders is unknown. 555
In this case, multiple offenders were submitted, but one of the
segments contains the 00 = Unknown value.
(Offender Sequence Number) contains 00 indicating that nothing is
known about the offender(s) regarding number and any identifying
Data Element 36 information. To exceptionally clear the incident, the value cannot be 557
00. The incident was submitted with Data Element 4 (Cleared
Exceptionally) having a value of A through E.
(Offender Sequence Number) The incident was submitted with Data
Element 6 (UCR Offense Code) value of 09C = Justifiable Homicide
or 360 = Failure to Register as a Sex Offender*, but unknown
Data Element 36 information was submitted for all the offender(s). At least one of the 559
offenders must have known information for age, sex, and race.
*Denotes offenses for federal and tribal LEA reporting only
Data Values: 00 = Unknown Offender
6/30/2023 2023.0 NIBRS Technical Specification 111
01–99
Data Element 37-Age of Offender
Age of Offender is used to indicate the age of the offender. The data value for Age of Offender
can be an exact age, a range of years, or unknown.
For an exact age, use only record positions 40 and 41 (leave positions 42 and 43 blank). To enter
an age range, enter the beginning age in the range in positions 40 and 41 and the ending age in
the range in positions 42 and 43.
When Age of Offender is populated with an age range (i.e., 16 through 19), then the system will
store the average age, decimal value truncated. For example, when the age range is 16 through
19, the average is 17.5 years old and is stored as 17 years.
Group: A
Format: 4-Character Numeric
Position: 40–43
Occurrence: Once per Offender Segment
Mandatory: Conditional
Edits:
Table 3-53 Age of Offender Edit Description
Age of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Age of Offender) The referenced data element in an Incident must
contain data when the referenced data element is mandatory or
Data Element 37 501
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Age of Offender) contains data but is not left-justified. A single
Data Element 37 508
two-character age must be in positions 1 through 2 of the field.
(Age of Offender) contains more than two characters indicating a
Data Element 37 possible age-range is being attempted. If so, the field must contain 509
a numeric entry of four digits.
(Age of Offender) was entered as an age-range. Accordingly, the
Data Element 37 510
first age component must be less than the second age.
(Age of Offender) was entered as an age-range. Therefore, the first
Data Element 37 522
age component cannot be 00 = Unknown.
(Age of Offender) cannot be less than 13 years old when Data
Data Element 37 Element 35 (Relationship of Victim to Offender) contains a 550
relationship of SE = Spouse.
(Age of Offender) Data Element 38 (Sex of Offender), and Data
Data Element 37 Element 39 (Race of Offender) cannot be entered when Data 552
Element 36 (Offender Sequence Number) is 00 = Unknown.
6/30/2023 2023.0 NIBRS Technical Specification 112
Age of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Age of Offender) has a relationship that is inconsistent with the
offender’s age. The age of the victim, and/or offender, must reflect
the implied relationship. For example, if the relationship of the
victim to offender is PA = Parent, then the victim’s age must be
greater than the offender’s age. The following relationships must
Data Element 37 be consistent with the victim’s age in relation to the offender’s age: 554
Relationship Victim’s Age Is
CH = Victim was Child Younger
PA = Victim was Parent Older
GP = Victim was Grandparent Older
GC = Victim was Grandchild Younger
Data Element 37 (Age of Offender) must contain numeric entry of 00 through 99. 556
(Offender Segment) None of the Offender Segments contain all
known values for age, sex, and race. When an incident is cleared
Data Element 37 558
exceptionally (Data Element 4 contains an A through E), one
offender must have all known values.
Data Values: 01–98 = Years Old
99 = Over 98 Years Old
00 = Unknown
Note: Any combination of years is valid for an age range. The younger age must be listed first in
the range. For example, “2530” is a valid age range.
Data Element 38-Sex of Offender
Sex of Offender is used to identify the sex of the offender.
Group: A
Format: 1-Character Alphabetic
Position: 44
Occurrence: Once per Offender Segment
Mandatory: Conditional
Edits:
Table 3-54 Sex of Offender Edit Description
Sex of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Sex of Offender) The referenced data element in an incident must
contain data when the referenced data element is mandatory or when
Data Element 38 501
the conditions are met for data that must be entered into a
conditionally mandatory field.
(Sex of Offender) The referenced data element must contain a valid
Data Element 38 data value when it is entered; blank is permissible on nonmandatory 504
fields.
6/30/2023 2023.0 NIBRS Technical Specification 113
Sex of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Sex of Offender) Data Element 38 and Data Element 39 (Race of
Data Element 38 Offender) cannot be entered when Data Element 36 (Offender 552
Sequence Number) is 00 = Unknown.
(Offender Segment) None of the Offender Segments contain all known
values for age, sex, and race. When an incident is cleared
Data Element 38 558
exceptionally (Data Element 4 contains an A through E) one offender
must have all known values.
Data Values: F = Female
M = Male
U = Unknown
Data Element 39-Race of Offender
Race of Offender is used to identify the race of the offender.
Group: A
Format: 1-Character Alphabetic
Position: 45
Occurrence: Once per Offender Segment
Mandatory: Conditional
Edits:
Table 3-55 Race of Offender Edit Description
Race of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Race of Offender) The referenced data element in an incident must
contain data when the referenced data element is mandatory or 501
Data Element 39
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Race of Offender) The referenced data element must contain a
Data Element 39 valid data value when it is entered; blank is permissible on 504
nonmandatory fields.
Data Element 38 (Sex of Offender), and Data Element 39 (Race of
Data Element 39 Offender) cannot be entered when Data Element 36 (Offender 552
Sequence Number) is 00 = Unknown.
(Offender Segment) None of the Offender Segments contain all
known values for age, sex, and race. When an Incident is cleared 558
Data Element 39
exceptionally (Data Element 4 contains an A through E) one
offender must have all known values.
Data Values: W = White
B = Black or African American
I = American Indian or Alaska Native
A = Asian
P = Native Hawaiian or Other Pacific Islander
6/30/2023 2023.0 NIBRS Technical Specification 114
U = Unknown
Data Element 39A-Ethnicity of Offender
Ethnicity of Offender is used to identify the ethnicity of the offender.
Group: A
Format: 1-Character Alphabetic
Position: 46
Occurrence: Once per Offender Segment
Mandatory: Optional
Edits:
Table 3-56 Ethnicity of Offender Edit Description
Ethnicity of Offender Element Edits
Associated
Data Element Edit Description
Error Code
(Ethnicity of Offender) The referenced data element must contain
Data Element 39A a valid data value when it is entered; blank is permissible on 504
nonmandatory fields.
(Ethnicity of Offender) Data Element 38 (Sex of Offender) and
Data Element 39A Data Element 39 (Race of Offender) cannot be entered when 552
Data Element 36 (Offender Sequence Number) is 00 = Unknown.
Data Values: H = Hispanic or Latino
N = Not Hispanic or Latino
U = Unknown
3.3.7 Arrestee Segment/Group B Arrest Report Segment
The Arrestee Segment and Group B Arrest Report Segment are used to report the apprehension
of the persons who committed crimes (up to 99) reported for Group A and Group B offenses, to
describe the arrestee (e.g., age, sex, race, and ethnicity), and to indicate the circumstances of the
arrest.
One “Arrestee Segment” is submitted for each person arrested for committing offenses in an
incident that involves at least one Group A offense. Therefore, both Group A and Group B
offenses can be submitted in Data Element 45 (UCR Arrest Offense Code).
One Group B Arrest Report Segment is submitted for each person arrested for committing a
Group B offense.
When the apprehension of an arrestee results in the submission of an Arrestee Segment for more
than one incident within the jurisdiction of the LEA, Data Element 44 (Multiple Arrestee
Segments Indicator) must contain C = Count Arrestee for one of the Arrestee Segments and M =
Multiple must be entered for the remaining Arrestee Segments submitted for the incidents.
Differences between the Arrestee Segment and the Group B Arrest Report Segment are:
• The Arrestee Segment is uniquely identified by Data Element 1 (ORI), Data Element 2
(Incident Number), and Data Element 40 (Arrestee Sequence Number); the Group B
Arrest Report Segment is uniquely identified by the Data Element 1 (ORI), Data Element
6/30/2023 2023.0 NIBRS Technical Specification 115
41 (Arrest Transaction Number), and Data Element 40 (Arrestee Sequence Number) and
Data Element 2 (Incident Number) is not used.
• In the Group B Arrest Report Segment, Data Element 40 (Arrestee Sequence Number)
and Data Element 41 (Arrest Transaction Number) are reversed.
• The record positions of many of the data elements are different when comparing the
Arrestee Segment and the Group B Arrest Report Segment. The differences are noted in
the various data element descriptions.
• The Group B Arrest Report Segment does not use Data Element 44 (Multiple Arrestee
Segments Indicator).
Note: In addition to the data elements specified, the Arrestee Segment and Group B Arrest
Report Segment also contain the Header Data Elements identified in Section 3.3.1, as well as
Data Element 1 (ORI) and Data Element 2 (Incident Number) [for only the Arrestee Segment]
included in the Administrative Segment, Section 3.3.2.
Data Element 40-Arrestee Sequence Number
Arrestee Sequence Number is used to assign a sequence number from 01–99 to the arrestees in
an incident.
Group: A, B
Format: 2-Character Numeric
Position: 38–39 (both Arrestee Segment/Group B Arrest Report Segment)
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-57 Arrestee Sequence Number Edit Description
Arrestee Sequence Number Element Edits
Associated
Data Element Edit Description
Error Code
(Arrestee Sequence Number) The referenced data element in an
incident must contain data when the referenced data element is
Data Element 40 601, 701
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
Data Element 40 (Arrestee Sequence Number) must be numeric
Data Element 40 602,702
entry of 01 to 99 with zero left-fill.
Data Values: 01–99
Data Element 41-Arrest Transaction Number
Arrest Transaction Number is used to assign a unique identifier to each arrest report submitted.
The arrest transaction number may be the incident number of the incident relating to the arrest
(for the Arrestee Segment) or a separate transaction number relating to the arrest.
Group: A, B
Format: 12-Character Alphanumeric
6/30/2023 2023.0 NIBRS Technical Specification 116
Position: 40–51 Arrestee Segment
26–37 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-58 Arrest Transaction Number Edit Description
Arrestee Transaction Number Element Edits
Associated
Data Element Edit Description
Error Code
(Arrest Transaction Number) The referenced data element in an
incident must contain data when the referenced data element is
Data Element 41 mandatory or when the conditions are met for data that must be 601, 701
entered into a conditionally mandatory field.
(Arrest Transaction Number) Must be blank right-fill if under 12
Data Element 41 characters in length. Cannot have embedded blanks between the 615, 715
first and last characters entered.
(Arrest Transaction Number) Must be left-justified with blank right-
Data Element 41 fill if under 12 characters in length. 616, 716
(Arrest Transaction Number) Must contain a valid character
combination of the following:
• A–Z (capital letters only)
Data Element 41 • 0–9 617, 717
• Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not valid.
Data Values: 12-character alphanumeric value consisting of:
A–Z
0–9
Hyphen
Data Element 42-Arrest Date
Arrest Date is used to enter the year, month, and day of the arrest.
Group: A, B
Format: 8-Character Numeric (YYYY/MM/DD)
Position: 52–59 Arrestee Segment
40–47 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
6/30/2023 2023.0 NIBRS Technical Specification 117
Table 3-59 Arrest Date Edit Description
Arrestee Date Element Edits
Associated
Data Element Edit Description
Error Code
(Arrest Date) The referenced data element in an incident must
contain data when the referenced data element is mandatory or when
Data Element 42 601, 701
the conditions are met for data that must be entered into a
conditionally mandatory field.
(Arrest Date) Each component of the date must be valid; that is,
months must be 01 through 12, days must be 01 through 31, and
year must include the century (i.e., 19xx, 20xx). In addition, days
cannot exceed maximum for the month (e.g., June cannot have 31
days). The date cannot exceed the current date.
Data Element 42 605, 705
The date cannot be later than that entered within the Month of
Electronic submission and Year of Electronic submission fields on the
data record. For example, if Month of Electronic submission and Year
of Electronic submission are 06/1999, the arrest date cannot contain
any date 07/01/1999 or later.
(Arrest Date) The UCR Program has determined that an ORI will no
Data Element 42 longer be submitting data to the FBI as of an inactive date. The FBI 618, 718
will not accept arrest data from this ORI after this date.
(Arrest Date) cannot be earlier than Data Element 3 (Incident
Date/Hour). A person cannot be arrested before the incident
occurred.
The exception to this rule is when an additional arrest is reported for
Data Element 42 a pre-NIBRS incident. In this case, Segment Level 6 (Arrestee 665
Segment) will contain I = Incident Report, but the data value in Data
Element 2 (Incident Number) will not match an incident already on file
in the national UCR database. The segment will be processed, but
used only for SRS purposes and will not be included in the agency’s
NIBRS figures.
Group B Arrest Report (Level 7) submitted with a Segment Action
Data Element 42 Type of A = Add cannot have Data Element 42 (Arrest Date) earlier 720
than the Base Date.
(Arrest Date) is missing for a Group B Arrest Report with a Segment
Data Element 42 Action Type of D = Delete; must be populated with a valid data value 797
and cannot be blank.
(Arrest Date) is missing for a Group B Arrest Report with a Segment
Action Type of D = Delete; at least one Group B Arrest Report is on
Data Element 42 798
file that matches Data Element 41 (Arrest Transaction Number) with
an Arrest Date outside the two year window.
(Arrest Date) is missing for a Group B Arrest Report with a Segment
Data Element 42 Action Type of D = Delete; multiple Group B Arrest Reports are on file 799
that match Data Element 41 (Arrest Transaction Number).
Data Values: Data Element 42 (Arrest Date) must be a valid date in YYYYMMDD format:
Year (YYYY): 1991–Current
Month (MM):
01 = January
02 = February
6/30/2023 2023.0 NIBRS Technical Specification 118
03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
Day of the Month (DD): 01–31 (depending on the month)
Data Element 43-Type of Arrest
Type of Arrest is used to indicate how the offender was arrested.
Group: A, B
Format: 1-Character Alphabetic
Position: 60 Arrestee Segment
48 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-60 Type of Arrest Edit Description
Type of Arrest Element Edits
Associated
Data Element Edit Description
Error Code
(Type of Arrest) The referenced data element in an incident must 601, 701
contain data when the referenced data element is mandatory or
Data Element 43
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Type of Arrest) The referenced data element must contain a valid
Data Element 43 data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
Data Values:
O = On-View Arrest (apprehension without a warrant or previous incident report)
S = Summoned/Cited (not taken into custody)
T = Taken Into Custody (based on a warrant and/or previously submitted incident
report)
Data Element 44-Multiple Arrestee Segments Indicator
Multiple Arrestee Segments Indicator is used to ensure that an arrestee is counted only once
when the arrestee’s apprehension causes the reporting agency to submit two or more Arrestee
Segments concerning separate Group A Incident Reports.
6/30/2023 2023.0 NIBRS Technical Specification 119
When the arrestee was involved in more than one crime and is arrested, enter C = Count Arrestee
in one of the Arrestee Segments and enter M = Multiple in all of the remaining Arrestee
Segments. When the arrest does not cause the reporting agency to submit multiple Arrestee
Segments for the same arrestee, N = Not Applicable should be entered.
Group: A
Format: 1-Character Alphabetic
Position: 61 Arrestee Segment
Occurrence: Once per Arrestee Segment
Mandatory: Yes
Edits:
Note:
Table 3-61 Multiple Arrestee Segments Indicator Edit Description
Multiple Arrestee Segments Indicator Element Edits
Associated
Data Element Edit Description
Error Code
(Multiple Arrestee Segments Indicator) The referenced data element
in an Incident must contain data when the referenced data element
Data Element 44 601
is mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
(Multiple Arrestee Segments Indicator) The referenced data element
Data Element 44 must contain a valid data value when it is entered; blank is 604
permissible on nonmandatory fields.
Data Values: C = Count Arrestee
M = Multiple
N = Not Applicable
Data Element 45-UCR Arrest Offense Code
UCR Arrest Offense Code is used to enter the 3-character UCR Offense Code of the offense for
which the arrestee was apprehended. When the arrestee was apprehended for more than one
offense, the reporting agency must determine which offense was the most serious and enter it as
the arrest offense.
Note: The UCR Arrest Offense Code does not have to match the data value entered in Data
Element 6 (UCR Offense Code).
Group: A, B
Format: 3-Character Alphanumeric
Position: 62–64 Arrestee Segment
49–51 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
6/30/2023 2023.0 NIBRS Technical Specification 120
Table 3-62 UCR Arrest Offense Code Edit Description
UCR Arrest Offense Code Element Edits
Associated
Data Element Edit Description
Error Code
(UCR Arrest Offense Code) The referenced data element in an
Incident must contain data when the referenced data element is
Data Element 45 601, 701
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
(UCR Arrest Offense Code) The referenced data element must
Data Element 45 contain a valid data value when it is entered; blank is permissible 604, 704
on nonmandatory fields.
(UCR Arrest Offense Code) The following values for Data Element
45 (UCR Arrest Offense Code) are valid only for use by federal and
tribal agencies:
26H = Money Laundering
101 = Treason
103 = Espionage
30A = Illegal Entry into the United States
30B = False Citizenship
30C = Smuggling Aliens
30D = Re-entry after Deportation
360 = Failure to Register as a Sex Offender
49A = Harboring Escapee/Concealing from Arrest
Data Element 45 49B = Flight to Avoid Prosecution 650, 750
49C = Flight to Avoid Deportation
521 = Violation of National Firearm Act of 1934
522 = Weapons of Mass Destruction
526 = Explosives
58A = Import Violations
58B = Export Violations
61A = Federal Liquor Offenses
61B = Federal Tobacco Offenses
620 = Wildlife Trafficking
90K = Failure to Appear
90L = Federal Resource Violations
90M = Perjury
(UCR Arrest Offense Code) was entered with 09C = Justifiable
Data Element 45 670
Homicide. This is not a valid arrest offense.
(UCR Arrest Offense Code) must contain a Group B Offense Code
Data Element 45 in Data Element 45 (UCR Arrest Offense). The offense code 760
submitted is not a Group B offense code.
Data Values: Refer to Appendix A:–Group A Offenses and Group B Offenses
Data Element 46-Arrestee Was Armed With
Arrestee Was Armed With is used to indicate whether the arrestee was armed with a commonly
known weapon at the time of apprehension.
Group: A, B
Format: 2-Character Numeric
Position: 65–66 Weapon 1 Arrestee Segment
68–69 Weapon 2
6/30/2023 2023.0 NIBRS Technical Specification 121
52–53 Weapon 1 Group B Arrest Report Segment
55–56 Weapon 2
Occurrence: 2 times per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-63 Arrestee Was Armed With Edit Description
Arrestee Was Armed With Element Edits
Associated
Data Element Edit Description
Error Code
(Arrestee Was Armed With) The referenced data element in an
Incident must contain data when the referenced data element is
Data Element 46 601, 701
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
(Arrestee Was Armed With) The referenced data element must
Data Element 46 contain a valid data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
(Arrestee Was Armed With) The referenced data element in error is
Data Element 46 one that contains multiple data values. When more than one code is 606, 706
entered, none can be duplicate codes.
(Arrestee Was Armed With) can have multiple data values and was
Data Element 46 entered with multiple values. However, 01 = Unarmed cannot be 607, 707
entered with any other data value.
Data Values: 01 = Unarmed
11 = Firearm (type not stated)
12 = Handgun
13 = Rifle
14 = Shotgun
15 = Other Firearm
16 = Lethal Cutting Instrument
17 = Club/Blackjack/Brass Knuckles
Data Element 46-Automatic Weapon Indicator
Automatic Weapon Indicator is used to indicate whether a firearm identified in Data Element 46
(Arrestee Was Armed With) is an automatic firearm (i.e., any firearm that shoots or is designed
to shoot more than one shot at a time by a single pull of the trigger without manual reloading).
Group: A, B
Format: 1-Character Alphabetic
Position: 67 Indicator 1 Arrestee Segment
70 Indicator 2
54 Indicator 1 Group B Arrest Report Segment
57 Indicator 2
Occurrence: 2 times per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Conditional
6/30/2023 2023.0 NIBRS Technical Specification 122
This data element is mandatory when Data Element 46 (Arrestee Was Armed With) is a firearm
(data values 11–15).
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-64 Automatic Weapon Indicator Edit Description
Automatic Weapon Indicator Element Edits
Associated
Data Element Edit Description
Error Code
(Automatic Weapon Indicator) The referenced data element must
Data Element 46 contain a valid data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
(Automatic Weapon Indicator) does not have A = Automatic or a
Data Element 46 654, 754
blank in the third position of field.
(Automatic Weapon Indicator) In Data Element 46 (Arrestee Was
Armed With) A = Automatic is the third character of code. It is valid
only with codes:
11 = Firearm (Type Not Stated)
12 = Handgun
Data Element 46 655, 755
13 = Rifle
14 = Shotgun
15 = Other Firearm
A weapon code other than those mentioned was entered with the
automatic indicator. An automatic weapon is, by definition, a firearm.
Data Values: A = Automatic
(blank) = Not Automatic
Data Element 47-Age of Arrestee
Age of Arrestee is used to indicate the age of the arrestee. The data value for Age of Arrestee can
be an exact age, a range of years, or unknown.
For an exact age, use only the first two record positions (71 and 72 in the Arrestee Segment and
58 and 59 in the Group B Arrest Report Segment) and leave the other two positions blank. To
enter an age range, enter the beginning age in the range in the first two record positions and the
ending age in the range in the last two positions.
When Age of Arrestee is populated with an age range (i.e., 16 through 19), then the system will
store the average age, decimal value truncated. For example, when the age range is 16 through
19, the average is 17.5 years old and is stored as 17 years.
Group: A, B
Format: 2-Character Numeric
Position: 71–74 Arrestee Segment
58–61 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
6/30/2023 2023.0 NIBRS Technical Specification 123
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-65 Age of Arrestee Edit Description
Age of Arrestee Element Edits
Associated
Data Element Edit Description
Error Code
(Age of Arrestee) The referenced data element in an Incident
must contain data when the referenced data element is mandatory
Data Element 47 601, 701
or when the conditions are met for data that must be entered into
a conditionally mandatory field.
(Age of Arrestee) contains data, but is not left-justified. A single
Data Element 47 608, 708
two-character age must be in positions 1 through 2 of the field.
(Age of Arrestee) contains more than two characters indicating a
Data Element 47 possible age-range is being attempted. If so, the field must 609, 709
contain a numeric entry of four digits.
(Age of Arrestee) was entered as an age-range. Accordingly, the
Data Element 47 610, 710
first age component must be less than the second age.
(Age of Arrestee) was entered as an age-range. Therefore, the
Data Element 47 622, 722
first age component cannot be 00 = Unknown.
(Disposition of Arrestee Under 18) was not entered, but Data
Data Element 47 Element 47 (Age of Arrestee) is under 18. Whenever an arrestee’s 652, 752
age indicates a juvenile, the agency must enter the disposition.
Data Element 47 Data Element 47 (Age of Arrestee) does not contain a numeric
664
entry of 00 through 99 for an exact age.
Data Element 47 Data Element 47 (Age of Arrestee) does not contain a numeric
757
entry of 00 through 99 for an exact age.
Data Values: 01–98 = Years Old
99 = Over 98 Years Old
00 = Unknown
Note: Any combination of years is valid for an age range. The younger age must be listed first in
the range. For example, “2530” is a valid age range.
Data Element 48-Sex of Arrestee
Sex of Arrestee is used to indicate the sex of the arrestee.
Group: A, B
Format: 1-Character Alphabetic
Position: 75 Arrestee Segment
62 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
6/30/2023 2023.0 NIBRS Technical Specification 124
Table 3-66 Sex of Arrestee Edit Description
Sex of Arrestee Element Edits
Associated
Data Element Edit Description
Error Code
(Sex of Arrestee) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
Data Element 48 601, 701
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Sex of Arrestee) does not contain a valid code of M = Male or
Data Element 48 F = Female. 667, 758
Note: U = Unknown (if entered) is not a valid sex for an arrestee.
Data Values: F = Female
M = Male
Data Element 49-Race of Arrestee
Race of Arrestee is used to describe the race of the arrestee.
Group: A, B
Format: 1-Character Alphabetic
Position: 76 Arrestee Segment
63 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Yes
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-67 Race of Arrestee Edit Description
Race of Arrestee Element Edits
Associated
Data Element Edit Description
Error Code
(Race of Arrestee) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
Data Element 49 601, 701
when the conditions are met for data that must be entered into a
conditionally mandatory field.
(Race of Arrestee) The referenced data element must contain a valid
Data Element 49 data value when it is entered; blank is permissible on nonmandatory 604, 704
fields.
Data Values: W = White
B = Black or African American
I = American Indian or Alaska Native
A = Asian
P = Native Hawaiian or Other Pacific Islander
U = Unknown
Data Element 50-Ethnicity of Arrestee
Ethnicity of Arrestee is used to describe the ethnicity of the arrestee.
6/30/2023 2023.0 NIBRS Technical Specification 125
Group: A, B
Format: 1-Character Alphabetic
Position: 77 Arrestee Segment
64 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Optional
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-68 Ethnicity of Arrestee Edit Description
Ethnicity of Arrestee Element Edits
Associated
Data Element Edit Description
Error Code
(Ethnicity of Arrestee) The referenced data element must contain a
Data Element 50 valid data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
Data Values: H = Hispanic or Latino
N = Not Hispanic or Latino
U = Unknown
Data Element 51-Resident Status of Arrestee
Resident Status of Arrestee is used to enter the arrestee’s resident status (resident, nonresident,
unknown) of the reporting agency’s jurisdiction.
Group: A, B
Format: 1-Character Alphabetic
Position: 78 Arrestee Segment
65 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Optional
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-69 Resident Status of Arrestee Edit Description
Resident Status of Arrestee Element Edits
Associated
Data Element Edit Description
Error Code
(Resident Status of Arrestee) The referenced data element must
Data Element 51 contain a valid data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
Data Values: R = Resident
N = Nonresident
U = Unknown
6/30/2023 2023.0 NIBRS Technical Specification 126
Data Element 52-Disposition of Arrestee Under 18
Disposition of Arrestee Under 18 is used to report the nature of the arrestee’s detention when the
arrestee is under 18 years of age or when the arrestee’s age was entered as an age range and the
average age was under 18 years of age at the time of the arrest.
Group: A, B
Format: 1-Character Alphabetic
Position: 79 Arrestee Segment
66 Group B Arrest Report Segment
Occurrence: Once per Arrestee Segment/Group B Arrest Report Segment
Mandatory: Conditional
This data element is mandatory when Data Element 47 (Age of Arrestee) contains an age under
18.
Edits:
Note: Error Codes 600–699 are used for Arrestee Segment edits. Error Codes 700–799 are used
for Group B Arrest Report Segment edits.
Table 3-70 Disposition of Arrestee Under 18 Edit Description
Disposition of Arrestee Under 18 Element Edits
Associated
Data Element Edit Description
Error Code
(Disposition of Arrestee Under 18) The referenced data element must
Data Element 52 contain a valid data value when it is entered; blank is permissible on 604, 704
nonmandatory fields.
(Disposition of Arrestee Under 18) was not entered, but Data Element
Data Element 52 47 (Age of Arrestee) is under 18. Whenever an arrestee’s age 652, 752
indicates a juvenile, the agency must enter the disposition.
(Disposition of Arrestee Under 18) was entered, but Data Element 47
(Age of Arrestee) is 18 or greater. Whenever an arrestee’s age
Data Element 52 653, 753
indicates an adult, the agency cannot enter the juvenile disposition
because it does not apply.
Data Values:
H = Handled Within Department (released to parents, released with warning, etc.)
R = Referred to Other Authorities (turned over to juvenile court, probation
department, welfare agency, other police agency, criminal or adult court, etc.)
3.3.8 Zero Report Segment
The Zero Report Segment is used to report that the LEA has no crime, arrests, or recovered
property to report for the given month. In order to compute valid crime rates and trends, it is
necessary that the FBI be able to identify months during which no criminal activity occurred.
Note: In addition to the data elements specified, the Zero Report Segment also contains the
Header Data Elements identified in Section 3.3.1, as well as Data Element 1 (ORI) and Data
Element 2 (Incident Number) included in the Administrative Segment, Section 3.3.2.
6/30/2023 2023.0 NIBRS Technical Specification 127
Refer to Section 4.7, Zero Reporting, for additional information pertaining to the handling of
zero reporting information.
Data Element (unnumbered)-Zero Report Month
Zero Report Month is used to identify the month in which the LEA has no crime, arrests, or
recovered property to report.
Group: N/A
Format: 2-Character Numeric (MM)
Positions: 38–39
Occurrence: Once per Zero Report Segment
Mandatory: Yes
Edits:
Table 3-71 Zero Report Month Edit Description
Zero Report Month Element Edits
Associated
Data Element Edit Description
Error Code
Mandatory Data Elements (Mandatory = Yes) must be
Zero Report Element (Month) 001
populated with a valid data value and cannot be blank.
Zero Report Month must be a valid month, data values 01
Zero Report Element (Month) 090
through 12.
Zero Report Month and Zero Report Year cannot precede
Zero Report Element (Month) the month and year in the date the LEA converted to the 093
NIBRS.
A Segment Level 0 was submitted with a month and year
entered into positions 38 through 43 that was later than
Zero Report Element (Month) 094
the Month of Electronic submission and Year of Electronic
submission entered into positions 7 through 12.
The combined Zero Report Month and Zero Report Year
cannot be on or after the date LEA is placed in Covered-
by Status. When Zero Report data are received for a LEA
in Covered-by Status, the FBI will remove the agency from
Zero Report Element (Month) 096
Covered-by Status, process the submission, and notify the
agency. Additionally, adjustments to previously submitted
data from an agency now in Covered-by Status will be
processed and no error generated.
Data Values: 01 = January
02 = February
03 = March
04 = April
05 = May
06 = June
07 = July
08 = August
09 = September
10 = October
11 = November
12 = December
6/30/2023 2023.0 NIBRS Technical Specification 128
Data Element (unnumbered)-Zero Report Year
Zero Report Year is used to identify the year in which Zero Report Month occurred.
Group: N/A
Format: 4-Character Numeric (YYYY)
Position: 40–43
Occurrence: Once per Zero Report Segment
Mandatory: Yes
Edits:
Table 3-72 Zero Report Year Edit Description
Zero Report Year Element Edits
Associated
Data Element Edit Description
Error Code
Mandatory Data Elements (Mandatory = Yes) must be
Zero Report Element (Year) 001
populated with a valid data value and cannot be blank.
Zero Report Month and Zero Report Year cannot
Zero Report Element (Year) precede the month and year in the date the LEA 093
converted to the NIBRS.
A Segment Level 0 was submitted with a month and year
entered into positions 38 through 43 that was later than
Zero Report Element (Year) the Month of Electronic submission and Year of 094
Electronic submission entered into positions 7 through
12.
Data Values: 1991–Current Year
6/30/2023 2023.0 NIBRS Technical Specification 129
4 SUBMISSION SPECIFICATIONS
Data may be submitted monthly via e-mail. This section describes the data submission format.
NIBRS submissions should be e-mailed to the following addresses:
• Test submissions & Production submissions: ucrstat@leo.gov
When submitting test data, the subject line of the email should state that the data being sent is
test data.
4.1 Segment Length
Each segment in a Group A Incident Report has its own fixed length, defined in the Header Data
Element “Segment Length.” For example, an Administrative Segment (Level 1) with Cargo
Theft must include 88 characters of data and the data value for Segment Length must be “0088”.
4.2 Data Records Must Be Initialized to Blanks
Each record written to a submission must first be initialized to “BLANKS” before data are
moved into the applicable fields. This will provide filler for those varying Data Elements that do
not have data because of the circumstances of the report or that are no longer used in the NIBRS.
4.3 Codes Must Be Right-Justified With Zero Left-Fill
Fields containing numeric data codes should be right justified with zero left-fill when there is
data to be reported. For example, when Data Element 15 (Property Description) code is 05 =
Buses, data value “05” would be entered, not “5b/” or “bb5” (bb = blank). The field should be
filled with blanks when no data are to be reported. Refer to individual data element for specific
formatting instructions.
4.4 Victim/Offender/Arrestee Sequence Numbers Can Have Gaps
Multiple Victim, Offender, and Arrestee Segments can have gaps in values entered into Data
Elements 23 (Victim Sequence Number), 36 (Offender Sequence Number), and 40 (Arrestee
Sequence Number). For instance, when four Offender Segments are submitted, the sequence
numbers would normally be 01, 02, 03, and 04; but could be 02, 03, 05, and 07.
The gaps in numbers could occur, for instance, where all offenders are initially entered into the
LEA’s database with consecutive sequence numbers. Then, one of the offenders is subsequently
deleted, thus possibly leaving a gap in the sequence numbers. Forcing a renumbering of these
numbers would be a complicated process, especially when multiple victims would have to be
adjusted to reflect the renumbered offender numbers in Data Element 34 (Offender Number to be
Related).
4.5 Segment Levels
The 58 numbered data elements and 11 structural data elements comprising a NIBRS data
submission are grouped into eight distinct Segment Levels identified as Levels 0–7. Each
segment must be identified by specifying the Segment Level data value. These values are
identified in Section 3.3.1: Header Data Elements, and Section 3.3.1.2: Segment Level.
6/30/2023 2023.0 NIBRS Technical Specification 130
UCR programs are responsible for ensuring that all Group A Incident Report data for the LEAs
that report to them are grouped in a submission by ORI (Data Element 1) and that the individual
segments making up each Incident Number (Data Element 2) within the ORI are in sequence by
Segment Level.
It is acceptable that the different ORIs themselves are not in sequence and that the different
Incident Numbers are not in sequence within the submitted ORI.
It is not acceptable to intersperse Zero Report Segments (Level 0) and Group B Arrest Report
Segments (Level 7) between Group A Incident Report segments (Levels 1–6).
4.6 Segment Action Types
Segment Action Type is a one-character alphabetic field. This data element identifies the
processing to be performed by the system in relation to the specified segment and is located at
the beginning of each segment in the Header Data Elements. These values are introduced in
Section 3.3.1, Header Data Elements, and Segment Action Type.
The data values for Segment Action Type are:
4.6.1 I = Incident Report
Applies to: Group A Incident Report
• Level 1–Administrative Segment
• Level 2–Offense Segment
• Level 3–Property Segment
• Level 4–Victim Segment
• Level 5–Offender Segment
• Level 6–Arrestee Segment
Description: This value is used to submit all known data at the time a Group A Incident Report
is initially submitted.
This Segment Action Type is also used to resubmit an entire Group A Incident Report previously
reported to the FBI, but which is deleted because one or more segments needed to be added,
modified, or deleted.
The LEA’s system must be designed so that the first I = Incident Report submission is never
preceded by a D = Delete action for that incident.
4.6.2 A = Add
Applies to: Group B Arrest Report
• Level 7–Group B Arrest Report Segment
Description: This value is used to submit all known data at the time a Group B Arrest Report is
initially submitted.
Applies to: Zero Report Segment
• Level 0–Zero Report Segment
Description: This value is used to submit a Zero Report, meaning no incidents or arrests
occurred during the reporting period.
6/30/2023 2023.0 NIBRS Technical Specification 131
4.6.3 D = Delete
Note: All segment level header data elements are required in addition to the specific data
elements listed below. Failure to submit valid segment level header data elements will result in
the generation of an error and the failure to delete the request incident. The required segment
header data elements are below:
• Segment Length
• Segment Level
• Segment Action Type
• Month of Submission
• Year of Submission
• City Indicator (Applicable only to direct reports)
Applies to: Group A Incident Report
• Level 1–Administrative Segment
Description: This value is used to delete all data from the database that is associated with a
Group A Incident Report.
When the Incident Number is on file, Segment Action Type D = Delete deletes all data from the
database that is associated with a Group A Incident Report.
Segment Action Type D = Delete is not allowed for pre-NIBRS submissions (i.e., when there is
no Group A Incident Report on file).
For Group A Incident data the following data elements are mandatory with Segment Action Type
D = Delete:
• Data Element 1 = ORI
• Data Element 2 = Incident Number
• Data Element 3 = Incident Date
Note: All other data elements are ignored.
Applies to: Group B Arrest Report
• Level 7–Group B Arrest Report Segment
Description: This value is used to delete the referenced Group B Arrest Report.
For Group B Incident data the following data elements are mandatory with Segment Action Type
D = Delete:
• Data Element 1 = ORI
• Data Element 41 = Arrest Transaction Number
• Data Element 42 = Arrest Date
Data Element 40 = Arrestee Sequence Number is an optional addition to the Delete. If data
element 40 = Arrest Sequence number exists, then only the specific arrestee is deleted. If data
6/30/2023 2023.0 NIBRS Technical Specification 132
element 40 = Arrest Sequence number is not entered, all arrestees associated with the arrest
Transaction Number will be deleted.
All other data elements are ignored.
Applies to: Zero Report Segment
• Level 0–Zero Report Segment
Description: This value is used to delete the Zero Report Segment in the system for the specified
ORI (Data Element 1), Zero Report Month, and Zero Report Year.
For Zero Report Segment data the following data elements are mandatory with Segment Action
Type D = Delete:
• Data Element 1 = ORI
• Data Element 2 = Incident Number = 000000000000
• Zero Report Month
• Zero Report Year
4.7 Zero Reporting
When a Zero Report Segment is submitted by (or on behalf of) an agency for a specific
month/year, and a Group A Incident or Group B Arrest Report is already on file, UCR will
generate a “Cannot Add Zero Report” error (Zero Report Error 028 or 029, respectively). When
a delete Zero Report Segment is submitted by (or on behalf of) an agency for a specific
month/year, and a Group A Incident or Group B Arrest Report is already on file, UCR will
generate a “Cannot Delete Zero Report” error (Zero Report Error 030 or 031, respectively).
When a Group A Incident or Group B Arrest Report is submitted by an agency for a specific
month/year, and a Zero Report indicator is already on file for that agency’s month/year, UCR
will process the submission and automatically remove the Zero Report indicator.
6/30/2023 2023.0 NIBRS Technical Specification 133
5 ERRORS
This section describes error codes and error handling related to submissions. Submissions with
errors will be sent back to the submitting agency for correction.
A list of the software edits used by the FBI for each data element is provided in Section 3.3, Data
Element Descriptions and a complete listing of edits for each segment is provided in Section 5.2,
Error Numbers and Messages. Reporting agencies should incorporate these edits in their IBR
systems.
5.1 Error Data Set
All FBI-detected errors will be written to the Error Data Set (EDS) following the EDS record
layout. The EDS file will then be returned to the reporting agency for error correction. The EDS
will be in ASCII text format with records 146 characters in length.
When a Group A Incident Report contains 25 segments and one segment contains an error, only
the error for this particular segment will be written to the EDS. The other 24 segments will not
be written to the EDS even though they have also been rejected by the FBI. The EDS only
contains descriptions of errors; no references are made to valid segments rejected as a result of
other FBI-detected errors within the incident report.
In addition to any error records generated, an ending record will always be written on the EDS
indicating that the submission was processed by the FBI. Record positions 15–23, the ORI field,
will contain 9 nines (999999999) and record positions 62 to 140, the Error Message field, will
contain “FBI processed submission on MM/DD/YYYY”. When this record is not on the EDS,
the CSMU should be contacted so the submission can be traced.
The table below describes the EDS Record Layout:
Table 5-1 EDS Record Layout
EDS Record Layout
Record
Field Name Description
Position
This value identifies the data value in Header Data Element “Year of
1–4 Year
Submission”.
This value identifies the data value in Header Data Element “Month of
5–6 Month
Submission”.
This value will be the physical record number of the error segment on the
submission.
For example, when the 600th record has an invalid value, then this value
Submission
will contain “0000600”.
7–13 Record
Number Most error segments will have a number, but certain errors will not. For
example, when a segment is missing from a Group A Incident Report, no
submission record number will be shown. The field may be used to assist
with retrieving the exact record in error.
Segment This value identifies the data value in Header Data Element “Segment
14
Action Type Action Type”.
6/30/2023 2023.0 NIBRS Technical Specification 134
EDS Record Layout
Record
Field Name Description
Position
This value identifies the data value in Data Element 1 (ORI).
15–23 ORI Note: The last record processed on the EDS will contain “999999999”
here to indicate that the submission has been processed by the FBI
System.
Incident
24–35 This value identifies the data value in Data Element 2 (Incident Number).
Number
Segment This value identifies the data value in Header Data Element “Segment
36
Level Level”.
UCR
This value identifies the data value in Data Element 6 (UCR Offense
37–39 Offense
Code) on the Offense Segment (Level 2) in error.
Code
This value identifies the data value in Data Element 23 (Victim Sequence
Person Number) on the Victim Segment (Level 4), Data Element 36 (Offender
40–42 Sequence Sequence Number) on the Offender Segment (Level 5), or Data Element
Number 40 (Arrestee Sequence Number) on the Arrestee Segment (Level 6) for
the segment in error.
Type
This value identifies the data value in Data Element 14 (Type Property
43 Property
Loss/Etc.) on the Property Segment (Level 3) in error.
Loss/Etc.
Data
44–46 Element This value identifies the Data Element that is in error.
Number
Error This value identifies the error number that can be used to refer to
47–49
Number additional information about the error condition.
Data Value
50–61 This value identifies the data value that is in error.
In Error
This is the error message associated with the error number identified in
Error record positions 47–49.
62–140
Message Note: When ORI is “99999999”, this value will contain “FBI Processed
Submission on MM/DD/YYYY”.
Unused
141–146 The FBI no longer uses this field.
Field (blank)
5.2 Error Numbers and Messages
This reference listing provides all of the error numbers that are returned on the EDS, their
associated error messages, and brief descriptions of the errors.
The error numbers and their associated error messages are populated below in numerical order
by type and segment. Brief descriptions of each error follow.
6/30/2023 2023.0 NIBRS Technical Specification 135
5.2.1 Structure Check Errors
Table 5-2 Structure Check Errors
Structure Check Errors
Error
Error Message Error Description
Number
Segment Levels in a Group A Incident Report must
SEGMENT LEVELS ARE OUT OF
be organized in numerical order. For example, an
050 NUMERICAL ORDER FOR THIS
incident having segments 1, 2, 2, 3, 4, 4, 4, 5 must
INCIDENT
be written in that order, not as 1, 2, 2, 5, 3, 4, 4, 4.
INVALID RECORD LEVEL ON Segment Level must contain a valid data value
051
SUBMISSION 0–7.
Segment Level 1 (Administrative Segment) with
CANNOT HAVE A GROUP A
Segment Action Type I = Incident Report must be
055 INCIDENT REPORT WITHOUT
the first segment submitted for each Group A
LEVEL 1 SEGMENT
Incident Report.
Data Element 2 (Incident Number) must be a
DUPLICATE INCIDENT-
056 unique number for each incident submitted. No two
PREVIOUSLY ADDED
incidents can have the same incident number.
Month of Submission and Year of Submission must
ALL SEGMENTS IN A
contain the same data values for each segment in
SUBMISSION MUST HAVE SAME
058 a NIBRS submission. The first segment processed
MONTH AND YEAR OF
will be compared with all other segments to check
SUBMISSION
for this condition.
Data Element 1 (ORI) must contain the same state
abbreviation code (e.g., SC, MD, etc.) in the first
ALL SEGMENTS IN SUBMISSION two positions (record positions 17 & 18). For non-
059
MUST BE FROM SAME STATE federal LEAs, every segment in a submission must
have the same state code in the first two positions
of the ORI.
Month of Submission and Year of Submission
PROCESSING DATE PRECEDES
cannot be after the date the FBI receives and
060 MONTH AND YEAR OF
processes a NIBRS submission. This edit checks
SUBMISSION
for data submitted for a future month/year.
Segment Level 2 (Offense Segment) must have at
least one Segment Level 4 (Victim Segment)
EACH OFFENSE MUST HAVE AT connected to it by entering the offense code
065
LEAST ONE VICTIM identified in Data Element 6 (UCR Offense Code)
in Data Element 24 (Victim Connected to UCR
Offense Code).
Data Element 34 (Offender Number to be Related)
has a value that does not have a corresponding
THE CORRESPONDING
Offender Segment. For example, if the field value
070 OFFENDER SEGMENT MUST
shown in Data Element 34 is 15, an Offender
EXIST
Segment does not exist with a value of 15 in Data
Element 36 (Offender Sequence Number).
6/30/2023 2023.0 NIBRS Technical Specification 136
Structure Check Errors
Error
Error Message Error Description
Number
Segment Level 6 (Arrestee Segment) with
Segment Action Type I = Incident Report cannot be
submitted with Data Element 42 (Arrest Date)
containing an arrest date on or earlier than the date
CANNOT HAVE ARRESTS WHEN
071 entered in Data Element 5 (Exceptional Clearance
CLEARED EXCEPTIONALLY
Date) when Data Element 4 (Cleared
Exceptionally) contains a data value other than
N = Not Applicable (indicating the incident is
cleared exceptionally).
Segment Level 3 (Property Segment) must first be
submitted with Data Element 14 (Type Property
Loss/Etc.) as 7 = Stolen/Etc. before it can be
submitted as 5 = Recovered for the same property
in Data Element 15 (Property Description). Any
property being reported as recovered must first be
reported as stolen. There are exceptions to this
rule:
RECOVERED PROPERTY MUST 1) When Data Element 6 (UCR Offense Code)
072 ALSO BE SUBMITTED AS contains an offense that allows property to be
STOLEN recovered without first being stolen in that
same incident (i.e., 250 = Counterfeiting/
Forgery and 280 = Stolen Property Offenses,
58B = Export Violations*).
2) When a vehicle was stolen and the recovered
property in Data Element 15 (Property
Description) is 38 = Vehicle Parts/Accessories.
*Denotes offenses for federal and tribal LEA
reporting only
Segment Level 3 (Property Segment) with
Segment Action Type I = Incident Report must
NUMBER OF RECOVERED
contain a data value in Data Element 18 (Number
VEHICLES CANNOT BE
073 of Stolen Motor Vehicles) greater than or equal to
GREATER THAN THE NUMBER
the data value entered in Data Element 19
STOLEN
(Number of Recovered Motor Vehicles) within the
same incident.
Segment Level 3 (Property Segment) with
Segment Action Type I = Incident Report must be
PROPERTY SEGMENT MUST submitted when Data Element 6 (UCR Offense
074
EXIST WITH THIS OFFENSE Code) contains an offense of
Kidnapping/Abduction, Crimes Against Property,
Drug/Narcotic Offenses, or Gambling Offenses.
Segment Levels 1, 2, 4, and 5 (Administrative
MISSING A MANDATORY Segment, Offense Segment, Victim Segment, and
075 SEGMENT LEVEL FOR A Offender Segment) with Segment Action Type
COMPLETE INCIDENT I = Incident Report must be submitted for each
Group A Incident Report; they are mandatory.
6/30/2023 2023.0 NIBRS Technical Specification 137
Structure Check Errors
Error
Error Message Error Description
Number
Segment Level 3 (Property Segment) with
Segment Action Type I = Incident Report cannot be
submitted unless Data Element 6 (UCR Offense
Code) contains an offense of 100 =
PROPERTY SEGMENT CANNOT Kidnapping/Abduction, Drug/Narcotic Offenses,
076 EXIST WITH OFFENSE 521 = Violation of National Firearm Act of 1934*,
SUBMITTED 522 = Weapons of Mass Destruction*, 526 =
Explosives*, 26H = Money Laundering*,
Commerce Violations*, or Gambling Offenses.
*Denotes offenses for federal and tribal LEA
reporting only
(Type Property Loss/Etc.) Must be 1 = None or
8 = Unknown when Data Element 6 (UCR Offense
Code) contains an offense off 100 =
Kidnapping/Abduction, Drug/Narcotic Offenses,
521 = Violation of National Firearm Act of 1934*,
NEED A PROPERTY LOSS CODE 522 = Weapons of Mass Destruction*, 526 =
077 OF 1 OR 8 WHEN THIS OFFENSE Explosives*, 26H = Money Laundering*,
IS ATTEMPTED Commerce Violations*, or Gambling Offenses and
Data Element 7 (Offense Attempted/Completed) is
Attempted.
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 14 (Type Property Loss/Etc.) must
be 1 = None or 5 = Recovered when Data Element
6 (UCR Offense Code) is 280 = Stolen Property
Offenses, and Data Element 7 (Offense
Attempted/Completed) is C = Completed.
A VALID PROPERTY LOSS CODE
078 DOES NOT EXIST FOR THIS Data Element 14 (Type Property Loss/Etc.) must
COMPLETED OFFENSE be 1 = None, 5 = Recovered, 7 = Stolen/Etc., or
8 = Unknown when Data Element 6 (UCR Offense
Code) is 100 = Kidnapping/Abduction,
220 = Burglary/ Breaking & Entering, or
510 = Bribery, and Data Element 7 (Offense
Attempted/Completed) is C = Completed.
6/30/2023 2023.0 NIBRS Technical Specification 138
Structure Check Errors
Error
Error Message Error Description
Number
Data Element 14 (Type Property Loss/Etc.) must
be None or Seized when Data Element 6 (UCR
Offense Code) is any of the following and Data
Element 7 (Offense Attempted/Completed) is
Completed:
35A = Drug/ Narcotic Violations
35B = Drug Equipment Violations
521= Violation of National Firearm Act of 1934*,
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 14 (Type Property Loss/Etc.) must
be 2 = Burned when Data Element 6 (UCR Offense
Code) is 200 = Arson and Data Element 7 (Offense
Attempted/Completed) is C = Completed.
Data Element 14 (Type Property Loss/Etc.) must
be 3 = Counterfeited/Forged, 5 = Recovered, or
6 = Seized when Data Element 6 (UCR Offense
Code) is 250 = Counterfeiting/Forgery or 58B =
Export Violations*, and Data Element 7 (Offense
Attempted/Completed) is C = Completed.
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 14 (Type Property Loss/Etc.) must
be 4 = Destroyed/Damaged/Vandalized when Data
Element 6 (UCR Offense Code) is
290 = Destruction/Damage/Vandalism of Property
and Data Element 7 (Offense Attempted/
Completed) is C = Completed.
6/30/2023 2023.0 NIBRS Technical Specification 139
Structure Check Errors
Error
Error Message Error Description
Number
Data Element 14 (Type Property Loss/Etc.) must
be 5 = Recovered or 7 = Stolen/Etc. when Data
Element 6 (UCR Offense Code) is any of the
following and Data Element 7 (Offense
Attempted/Completed) is C = Completed:
120 = Robbery
210 = Extortion/Blackmail
23A = Pocket-picking
23B = Purse-snatching
23C = Shoplifting
23D = Theft from Building
23E = Theft from Coin-Operated Machine or
Device
23F = Theft from Motor Vehicle
23G = Theft of Motor Vehicle Parts or Accessories
23H = All Other Larceny
240 = Motor Vehicle Theft
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C = Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
270 = Embezzlement
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 14 (Type Property Loss/Etc.) must
be 6 = Seized when Data Element 6 (UCR Offense
Code) is any of the following and Data Element 7
(Offense Attempted/Completed) is C = Completed:
39A = Betting/Wagering
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment Violation
39D = Sports Tampering
6/30/2023 2023.0 NIBRS Technical Specification 140
Structure Check Errors
Error
Error Message Error Description
Number
The Group A Incident Report submission contains
only offense(s) that are Crimes Against Society.
When this is so, Data Element 25 (Type of Victim)
must be S = Society/Public, and only one victim
may be submitted.
Must be G = Government for the following
offenses:
CRIMES AGAINST SOCIETY CAN 26H = Money Laundering*
080 HAVE ONLY ONE 521 = National Firearm Act 1934*
SOCIETY/PUBLIC VICTIM 522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 141
If Type Property Loss is 1 = None, then an Offense
segment must be submitted in which Data Element
6 (UCR Offense Code) contains a valid offense for
type loss 1 = None and an applicable Data Element
7 (Offense Attempted/Completed) must exist for
that offense.
The following offense/attempted-completed
combinations are valid for Type Loss 1 = None:
Arson-Attempted
Bribery-Attempted/Completed
Burglary/Breaking & Entering-Attempted/
Completed
Counterfeiting/Forgery-Attempted
Destruction/Damage/Vandalism of Property-
Attempted
Drug/Narcotic Violations-Attempted/Completed
Drug Equipment Violations-Attempted/Completed
Embezzlement-Attempted
Extortion/Blackmail-Attempted
False Pretenses/Swindle/Confidence Game-
Attempted
Credit Card/Automated Teller Machine Fraud-
Attempted
Impersonation-Attempted
TYPE PROPERTY LOSS CODE IS Welfare Fraud-Attempted
081 NOT VALID WITH THE Wire Fraud-Attempted
OFFENSES SUBMITTED Identity Theft-Attempted
Hacking/Computer Invasion-Attempted
Betting/Wagering-Attempted
Operating/Promoting/Assisting Gambling-
Attempted
Gambling Equipment Violations- Attempted
Sports Tampering-Attempted
Kidnapping/Abduction-Attempted/Completed
Pocket-picking-Attempted
Purse-snatching-Attempted
Shoplifting-Attempted
Theft From Building-Attempted
Theft From Coin-Operated Machine or Device-
Attempted
Theft From Motor Vehicle-Attempted
Theft of Motor Vehicle Parts or Accessories-
Attempted
Motor Vehicle Theft-Attempted
Robbery-Attempted
Stolen Property Offenses-Attempted/Completed
Money Laundering*-Attempted
Violation of National Firearm Act of 1934*-
Attempted/Completed
Weapons of Mass Destruction*-
Attempted/Completed
Explosives*-Attempted/Completed
Import Violations*-Attempted/Completed
6/30/2023 2023.0 NIBRS Technical Specification 142
Structure Check Errors
Error
Error Message Error Description
Number
Export Violations*-Attempted/Completed
Federal Liquor Offenses*-Attempted/Completed
Federal Tobacco Offenses*-Attempted/Completed
Wildlife Trafficking*-Attempted/Completed
*Denotes offenses for federal and tribal LEA
reporting only
If Type Property Loss is 2 = Burned, then an
Offense Segment must be submitted in which Data
Element 6 (UCR Offense Code) contains an
offense of 200 = Arson, and Data Element 7
(Offense Attempted/Completed) must be
C = Completed.
If Type Property Loss is 3 = Counterfeiting/Forgery,
then an Offense Segment must be submitted in
which Data Element 6 (UCR Offense Code)
contains an offense of 250 = Counterfeiting/
Forgery, 58B = Export Violations*, and Data
Element 7 (Offense Attempted/Completed) must be
C = Completed.
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 143
Structure Check Errors
Error
Error Message Error Description
Number
If Type Property Loss is 4 = Damaged/Destroyed,
then an Offense segment must be submitted in
which Data Element 6 (UCR Offense Code)
contains an offense of 290 =
Destruction/Damage/Vandalism of Property, and
Data Element 7(Offense Attempted/Completed)
must be C = Completed.
6/30/2023 2023.0 NIBRS Technical Specification 144
Structure Check Errors
Error
Error Message Error Description
Number
If Type Property Loss is 5 = Recovered, then an
Offense Segment must be submitted in which Data
Element 6 (UCR Offense Code) contains a valid
offense for Type Loss 5 = Recovered and Data
Element 7 (Offense Attempted/Completed) must be
C = Completed.
The following completed offenses are valid for
Type Loss 5 = Recovered:
510 = Bribery
220 = Burglary/Breaking & Entering
250 = Counterfeiting/Forgery
270 = Embezzlement
210 = Extortion/Blackmail
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C= Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
100 = Kidnapping/Abduction
23A = Pocket-picking
23B = Purse-Snatching
23C = Shoplifting
23D = Theft From Building
23E = Theft From Coin Operated Machine
23F = Theft From Motor Vehicle
23G = Theft of Motor Vehicle Parts or Accessories
23H = All Other Larceny
58B = Export Violations*
240 = Motor Vehicle Theft
120 = Robbery
280 = Stolen Property Offenses
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 145
Structure Check Errors
Error
Error Message Error Description
Number
If Type Property Loss is 6 = Seized, then an
Offense Segment must be submitted in which Data
Element 6 (UCR Offense Code) contains a valid
offense for Type Loss 6 = Seized and Data
Element 7 (Offense Attempted/Completed) must be
C = Completed.
The following completed offenses are valid for
Type Loss 6 = Seized:
250 = Counterfeiting/Forgery
35A = Drug/Narcotics Violations
35B = Drug Equipment Violations
39A = Betting/Wagering
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment
39D = Sports Tampering
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 146
Structure Check Errors
Error
Error Message Error Description
Number
If Type Property Loss is 7 = Stolen, then an
Offense segment must be submitted in which Data
Element 6 (UCR Offense Code) contains a valid
offense for type loss 7 = Stolen and Data Element
7 (Offense Attempted/Completed) must be C =
Completed.
The following completed offenses are valid for
Type Loss 7 = Stolen:
510 = Bribery
220 = Burglary/Breaking & Entering
270 = Embezzlement
210 = Extortion/Blackmail
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C= Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
26H = Money Laundering*
100 = Kidnapping/Abduction
23A = Pocket-picking
23B = Purse-snatching
23C = Shoplifting
23D = Theft From Building
23E = Theft From Coin Operated Machine
23F = Theft From Motor Vehicle
23G = Theft of Motor Vehicle Parts or Accessories
23H = All Other Larceny
240 = Motor Vehicle Theft
120 = Robbery
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 147
If Type Property Loss is 8 = Unknown, then an
Offense Segment must be submitted in which Data
Element 6 (UCR Offense Code) contains a valid
offense for Type Loss 8 = Unknown and an
applicable Data Element 7 (Offense Attempted/
Completed) must exist for that offense.
The following offense/attempted-completed
combinations are valid for Type Loss 8 = Unknown:
200 = Arson-Attempted
510 = Bribery-Attempted/Completed
220 = Burglary/Breaking & Entering-
Attempted/Completed
250 = Counterfeiting/Forgery-Attempted
290 = Destruction/Damage/Vandalism of Property-
Attempted
35A = Drug/Narcotic Violations-Attempted
35B = Drug Equipment Violations-Attempted
270 = Embezzlement-Attempted
210 = Extortion/Blackmail-Attempted
26A = False Pretenses/Swindle/Confidence Game-
Attempted
26B = Credit Card/Automated Teller Machine
Fraud-Attempted
26C = Impersonation-Attempted
26D = Welfare Fraud-Attempted
26E = Wire Fraud-Attempted
26F = Identity Theft-Attempted
26G = Hacking/Computer Invasion- Attempted
39A = Betting/Wagering-Attempted
39B = Operating/Promoting/Assisting Gambling-
Attempted
39C = Gambling Equipment Violations- Attempted
39D = Sports Tampering-Attempted
100 = Kidnapping/Abduction-Attempted/Completed
23A = Pocket-picking-Attempted
23B = Purse-snatching-Attempted
23C = Shoplifting-Attempted
23D = Theft From Building-Attempted
23E = Theft From Coin-Operated Machine or
Device-Attempted
23F = Theft From Motor Vehicle-Attempted
23G = Theft of Motor Vehicle Parts or Accessories-
Attempted
23H = All Other Larceny-Attempted
240 = Motor Vehicle Theft- Attempted
120 = Robbery-Attempted
280 = Stolen Property Offenses-Attempted
26H = Money Laundering-Attempted
521 = Violation of National Firearms Act of 1934*-
Attempted
522 = Weapons of Mass Destruction*-Attempted
526 = Explosives*-Attempted/Completed
58A = Import Violations*-Attempted/Completed
58B = Export Violations*-Attempted/Completed
6/30/2023 2023.0 NIBRS Technical Specification 148
Structure Check Errors
Error
Error Message Error Description
Number
61A = Federal Liquor Offenses*-
Attempted/Completed
61B = Federal Tobacco Offenses*-
Attempted/Completed
620 = Wildlife Trafficking*-Attempted/Completed
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 16 (Value of Property) for property
classified as 7 = Stolen/Etc. in Data Element 14
(Type Property Loss/Etc.) must be greater than or
equal to the value entered in Data Element 16
(Value of Property) for property classified as
5 = Recovered for the same property specified in
Data Element 15 (Property Description) in an
incident.
RECOVERED PROPERTY VALUE Note: An exception occurs when Data Element 6
084 CANNOT BE GREATER THAN (UCR Offense Code) contains an offense that
THE VALUE WHEN STOLEN allows property to be recovered without first being
stolen in that same incident (i.e.,
250 = Counterfeiting/Forgery and 280 = Stolen
Property Offenses)
Note: This edit also applies when a vehicle was
stolen and the recovered property in Data Element
15 (Property Description) is 38 = Vehicle
Parts/Accessories. The value of recovered parts
cannot exceed the value of stolen vehicles.
Segment Level 4 (Victim Segment) with a data
value in Data Element 24 (Victim Connected to
UCR Offense Code) of a Crime Against Person or
Robbery must contain at least two offender
EACH VICTIM MUST BE
sequence numbers in Data Element 34 (Offender
085 CONNECTED TO AT LEAST TWO
Number to be Related) when there are two or more
OFFENDERS
Segment Level 5 (Offender Segment) records
submitted for the incident, and Data Element 25
(Type of Victim) is I = Individual or L = Law
Enforcement.
Segment Level 6 (Arrestee Segment) and Segment
Level 7 (Group B Arrest Report Segment) cannot
GROUP A AND GROUP B
have the same data values entered in Data
088 CANNOT HAVE SAME
Element 2 (Incident Number) and Data Element 41
IDENTIFIER
(Arrest Transaction Number), respectively, for the
same ORI.
A Segment Level 0 was submitted that had an
ZERO REPORTING MONTH IS invalid reporting month in positions 38 through 39.
090
NOT 01-12 The data entered must be a valid month of 01
through 12.
ZERO-REPORTING YEAR IS A Segment Level 0 was submitted that did not
091
INVALID have four numeric digits in positions 40 through 43.
6/30/2023 2023.0 NIBRS Technical Specification 149
Structure Check Errors
Error
Error Message Error Description
Number
ZERO REPORTING INCIDENT (Incident Number) Zero-Reporting Segment (Level
092
NUMBER MUST BE ALL ZEROS 0) must contain 12 zeros as the Incident Number.
ZERO REPORT MONTH/YEAR IS Zero Report Month and Zero Report Year cannot
093 PRIOR TO AGENCY precede the month and year in the date the LEA
CONVERSION TO THE NIBRS converted to the NIBRS.
A Segment Level 0 was submitted with a month
ZERO REPORT MONTH/YEAR and year entered into positions 38 through 43 that
094 EXCEEDED MONTH/YEAR OF was later than the Month of Electronic submission
SUBMISSION and Year of Electronic submission entered into
positions 7 through 12.
An instruction to delete data in NIBRS before the
PRE-NIBRS SEGMENTS CANNOT agency transitioned to NIBRS, which is not
095
BE DELETED IN THIS WAY allowed.
The combined Zero Report Month and Zero Report
Year cannot be on or after the date an LEA is
ZERO REPORT MONTH & ZERO placed in Covered-by Status. When Zero Report
REPORT YEAR CANNOT BE ON data are received for a LEA in Covered-by Status,
096 OR AFTER DATE AGENCY IS the FBI will remove the agency from Covered-by
PLACED ON COVERED-BY Status, process the submission, and notify the
STATUS agency. Additionally, adjustments to previously
submitted data from an agency now in Covered-by
Status will be processed and no error generated.
THE ORI INFORMATION IS
The ORI exists in the reference table for a different
931 DUPLICATED IN THE
agency. Verify that the ORI is accurate.
REFERENCE DATA
INVALID ORI FORMAT - THE ORI The ORI submitted was not found in the reference
932 WAS NOT FOUND IN THE data table. Verify that the submitting agency is
REFERENCE DATA providing an accurate ORI for the data submission.
The ORI submitted is currently in a Covered-by
status. Verify that the information being provided is
THE ORI IS COVERED BY
933 accurate and/or to ensure that the submitting
ANOTHER AGENCY
agency is now providing its own information and is
no longer in Covered-by status.
THE ORI IS MARKED AS
The ORI submitted has been marked for deletion.
934 DELETED IN THE REFERENCE
Verification is needed to ensure this is accurate.
DATA
Data was submitted by an agency that does not
have a NIBRS certification date set in the FBI
database. Agencies and/or state programs must
NIBRS CERTIFICATION DATE
935 first pass a testing phase to achieve NIBRS
DOES NOT EXIST
certification and then the FBI reference data
administrator can enter a certification date into the
system.
6/30/2023 2023.0 NIBRS Technical Specification 150
Structure Check Errors
Error
Error Message Error Description
Number
An incident has been submitted with an incident
date that predates the agency's NIBRS start date.
Pre-NIBRS incidents are submitted to add
additional information that occurred after the
NIBRS start date for crimes that occurred when the
agency was still submitting Summary data. For
example, a burglary was submitted via SRS in
937 PRE-NIBRS INCIDENT RECEIVED January. The agency started submitting via NIBRS
February 1st. An offender was arrested for the
January burglary in February. The agency will send
a NIBRS incident with the new information of an
arrest. We will only count the arrest in the
database, since the offense itself is Pre-NIBRS and
would have previously been reported via a
Summary submittal.
Action Type of “A” is used, and there are multiple
938 MULTIPLE INCIDENTS ON FILE incidents on file for the same agency/incident
number.
Action Type of “M” is used for a Group B Arrest
CANNOT MODIFY PRE-NIBRS
939 and the Arrest Date is before the agency
GROUP B INCIDENT
transitioned to NIBRS.
Agency is trying to add an exceptional clearance
EXCEPTIONAL CLEARANCE
940 and the incident has already been exceptionally
ALREADY ON FILE
cleared either by circumstances or arrest.
Agency is trying to perform any insert or replace
WEB SERVICE SUBMISSION action for a Group A/Group B Incident while an
941
ALREADY IN PROCESS action is currently pending for the same
agency/incident number in web services.
INVALID ORI FORMAT - NOT A Data Element 1 (ORI) and Data Element 25C
952 VALID ORI - NOT IN UCR ORI (Officer–ORI Other Jurisdiction) must be a valid
FILE nine-character NCIC ORI.
5.2.2 Administrative Segment Errors
Table 5-3 Administrative Segment Errors
Administrative Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element is
MUST BE PRESENT—
101 mandatory or when the conditions are met for
MANDATORY FIELD
data that must be entered into a conditionally
mandatory field.
The referenced data element must contain a valid
INVALID DATA VALUE-NOT ON
104 data value when it is entered; blank is permissible
FBI VALIDATION TABLE
on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 151
Administrative Segment Errors
Error
Error Message Error Description
Number
The data element in error contains a date that is
not entered correctly. Each component of the date
must be valid; that is, months must be 01 through
12, days must be 01 through 31, and year must
105 INVALID DATA VALUE FOR DATE
include the century (i.e., 19xx, 20xx). In addition,
days cannot exceed maximum for the month (e.g.,
June cannot have 31days). Also, the date cannot
exceed the current date.
(Incident Hour) For offenses of 09A, 13A, 13B and
13C only–When Data Element 25 (Type of Victim)
is L = Law Enforcement Officer, then Data
106 INVALID DATA VALUE FOR HOUR
Element 3 (Incident Date/Hour) must be populated
with a valid hour (00-23). Incident Hour Unknown
(Blank) is not a valid entry.
(Incident Number) Must be blank right-fill if under
CANNOT HAVE EMBEDDED
12 characters in length. Cannot have embedded
115 BLANKS BETWEEN FIRST AND
blanks between the first and last characters
LAST NON-BLANK CHARACTERS
entered.
MUST BE LEFT JUSTIFIED (Incident Number) must be left-justified with blank
116 BLANK DETECTED IN FIRST right-fill. Since the number is less than 12
POSITION characters, it must begin in position 1.
Must contain a valid character combination of the
following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
117 OTHER THAN A–Z, 0–9, AND/OR • 0–9
HYPHEN, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
The UCR Program has determined that an ORI
DATE CANNOT BE ON OR AFTER will no longer be submitting data to the FBI as of
118
THE INACTIVE DATE OF THE ORI an inactive date. The UCR Program will not
accept data from the ORI after this date.
6/30/2023 2023.0 NIBRS Technical Specification 152
Administrative Segment Errors
Error
Error Message Error Description
Number
Data Element 2A (Cargo Theft) must be blank,
unless Data Element 6 (UCR Offense Code)
includes at least one of the following:
120 = Robbery
210 = Extortion/Blackmail
220 = Burglary/Breaking & Entering
23D = Theft From Building
23F = Theft From Motor Vehicle
CARGO THEFT DATA CAN ONLY 23H = All Other Larceny
119 BE SUBMITTED FOR SPECIFIC 240 = Motor Vehicle Theft
OFFENSES 26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C = Impersonation
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
270 = Embezzlement
510 = Bribery
(Cargo Theft) must be populated with a Y = Yes or
N = No only when Data Element 6 (UCR Offense
Code) includes at least one of the following:
120 = Robbery
210 = Extortion/Blackmail
220 = Burglary/Breaking & Entering
23D = Theft From Building
23F = Theft From Motor Vehicle
CARGO THEFT VALUE 23H = All Other Larceny
122 REQUIRED WITH SPECIFIC 240 = Motor Vehicle Theft
OFFENSES
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C = Impersonation
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
270 = Embezzlement
510 = Bribery
This field must be blank if the Incident Date is
known. If the Incident Date is unknown, then the
REPORT INDICATOR MUST BE
151 Report Date would be entered instead and must
BLANK OR R
be indicated with an “R” in the Report Indicator
field within the Administrative Segment.
6/30/2023 2023.0 NIBRS Technical Specification 153
Administrative Segment Errors
Error
Error Message Error Description
Number
If Hour is entered within Data Element 3 (Incident
Date/Hour), it must be 00 through 23. If
00 = Midnight is entered, be careful that the
Incident Date is entered as if the time was 1
minute past midnight.
152 INVALID HOUR ENTRY Note: When an incident occurs exactly at
midnight, Data Element 3 (Incident Date) would
be entered as if the time is 1 minute past
midnight. For example, when a crime occurred
exactly at midnight on Thursday, Friday’s date
would be entered.
VALUE ENTERED CONFLICTS
Data Element 4 (Cleared Exceptionally) cannot be
WITH PRESENCE OF AN ENTRY
153 N = Not Applicable if Data Element 5 (Exceptional
IN EXCEPTIONAL CLEARANCE
Clearance Date) is entered.
DATE
CLEARANCE DATE PREDATES Data Element 5 (Exceptional Clearance Date) is
155
INCIDENT DATE earlier than Data Element 3 (Incident Date/Hour).
Data Element 5 (Exceptional Clearance Date)
AN ENTRY MUST BE MADE
must be present if the case was cleared
WHEN CLEARED
156 exceptionally. Data Element 4 (Cleared
EXCEPTIONALLY HAS ENTRIES
Exceptionally) has an entry of A through E;
OF A-E
therefore, the date must also be entered.
Data Element 3 (Incident Date/Hour) The date
INCIDENT DATE CANNOT BE cannot be later than the year and month the
170 AFTER MONTH AND YEAR OF electronic submission represents. For example,
ELECTRONIC SUBMISSION the May 1999 electronic submission cannot
contain incidents happening after this date.
Data Element 3 (Incident Date) cannot be earlier
INCIDENT DATE/HOUR FOR I
than 01/01/1991. This edit will preclude dates that
172 RECORDS CANNOT PREDATE
are obviously incorrect since the FBI began
01/01/1991
accepting NIBRS data on this date.
The electronic submission control date (positions
CANNOT CALCULATE BASE 7 through 12, month and year) and Data Element
175
DATE FROM INCIDENT DATE 3 (Incident Date/Hour) must both be valid dates
for calculating timeframes.
Segment Length for the Administrative Segment
(Level 1) must be 87 characters (not reporting
Cargo Theft) or 88 characters (reporting Cargo
Theft). Once an agency begins participation in
THIS ADMINISTRATIVE reporting Cargo Theft, indicated by 0088 in the
178 SEGMENT HAS A CONFLICTING RDW, then all future Administrative Segments
LENGTH within that ORI must be formatted using 0088.
Note: The only exception would be that data prior
to the agency starting to report Cargo Theft could
be submitted with the original 0087 RDW.
6/30/2023 2023.0 NIBRS Technical Specification 154
Administrative Segment Errors
Error
Error Message Error Description
Number
Data Element 3 (Incident Date) is missing for a
MISSING INCIDENT DATE FOR Group A Incident Report with a Segment Action
197
DELETE Type of D = Delete; must be populated with a
valid data value and cannot be blank.
Data Element 3 (Incident Date) is missing for a
MISSING INCIDENT DATE FOR
Group A Incident Report with a Segment Action
DELETE - INCIDENT NUMBER
Type of D = Delete; at least one Group A Incident
198 MATCHES GROUP A INCIDENT
Report is on file that matches Data Element 2
REPORTS WITH INCIDENT DATE
(Incident Number) with an Incident Date outside
OUTSIDE TWO YEAR WINDOW
the two year window.
Data Element 3 (Incident Date) is missing for a
MISSING INCIDENT DATE FOR Group A Incident Report with a Segment Action
DELETE - INCIDENT NUMBER Type of D = Delete; must be populated with a
199
MATCHES MULTIPLE GROUP A valid data value and cannot be blank. Incident
INCIDENT REPORTS Number matches multiple Group A Incident
Reports.
5.2.3 Offense Segment Errors
Table 5-4 Offense Segment Errors
Offense Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element is
MUST BE PRESENT—
201 mandatory or when the conditions are met for
MANDATORY FIELD
data that must be entered into a conditionally
mandatory field.
Data Element 10 (Number of Premises Entered) is
202 CONTAINS NONNUMERIC ENTRY
not a numeric entry of 01 through 99.
The referenced data element must contain a valid
204 INVALID DATA VALUE data value when it is entered; blank is permissible
on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 155
Offense Segment Errors
Error
Error Message Error Description
Number
Data Element 9 (Location Type) of 58 =
Cyberspace can only be entered when Data
Element 6 Offense Code is one of the violations
listed below:
210 = Extortion/Blackmail
250 = Counterfeiting/Forgery
270 = Embezzlement
280 = Stolen Property Offenses
290 = Destruction/Damage/Vandalism of Property
370 = Pornography/Obscene Material
510 = Bribery
26A = False Pretenses/Swindle/Confidence Game
26B = Credit Card/Automated Teller Machine
Fraud
26C = Impersonation
26D = Welfare Fraud
26E = Wire Fraud
26F = Identity Theft
ERROR - INVALID OFFENSE 26G = Hacking/Computer Invasion
205 CODE FOR LOCATION TYPE 26H = Money Laundering*
CYBERSPACE 39A = Betting/Wagering
39B = Operating/Promoting/Assisting Gambling
39C = Gambling Equipment Violations
13C = Intimidation
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
40A = Prostitution
40B = Assisting or Promoting Prostitution
40C = Purchasing Prostitution
101 = Treason*
103 = Espionage*
*Denotes offenses for federal and tribal LEA
reporting only
The referenced data element in error is one that
ERROR - DUPLICATE VALUE = contains multiple data values. When more than
206
[value] one code is entered, none can be duplicate
codes.
6/30/2023 2023.0 NIBRS Technical Specification 156
Offense Segment Errors
Error
Error Message Error Description
Number
The data element in error can have multiple data
values and was entered with multiple values.
However, mutually exclusive values cannot be
entered with any other data value. Refer to
individual data elements for mutually exclusive
data values.
ERROR - MUTUALLY EXCLUSIVE • 207A ERROR MUTUALLY EXCLUSIVE
207 VALUE - SUSPECTED OF USING
VALUE = [value]
• 207B ERROR MUTUALLY EXCLUSIVE
VALUE - BIAS MOTIVATION
• 207C ERROR MUTUALLY EXCLUSIVE
VALUE - CRIMINAL ACTIVITY / GANG
INFORMATION
• 207D ERROR MUTUALLY EXCLUSIVE
VALUE - WEAPON CODE
CANNOT CONTAIN EMBEDDED Must be blank right-fill if under 12 characters in
215 BLANKS BETWEEN FIRST AND length. Cannot have embedded blanks between
LAST NON BLANK CHARACTERS the first and last characters entered.
MUST BE LEFT-JUSTIFIED–
Must be left-justified with blank right-fill if under 12
216 BLANK DETECTED IN FIRST
characters in length.
POSITION
Must contain a valid character combination of the
following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
217 OTHER THAN A–Z, 0–9, AND/OR • 0–9
HYPHEN, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
6/30/2023 2023.0 NIBRS Technical Specification 157
Offense Segment Errors
Error
Error Message Error Description
Number
Data Element 12 (Type Criminal Activity/Gang
Information) Type Criminal Activity codes of B, C,
D, E, O, P, T, or U can only be entered when the
UCR Offense Code is:
250 = Counterfeiting/Forgery
280 = Stolen Property Offenses
30C = Smuggling Aliens*
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
39C = Gambling Equipment Violations
49A = Harboring Escapee/Concealing from
Arrest*
370 = Pornography/Obscene Material
520 = Weapon Law Violations
521 = Violation of National Firearm Act 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
DATA CAN ONLY BE ENTERED 620 = Wildlife Trafficking*
219
FOR SPECIFIC OFFENSES *Denotes offenses for federal and tribal LEA
reporting only
(Type Criminal Activity/Gang Information) Gang
Information codes of J, G, and N can only be
entered when the UCR Offense Code is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
11D = Fondling
120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
(Type Criminal Activity/Gang Information) Criminal
Activity codes of A, F, I, and S can only be
entered when the UCR Offense Code is:
720 = Animal Cruelty
6/30/2023 2023.0 NIBRS Technical Specification 158
Offense Segment Errors
Error
Error Message Error Description
Number
Data Element 12 (Type Criminal Activity/Gang
Information) must be populated with a valid data
value and cannot be blank when Data Element 6
(UCR Offense Code) is:
250 = Counterfeiting/Forgery
280 = Stolen Property Offenses
30C = Smuggling Aliens*
35A = Drug/Narcotic Violations
35B = Drug Equipment Violations
39C = Gambling Equipment Violations
49A = Harboring Escapee/Concealing from
DATA MUST BE ENTERED FOR Arrest*
220 370 = Pornography/Obscene Material
SPECIFIC OFFENSES
520 = Weapon Law Violations
521 = Violation of National Firearm Act 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
720 = Animal Cruelty
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 13 (Type Weapon/Force Involved)
must be populated with a valid data value and
cannot be blank when Data Element 6 (UCR
Offense Code) is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
09C = Justifiable Homicide
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
DATA MUST BE ENTERED FOR 11D = Fondling
221
SPECIFIC OFFENSES 120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
*Denote offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 159
Offense Segment Errors
Error
Error Message Error Description
Number
Data Element 13 (Type of Weapon/Force
Involved) Type of Weapon/Force Involved can
only be entered when the UCR Offense Code is:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
09C = Justifiable Homicide
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
DATA CAN ONLY BE ENTERED 11D = Fondling
222 120 = Robbery
FOR SPECIFIC OFFENSES
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
520 = Weapon Law Violations
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
*Denote offenses for federal and tribal LEA
reporting only
(UCR Offense Code)The following values for Data
Element 6 (UCR Offense Code) are only valid for
use by federal and tribal agencies:
26H = Money Laundering*
101 = Treason*
103 = Espionage*
30A = Illegal Entry into the United States*
30B = False Citizenship*
30C = Smuggling Aliens*
30D = Re-entry after Deportation*
360 = Failure to Register as a Sex Offender*
OFFENSE CODE CAN ONLY BE 49A = Harboring Escapee/Concealing from Arrest
250 USED BY FEDERAL AGENCIES
49B = Flight to Avoid Prosecution*
AND TRIBAL AGENCIES
49C = Flight to Avoid Deportation*
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 160
Offense Segment Errors
Error
Error Message Error Description
Number
(Offense Attempted/Completed) Must be a valid
251 INVALID CODE
code of A = Attempted or C = Completed.
When Data Element 10 (Number of Premises
OFFENSE CODE MUST BE 220 Entered) is entered, Data Element 9 (Location
WITH A LOCATION TYPE OF 14 Type) must be 14 = Hotel/Motel/Etc. or
252
OR 19 FOR DATA TO BE 19 = Rental Storage Facility, and Data Element 6
ENTERED (UCR Offense Code) must be
220 = Burglary/Breaking & Entering.
Data Element 11 (Method of Entry) was not
MUST BE PRESENT WHEN entered; it must be entered when UCR Offense
253
OFFENSE CODE IS 220 Code of 220 = Burglary/Breaking & Entering has
been entered.
Data Element 11 (Method of Entry) only applies to
UCR Offense Code of 220 = Burglary/Breaking &
MUST BE BLANK WHEN
254 Entering. Since a burglary offense was not
OFFENSE IS OTHER THAN 220
entered, the Method of Entry should not have
been entered.
AUTOMATIC INDICATOR MUST
255 Must be A = Automatic or blank = Not Automatic
BE BLANK OR A
Code must be C = Completed if Data Element 6
OFFENSE CODES OF 09A, 09B, (UCR Offense Code) is an Assault, Homicide, or
256 09C, 13A, 13B, 13C, AND 360 360 = Failure to Register as a Sex Offender*.
MUST HAVE ENTRY OF C *Denotes offenses for federal and tribal LEA
reporting only
Data Element 10 (Number of Premises Entered)
MUST BE PRESENT WITH AN must be entered if offense code is
257 OFFENSE CODE OF 220 AND A 220 = Burglary/Breaking & Entering and if Data
LOCATION TYPE OF 14 OR 19 Element 9 (Location Type) contains 14 = Hotel/
Motel/Etc. or 19 = Rental Storage Facility.
In Data Element 13 (Type of Weapon/Force
Involved), A = Automatic is the third character of
code. It is valid only with the following codes:
11 = Firearm (Type Not Stated)
WEAPON TYPE MUST = 11, 12, 12 = Handgun
258 13, 14, OR 15 FOR AN A IN THE 13 = Rifle
AUTO INDICATOR 14 = Shotgun
15 = Other Firearm
A weapon code other than those mentioned was
entered with the automatic indicator. An automatic
weapon is, by definition, a firearm.
When a Group A Incident Report is submitted, the
individual segments comprising the incident
cannot contain duplicates. In this case, two
262 DUPLICATE OFFENSE SEGMENT
Offense Segments were submitted having the
same offense in Data Element 6 (UCR Offense
Code).
6/30/2023 2023.0 NIBRS Technical Specification 161
Offense Segment Errors
Error
Error Message Error Description
Number
Offenses may be submitted only 10 times for each
CANNOT HAVE MORE THAN 10
263 Group A Incident Report; 10 offense codes are
OFFENSES
allowed for each incident.
Data Element 6 (UCR Offense Code) must be a
GROUP A OFFENSE CANNOT
264 Group A UCR Offense Code, not a Group B
CONTAIN A GROUP B OFFENSE
Offense Code.
If an Offense Segment (Level 2) was submitted for
13B = Simple Assault, Data Element 13 (Type
Weapon/Force Involved) can only have codes of
INVALID WEAPON WITH AN
265 40 = Personal Weapons, 90 = Other,
OFFENSE OF 13B
95 = Unknown, and 99 = None. All other codes
are not valid because they do not relate to a
simple assault.
When a Justifiable Homicide is reported, no other
NO OTHER OFFENSE CAN BE
offense may be reported in the Group A Incident
266 SUBMITTED WITH JUSTIFIABLE
Report. These should be submitted on another
HOMICIDE
Group A Incident Report.
If a homicide offense is submitted, Data Element
INVALID WEAPON TYPE FOR 13 (Type Weapon/Force Involved) cannot have
267
HOMICIDE OFFENSES 99 = None. Some type of weapon/force must be
used in a homicide offense.
Data Element 6 (UCR Offense Code) is a
(23A-23H) = Larceny/Theft Offenses and a
Property Segment exists with Data Element 14
(Type Property Loss/Etc.) of 7 = Stolen/Etc. and
Data Element 15 (Property Description) of
LARCENY OFFENSE CANNOT
03 = Automobiles, 05 = Buses, 24 = Other Motor
HAVE A MOTOR VEHICLE
268 Vehicles, 28 = Recreational Vehicles, or
PROPERTY DESCRIPTION
37 = Trucks; then the incident must contain
ENTERED
another Offense Segment with Data Element 6
(UCR Offense Code) containing a Crime Against
Property other than a Larceny/Theft offense (refer
to Appendix E: Mandatories for each Crime
Against Property offense).
If Data Element 6 (UCR Offense Code) is
POSSIBLE CLASSIFICATION 13B = Simple Assault and the weapon involved is
ERROR OF AGGRAVATED 11 = Firearm, 12 = Handgun, 13 = Rifle,
269
ASSAULT 13A CODED AS 14 = Shotgun, or 15 = Other Firearm, then the
SIMPLE 13B offense should instead be classified as
13A = Aggravated Assault.
JUSTIFIABLE HOMICIDE MUST
Must be 88 = None when Data Element 6 (UCR
270 BE CODED AS NON BIAS
Offense Code) is 09C = Justifiable Homicide.
MOTIVATED
6/30/2023 2023.0 NIBRS Technical Specification 162
Offense Segment Errors
Error
Error Message Error Description
Number
Segment Length for the Offense Segment (Level
2) must be 63 characters (reporting only Bias
Motivation #1) or 71 characters (reporting Bias
Motivations #2–#5). Once an agency begins
participation in reporting Bias Motivations #2-#5,
THIS OFFENSE SEGMENT HAS A indicated by 0071 in the RDW, then all future
284 Offense Segments within that ORI must be
CONFLICTING LENGTH
formatted using 0071.
Note: The only exception would be that data prior
to the agency starting to report Bias Motivations
#2-#5 could be submitted with the original 0063
RDW.
5.2.4 Property Segment Errors
Table 5-5 Property Segment Errors
Property Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element is
MUST BE PRESENT—
301 mandatory or when the conditions are met for data
MANDATORY FIELD
that must be entered into a conditionally mandatory
field.
Must be numeric entry with zero left-fill. Refer to
302 CONTAINS NONNUMERIC ENTRY individual data element for specific formatting
instructions.
The referenced data element must contain a valid
304 INVALID DATA VALUE data value when it is entered; Blank is permissible
on nonmandatory fields
Each component of the date must be valid; that is,
months must be 01 through 12, days must be 01
through 31, and year must include the century (i.e.,
19xx, 20xx). In addition, days cannot exceed
maximum for the month (e.g., June cannot have 31
days). The date cannot be later than that entered
305 DATE RECOVERED IS INVALID within the Month of Electronic submission and Year
of Electronic submission fields on the data record.
For example, if Month of Electronic Submission
and Year of Electronic submission are 06/1999, the
recovered date cannot contain any date
07/01/1999 or later. Cannot be earlier than Data
Element 3 (Incident Date/Hour).
The referenced data element in error is one that
ERROR-DUPLICATE DATA contains multiple data values. When more than
306 one code is entered, none can be duplicate codes.
VALUE
Refer to individual data elements for exceptions.
6/30/2023 2023.0 NIBRS Technical Specification 163
Property Segment Errors
Error
Error Message Error Description
Number
Data Element 2 (Incident Number) Must be blank
CANNOT HAVE EMBEDDED
right-fill if under 12 characters in length. Cannot
315 BLANKS BETWEEN FIRST AND
have embedded blanks between the first and last
LAST NON-BLANK CHARACTERS
characters entered.
MUST BE LEFT-JUSTIFIED– Data Element 2 (Incident Number) Must be left-
316 BLANK DETECTED IN FIRST justified with blank right-fill if under 12 characters in
POSITION length.
Must contain a valid character combination of the
following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
317 OTHER THAN A–Z, 0–9, AND/OR • 0–9
HYPHEN, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not
valid.
Data Element 16 (Value of Property) cannot be
zero unless Data Element 15 (Property
Description) is:
Mandatory zero
09=Credit/Debit Cards
22=Nonnegotiable Instruments
PROPERTY VALUE OF ZERO IS
351 48=Documents–Personal or Business
NOT ALLOWED
65=Identity Documents
66=Identity–Intangible
Optional zero
77=Other
99=(blank)–this data value is not currently
used by the FBI.
6/30/2023 2023.0 NIBRS Technical Specification 164
Property Segment Errors
Error
Error Message Error Description
Number
(Type Property Loss/Etc.) Referenced data
elements must be blank when one of the following
criteria is met:
1) If Data Element 14 (Type Property Loss/Etc.)
is 8 = Unknown, then Data Elements 15
through 22 must be blank.
2) If Data Element 14 (Type Property Loss/Etc.)
is 1 = None and Data Element 6 (UCR Offense
Code) is 35A = Drug/ Narcotic Violations, then
Data Elements 15 through 19 and 21 through
DATA ELEMENTS 15 - 22 MUST 22 must be blank, and Data Element 20
352 BE BLANK WHEN PROPERTY (Suspected Drug Type) must be entered.
LOSS CODE=1 OR 8
Data Element 20 Exception-The incident
consists of multiple offense segments
where at least one offense code is not
35A = Drug/Narcotic Violations and
requires property to be entered.
3) If Data Element 14 (Type Property Loss/Etc.)
is 1 = None and the incident has no Offense
Segments with a Data Element 6 (UCR
Offense Code) of 35A = Drug/ Narcotic
Violations, then Data Elements 15 through 22
must be blank.
Data Element 15 (Property Description) is 88 =
PENDING INVENTORY MUST
353 Pending Inventory, but Data Element 16 (Value of
HAVE PROPERTY VALUE OF 1
Property) is not $1.
VALUE OF PROPERTY ENTERED Data Element 16 (Value of Property) contains a
354 WITHOUT PROPERTY value, but Data Element 15 (Property Description)
DESCRIPTION was not entered.
PROPERTY LOSS CODE (14) Data Element 14 (Type Property Loss/Etc.) must
355 MUST=5 (RECOVERED) FOR be 5 = Recovered for Data Element 17 (Date
DATA TO BE ENTERED Recovered) to be entered.
PROPERTY DESCRIPTION (15) Data Element 17 (Date Recovered) was entered,
356 AND VALUE (16) MUST BOTH but Data Elements 15 (Property Description)
EXIST IF DATA ARE PRESENT and/or 16 (Value of Property) were not entered.
Data Element 18 (Number of Stolen Motor
Vehicles) was entered. However, Data Element 14
STOLEN VEHICLE NUMBER (Type Property Loss/Etc.) 7 = Stolen/Etc. was not
357 CANNOT BE ENTERED WITHOUT entered, and/or Data Element 6 (UCR Offense
MOTOR VEHICLE OFFENSE Code) of 240 = Motor Vehicle Theft was not
entered, and/or Data Element 7 (Offense
Attempted/Completed) was A = Attempted.
Entry must be made for Data Element 18 (Number
of Stolen Motor Vehicles) when Data Element 6
DATA MUST EXIST WITH AN
(UCR Offense Code) is 240 = Motor Vehicle Theft,
358 OFFENSE CODE OF 240 AND A
Data Element 7 (Offense Attempted/Completed) is
PROPERTY LOSS OF 7
C = Completed, and Data Element 14 (Type
Property Loss/Etc.) is 7 = Stolen/Etc.
6/30/2023 2023.0 NIBRS Technical Specification 165
Property Segment Errors
Error
Error Message Error Description
Number
Data Element 15 (Property Description) must be
one of the following:
03 = Automobiles
05 = Buses
24 = Other Motor Vehicles
ALL NONVEHICULAR PROPERTY 28 = Recreational Vehicles
359
DESCRIPTIONS WERE ENTERED 37 = Trucks
When Data Element 6 (UCR Offense Code) is
240 = Motor Vehicle Theft, and Data Element 18
(Number of Stolen Motor Vehicles) or Data
Element 19 (Number of Recovered Motor Vehicles)
contains a data value of 01-99.
Data Element 19 (Number of Recovered Motor
Vehicles) was entered. However, Data Element 14
(Type Property Loss/Etc.) 5 = Recovered was not
entered, and/or Data Element 6 (UCR Offense
Code) of 240 = Motor Vehicle Theft was not
entered, and/or Data Element 7 (Offense
Attempted/Completed) was A = Attempted.
PROPERTY LOSS (14) MUST BE
360 5 WITH AN OFFENSE CODE OF The exception to this rule is when recovered
240 FOR DATA TO BE ENTERED property is reported for a pre-NIBRS incident. In
this case, Segment Level 3 (Property Segment) will
contain I = Incident Report, but the data value in
Data Element 2 (Incident Number) will not match
an incident already on file in the national UCR
database. The segment will be processed but used
only for SRS purposes and will not be included in
the agency’s NIBRS figures.
Entry must be made for Data Element 19 (Number
of Recovered Motor Vehicles) When Data Element
DATA MUST EXIST WITH AN 6 (UCR Offense Code) is 240 = Motor Vehicle
361 OFFENSE CODE OF 240 AND A Theft, Data Element 7 (Offense Attempted/
PROPERTYLOSS OF 5 Completed) is C = Completed, Data Element 14
(Type Property Loss/Etc.) is 5 = Recovered, and
vehicle codes were recovered.
Since X = Over 3 Drug Types was entered in Data
TWO OTHER CODES MUST BE
Element 20 (Suspected Drug Type), two other
362 ENTERED WHEN AN X IS
codes must also be entered. Less than three codes
PRESENT
are present.
DRUG QUANTITY Since Data Element 20 (Suspected Drug Type)
MEASUREMENT MUST BE contains X=Over 3 Drug Types, Data Element 21
363
BLANK WITH OVER 3 DRUG (Estimated Quantity) and 22 (Type Measurement)
TYPES must be blank.
6/30/2023 2023.0 NIBRS Technical Specification 166
Property Segment Errors
Error
Error Message Error Description
Number
When Data Element 6 (UCR Offense Code) is 35A
= Drug/Narcotic Violations, Data Element 14 (Type
Property Loss/Etc.) is 6 = Seized, Data Element 15
WITH DATA ENTERED BOTH (Property Description) is 10 = Drugs, and Data
QUANTITY (21) AND Element 20 (Suspected Drug Type) is entered,
364
MEASUREMENT (22) MUST BE both Data Element 21 (Estimated Drug Quantity)
PRESENT and Data Element 22 (Type Drug Measurement)
must also be entered, unless Data Element 20
(Suspected Drug Type) contains X = Over 3 Drug
Types.
Data Element 20 (Suspected Drug Type) was
entered, but one or more required data elements
were not entered. Data Element 6 (UCR Offense
OFFENSE=35A AND PROPERTY
Code) must be 35A = Drug/Narcotic Violations,
365 LOSS=6 AND DESCRIPTION=10
Data Element 14 (Type Property Loss/Etc.) must
MUST EXIST
be 6 = Seized, or 1 = None and if seized, Data
Element 15 (Property Description) must be
10 = Drugs/Narcotics.
Data Element 21 (Estimated Quantity) was
WITH DATA ENTERED BOTH
entered, but Data Elements 20 (Suspected Drug
366 TYPE (20) AND MEASUREMENT
Type) and/or 22 (Type Measurement) were not
(22) MUST BE PRESENT
entered; both must be entered.
Data Element 22 (Type Measurement) was
entered with NP = Number of Plants in
combination with an illogical drug type. Based
upon the various ways a drug can be measured,
very few edits can be done to check for illogical
combinations of drug type and measurement. The
only restriction will be to limit NP = Number of
DRUG TYPE MUST BE E, G, OR K Plants to the following drugs:
367
FOR A VALUE OF NP DRUG MEASUREMENT
E = Marijuana NP
G = Opium NP
K = Other Hallucinogens NP
All other Data Element 22 (Type Measurement)
codes are applicable to any Data Element 20
(Suspected Drug Type) code.
Data Element 22 (Type Measurement) was
WITH DATA ENTERED BOTH
entered, but Data Elements 20 (Suspected Drug
368 TYPE (20) AND QUANTITY (21)
Type) and/or 21 (Estimated Quantity) were not
MUST BE PRESENT
entered; both must be entered.
If Data Element 14 (Type Property/Loss/Etc.) is 2 =
Burned, 3 = Counterfeited/ Forged, 4 =
DATA ELEMENTS 15-22 WERE
Destroyed/Damaged/Vandalized, 5 = Recovered, 6
372 ALL BLANK WITH THIS
= Seized, or 7 = Stolen/Etc., Data Elements 15
PROPERTY LOSS CODE
through 22 must have applicable entries in the
segment.
6/30/2023 2023.0 NIBRS Technical Specification 167
Property Segment Errors
Error
Error Message Error Description
Number
At least one Data Element 15 (Property
Description) code must be entered when Data
Element 14 (Type Property Loss/Etc.) contains
Property Segment(s) for:
MANDATORY FIELD WITH THE
375 PROPERTY LOSS CODE 2=Burned
ENTERED 3=Counterfeited/Forged
4=Destroyed/Damaged/Vandalized
5=Recovered
6=Seized
7=Stolen/Etc.
When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot
DUPLICATE TYPE PROPERTY
contain duplicates. Example, two property
376 LOSS SEGMENTS ARE NOT
segments cannot be submitted having the same
ALLOWED
entry in Data Element 14 (Type Property
Loss/Etc.).
Segment Level 3 (Property Segment) cannot be
submitted with 10=Drugs/Narcotics in Data
DRUG/NARCOTIC VIOLATIONS
Element 15 (Property Description) and blanks in
382 OFFENSE MUST BE SUBMITTED
Data Element 16 (Value of Property) unless Data
FOR SEIZED DRUGS
Element 6 (UCR Offense Code) is
35A=Drug/Narcotic Violations.
Data Element 16 (Value of Property) must be blank
PROPERTY VALUE MUST BE
when Data Element 15 (Property Description) code
383 BLANK FOR 35A (SINGLE
is 10=Drugs/Narcotics and the only offense
OFFENSE)
submitted is a 35A=Drug/Narcotic Violations.
Data Element 21 (Estimated Drug Quantity) must
be 000000001000=None (i.e., 1) when Data
DRUG QUANTITY MUST BE Element 22 (Type Drug Measurement) is XX=Not
NONE WHEN DRUG Reported indicating the drugs were sent to a
384 laboratory for analysis.
MEASUREMENT IS NOT
REPORTED When the LEA receives the drug analysis, it should
update Data Element 21 and Data Element 22 with
the correct data values.
1) If 35A = Drug/Narcotic Violation Offense exists
without a 35B = Drug Equipment Violation
WITH A PROPERTY LOSS=6 AND Offense and a Property Type of 6 = Seized
ONLY OFFENSE 35A CANNOT and Property Description of 11 and no other
HAVE DESCRIPTION 11 or WITH crimes requiring a Property Segment exist.
387
A PROPERTY LOSS=6 AND ONLY 2) If 35B = Drug Equipment Violation Offense
OFFENSE 35B CANNOT HAVE exists without 35A = Drug/Narcotic Violation
DESCRIPTION 10 Offense and a Property Type of 6 = Seized
and Property Description of 10 and no other
crimes requiring a Property Segment exist.
6/30/2023 2023.0 NIBRS Technical Specification 168
Property Segment Errors
Error
Error Message Error Description
Number
More than one vehicle code was entered in Data
Element 15 (Property Description), but the number
stolen in Data Element 18 (Number of Stolen Motor
Vehicles) is less than this number. For example, if
NUMBER STOLEN IS LESS THAN vehicle codes of 03 = Automobiles and 05 = Buses
388 were entered as being stolen, then the number
NUMBER OF VEHICLE CODES
stolen must be at least 2, unless the number stolen
was 00 = Unknown.
The exception to this rule is when 00 = Unknown is
entered in Data Element 18.
More than one vehicle code was entered in Data
Element 15 (Property Description), but the number
recovered in Data Element 19 (Number of
Recovered Motor Vehicles) was less than this
NUMBER RECOVERED IS LESS number. For example, if vehicle codes of
389 THAN NUMBER OF VEHICLE 03 = Automobiles and 05 = Buses were entered as
CODES being recovered, then the number recovered must
be at least 2, unless the number recovered was
00 = Unknown.
The exception to this rule is when 00 = Unknown is
entered in Data Element 19.
6/30/2023 2023.0 NIBRS Technical Specification 169
Property Segment Errors
Error
Error Message Error Description
Number
(Property Description) must contain a data value
that is logical for one or more of the Crime Against
Property offenses entered in Data Element 6 (UCR
Offense Code). See Table 3-28: Illogical Property
Description for the Offense(s) Submitted.
Illogical combinations include:
1) Property descriptions for structures are
illogical with 220 = Burglary/Breaking &
Entering or 240 = Motor Vehicle Theft
2) Property descriptions for items that would not
fit in a purse or pocket (aircraft, vehicles,
structures, a person’s identity, watercraft, etc.)
ILLOGICAL PROPERTY are illogical with 23A = Pocket-picking or
390 DESCRIPTION FOR THE 23B = Purse-snatching
OFFENSE SUBMITTED 3) Property descriptions that cannot be shoplifted
due to other UCR definitions (aircraft,
vehicles, structures, a person’s identity,
watercraft, etc.) are illogical with 23C =
Shoplifting
4) Property descriptions for vehicles and
structures are illogical with 23D = Theft from
Building, 23E = Theft from Coin-Operated
Machine or Device, 23F = Theft from Motor
Vehicle, and 23G = Theft of Motor Vehicle
Parts or Accessories
5) Property descriptions for vehicles are illogical
with 23H = All Other Larceny
Data Element 15 (Property Description) has a code
that requires a zero value in Data Element 16
(Value of Property). Either the wrong property
description code was entered or the property value
was not entered. (This error was formerly error
number 340, a warning message.)
PROPERTY VALUE MUST BE
391 ZERO FOR DESCRIPTION Data Element 16 (Value of Property) must be zero
SUBMITTED when Data Element 15 (Property Description) is:
09=Credit/Debit Cards
22=Nonnegotiable Instruments
48=Documents–Personal or Business
65=Identity Documents
6 6=Identity–Intangible
6/30/2023 2023.0 NIBRS Technical Specification 170
Property Segment Errors
Error
Error Message Error Description
Number
An offense of 35A = Drug/Narcotic Violations and
Data Element 14 (Type Property Loss/Etc.) with
1 = None were entered, but Data Element 20
35A OFFENSE ENTERED AND (Suspected Drug Type) was not submitted. Since a
392 1=NONE ENTERED MISSING drug seizure did not occur, the suspected drug
SUSPECTED DRUG TYPE (20) type must also be entered.
Exception - The incident consists of multiple
offense segments where at least one offense code
is not 35A = Drug/Narcotic Violations.
5.2.5 Victim Segment Errors
Table 5-6 Victim Segment Errors
Victim Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element is
MUST BE PRESENT— mandatory or when the conditions are met for data
401
MANDATORY FIELD that must be entered into a conditionally mandatory
field.
402 CONTAINS NONNUMERIC ENTRY Must contain numeric entry with zero left-fill.
The referenced data element must contain a valid
404 INVALID DATA VALUE data value when it is entered; blank is permissible
on nonmandatory fields.
The referenced data element in error is one that
ERROR - DUPLICATE VALUE = contains multiple data values. When more than one
406
[value] code is entered, none can be duplicate codes.
Data Element 33 (Type Injury) Can have multiple
data values and was entered with multiple values.
ERROR - MUTUALLY EXCLUSIVE However, the entry shown between the brackets in
407
VALUE = [value] [value] above cannot be entered with any other
data value.
Data Element 26 (Age of Victim) contains data, but
EXACT AGE MUST BE IN FIRST is not left-justified. A single two-character age must
408
TWO POSITIONS be in positions 1 and 2 of the field.
Data Element 26 (Age of Victim) contains more
than two characters indicating a possible age-
409 CONTAINS NONNUMERIC ENTRY range was being attempted. If so, the field must
contain a numeric entry of four digits.
Data Element 26 (Age of Victim) was entered as an
FIRST AGE MUST BE LESS THAN age-range. Accordingly, the first age component
410
SECOND FOR AGE RANGE must be less than the second age.
6/30/2023 2023.0 NIBRS Technical Specification 171
Victim Segment Errors
Error
Error Message Error Description
Number
Data Element 2 (Incident Number) must be blank
CANNOT CONTAIN EMBEDDED right-fill if under 12 characters in length. Cannot
415 BLANKS BETWEEN FIRST AND have embedded blanks between the first and last
LAST NON BLANK CHARACTERS characters entered.
MUST BE LEFT-JUSTIFIED– Data Element 2 (Incident Number) must be left-
416 BLANK DETECTED IN FIRST justified with blank right-fill if under 12 characters in
POSITION length.
Data Element 2 (Incident Number) must contain a
valid character combination of the following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
417 OTHER THAN A–Z, 0–9, AND/OR • 0–9
HYPHEN, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not
valid.
Data Element 31 (Aggravated Assault/Homicide
Circumstances) may only be entered when one or
more of the offenses in Data Element 24 (Victim
Connected to UCR Offense Code) are:
09A = Murder and Nonnegligent Manslaughter
09B = Negligent Manslaughter
09C = Justifiable Homicide
13A = Aggravated Assault
Data Element 33 (Type Injury) may only be entered
when one or more of the offenses in Data Element
DATA CAN ONLY BE ENTERED 24 (Victim Connected to UCR Offense Code) are:
419
FOR SPECIFIC OFFENSES
100 = Kidnapping/Abduction
11A = Rape
11B = Sodomy
11C = Sexual Assault With An Object
11D = Fondling
120 = Robbery
13A = Aggravated Assault
13B = Simple Assault
210 = Extortion/Blackmail
64A = Human Trafficking, Commercial Sex Acts
64B = Human Trafficking, Involuntary Servitude
Data Element 26 (Age of Victim) was entered as an
AGE RANGE CANNOT HAVE 00 age-range. Therefore, the first age component
422
IN FIRST TWO POSITIONS cannot be 00 = Unknown.
Data Element 26 (Age of Victim) cannot be less
VICTIM IS SPOUSE BUT AGE IS than 13 years old when Data Element 35
450 (Relationship of Victim to Offender) contains a
LESS THAN 13
relationship of SE = Spouse.
6/30/2023 2023.0 NIBRS Technical Specification 172
Victim Segment Errors
Error
Error Message Error Description
Number
When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot
VICTIM NUMBER ALREADY contain duplicates. In this case, two victim
451
EXISTS segments were submitted having the same entry in
Data Element 23 (Victim Sequence Number).
AGE OF VICTIM MUST BE (Age of Victim) must be 17 or greater and less than
GREATER THAN OR EQUAL TO or equal to 98 or 00 = Unknown, when Data
452 17 AND LESS THAN OR EQUAL Element 25 (Type of Victim) is L = Law
TO 98 WHEN VICTIM TYPE (25) = Enforcement Officer. (Data Element 26 must be
L >=17 & <=98 or Data Element 26 = 00)
The data element associated with this error must
MUST BE PRESENT WHEN be present when Data Element 25 (Type of Victim)
453
VICTIM TYPE (25) = I is I = Individual.
Data Element 25A (Type of Officer
Activity/Circumstance), Data Element 25B (Officer
MUST BE ENTERED WHEN Assignment Type), Data Element 26 (Age of
454 VICTIM TYPE IS LAW Victim), Data Element 27 (Sex of Victim), and Data
ENFORCEMENT OFFICER Element 28 (Race of Victim) must be entered when
Data Element 25 (Type of Victim) is L = Law
Enforcement Officer.
Data Element 31 (Aggravated Assault/Homicide
ADDITIONAL JUSTIFIABLE Circumstances) contains: 20 = Criminal Killed by
455 HOMICIDE IS MANDATORY WITH Private Citizen or 21 = Criminal Killed by Police
A 20 OR 21 ENTERED Officer, but Data Element 32 (Additional Justifiable
Homicide Circumstances) was not entered.
Data Element 31 (Aggravated Assault/Homicide
Circumstances) was entered with two entries but
was rejected for one of the following reasons:
1) 10 = Unknown Circumstances is mutually
exclusive with any other value.
MULTIPLE VALUES ENTERED 2) Multiple values from more than one category
FOR DATA ELEMENT ARE NOT were entered.
456
COMPATIBLE - VALUES ARE
MUTUALLY EXCLUSIVE 3) Values from the category 09B = Negligent
Manslaughter are mutually exclusive with any
other value.
4) Values from the category 09C = Justifiable
Homicide are mutually exclusive with any
other value.
Data Element 32 (Additional Justifiable Homicide
WHEN DATA ELEMENT 32 IS Circumstances) was entered, but Data Element 31
457 ENTERED, DATA ELEMENT 31 (Aggravated Assault/Homicide Circumstances)
MUST EQUAL 20 OR 21 does not reflect a justifiable homicide
circumstance.
The Data Element associated with this error cannot
VICTIM TYPE (25) MUST BE I OR be entered when Data Element 25 (Type of Victim)
458
L FOR DATA TO BE ENTERED is not I = Individual or L = Law Enforcement Officer.
6/30/2023 2023.0 NIBRS Technical Specification 173
Victim Segment Errors
Error
Error Message Error Description
Number
Corresponding Data Element 35 (Relationship of
RELATIONSHIP MUST BE Victim to Offender) data must be entered when
460 ENTERED WHEN AN OFFENDER Data Element 34 (Offender Numbers to be
NUMBER (34) EXISTS Related) is entered with a value greater than 00.
461 ENTRY FOR TYPE OF VICTIM (Type of Victim) Must have a value of G =
MUST BE G WHEN THIS Government when Data Element 24 (Victim
OFFENSE CODE IS ENTERED Connected to UCR Offense Code) contains one of
the following:
26H = Money Laundering*
521 = National Firearm Act 1934*
522 = Weapons of Mass Destruction*
526 = Explosives*
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 31 (Aggravated Assault/Homicide
Circumstances) can only have codes of 01 through
INVALID AGGRAVATED 06 and 08 through 10 when Data Element 24
462 ASSAULT/HOMICIDE FOR 13A (Victim Connected to UCR Offense) is 13A =
OFFENSE Aggravated Assault. All other codes, including 07 =
Mercy Killing, are not valid because they do not
relate to an aggravated assault.
When a Justifiable Homicide is reported, Data
Element 31 (Aggravated Assault/Homicide
INVALID AGGRAVATED Circumstances) can only have codes of
463 ASSAULT/HOMICIDE FOR 09C 20 = Criminal Killed by Private Citizen or
OFFENSE 21 = Criminal Killed by Police Officer. In this case,
a code other than the two mentioned was entered.
(Type of Victim) Must have a value of I = Individual
ENTRY FOR TYPE OF VICTIM or L = Law Enforcement Officer when Data
464 MUST BE I WHEN THIS OFFENSE Element 24 (Victim Connected to UCR Offense
CODE IS ENTERED Code) contains a Crime Against Person.
6/30/2023 2023.0 NIBRS Technical Specification 174
Victim Segment Errors
Error
Error Message Error Description
Number
(Type of Victim) must have a value of
S = Society/Public when Data Element 24 (Victim
Connected to UCR Offense Code) contains a
Crime Against Society.
Exception:
26H = Money Laundering*
521 = National Firearm Act 1934*
ENTRY FOR TYPE OF VICTIM
522 = Weapons of Mass Destruction*
465 MUST BE S WHEN THIS
526 = Explosives*
OFFENSE CODE IS ENTERED
58A = Import Violations
58B = Export Violations
61A = Federal Liquor Offenses
61B = Federal Tobacco Offenses
620 = Wildlife Trafficking*
*Denotes offenses for federal and tribal LEA
reporting only
Each UCR Offense Code entered into Data
Element 24 (Victim Connected to UCR Offense
OFFENSE MUST BE SUBMITTED Code) must have the Offense Segment for the
466 AS LEVEL 2 RECORD IF VICTIM value. In this case, the victim was connected to
IS CONNECTED offenses that were not submitted as Offense
Segments. A victim cannot be connected to an
offense when the offense itself is not present.
(Type of Victim) cannot have a value of S =
ENTRY FOR TYPE OF VICTIM Society/Public when Data Element 24 (Victim
467 CANNOT BE S WHEN THIS Connected to UCR Offense Code) contains a
OFFENSE CODE IS ENTERED Crime Against Property.
Data Element 35 (Relationship of Victim to
RELATIONSHIP CANNOT BE Offender) cannot be entered when Data Element
468 ENTERED WHEN RELATED TO 34 (Offender Number to be Related) is zero. Zero
OFFENDER NUMBER 00 means that the number of offenders is unknown;
therefore, the relationship cannot be entered.
Data Element 27 (Sex of Victim) must be M = Male
VICTIM SEX MUST BE M OR F or F = Female to be connected to offense codes of
469
FOR AN 11A OR 36B OFFENSE 11A = Rape and 36B = Statutory Rape.
Data Element 35 (Relationship of Victim to
Offender) has a relationship of VO = Victim Was
Offender. When this code is entered, a minimum of
two victim and two offender segments must be
WHEN VO RELATIONSHIP IS submitted. In this case, only one victim and/or one
PRESENT, MUST HAVE TWO OR offender segment was submitted. The entry of VO
470
MORE VICTIMS AND on one or more of the victims indicates situations
OFFENDERS such as brawls and domestic disputes. In the vast
majority of cases, each victim is also the offender;
therefore, every victim record would contain a VO
code.
6/30/2023 2023.0 NIBRS Technical Specification 175
Victim Segment Errors
Error
Error Message Error Description
Number
Data Element 35 (Relationship of Victim to
Offenders) has relationships of VO = Victim Was
ONLY ONE VO RELATIONSHIP Offender that point to multiple offenders, which is
471
PER VICTIM an impossible situation. A single victim cannot be
two offenders.
If Data Element 37 (Age of Offender) is
WHEN OFFENDER 00 = Unknown, Data Element 38 (Sex of Offender)
AGE/SEX/RACE ARE UNKNOWN, is U = Unknown, and Data Element 39 (Race of
472 Offender) is U = Unknown, then Data Element 35
RELATIONSHIP MUST BE
RU=UNKNOWN (Relationship of Victim to Offender) must be
RU = Relationship Unknown.
Segment Level 4 (Victim Segment) cannot be
submitted multiple times with VO = Victim Was
ONLY ONE VO RELATIONSHIP Offender in Data Element 35 (Relationship of
474 CAN BE ASSIGNED TO A Victim to Offender) when Data Element 34
SPECIFIC OFFENDER (Offender Number to be Related) contains the
same data value (indicating the same offender).
A victim can only have one spousal relationship. In
ONLY ONE SE RELATIONSHIP this instance, the victim has a relationship of
475
PER VICTIM SE = Spouse to two or more offenders.
An offender can only have one spousal
ONLY ONE SE RELATIONSHIP relationship. In this instance, two or more victims
476 CAN BE ASSIGNED TO A have a relationship of SE = Spouse to the same
SPECIFIC OFFENDER offender.
A victim segment was submitted with Data Element
INVALID AGGRAVATED 24 (Victim Connected to UCR Offense Code)
ASSAULT/HOMICIDE having an offense that does not have a permitted
477
CIRCUMSTANCES FOR code for Data Element 31 (Aggravated
CONNECTED OFFENSE Assault/Homicide Circumstances).
6/30/2023 2023.0 NIBRS Technical Specification 176
Victim Segment Errors
Error
Error Message Error Description
Number
Mutually exclusive offenses are ones that cannot
occur to the same victim by UCR definitions. A
lesser included offense is one that is an element of
another offense and should not be reported as
having happened to the victim along with the other
offense. Lesser included and mutually exclusive
offenses are defined as follows:
1) Murder – Aggravated Assault, Simple Assault,
and Intimidation are all Lesser Included
offenses of Murder. Negligent Manslaughter is
Mutually Exclusive.
2) Aggravated Assault – Simple Assault and
Intimidation are Lesser Included. Note:
Aggravated Assault is a Lesser Included
offense of Murder, Rape, Sodomy, Sexual
Assault With An Object, and Robbery.
3) Simple Assault – Intimidation is a Lesser
Included offense of Simple Assault. Note:
Simple Assault is a Lesser Included offense of
Murder, Aggravated Assault, Rape, Sodomy,
Sexual Assault With An Object, Fondling, and
Robbery.
VICTIM CONNECTED TO AN 4) Intimidation – Intimidation is a Lesser Included
478 INVALID COMBINATION OF offense of Murder, Aggravated Assault, Rape,
OFFENSES Sodomy, Sexual Assault With An Object,
Fondling, and Robbery.
5) Negligent Manslaughter – Murder, Aggravated
Assault, Simple Assault, and Intimidation are
Mutually Exclusive offenses. Negligent
Manslaughter is defined as the killing of
another person through negligence, while
assault offenses are characterized by unlawful
attack(s).
6) Rape – Aggravated Assault, Simple Assault,
Intimidation, and Fondling are Lesser Included
offenses of Rape. Incest and Statutory Rape
are mutually exclusive offenses and cannot
occur with Rape. The prior two offenses
involve consent, while the latter involves
action against the victim’s will.
7) Sodomy – Aggravated Assault, Simple
Assault, Intimidation, and Fondling are Lesser
Included offenses of Sodomy. Incest and
Statutory Rape are Mutually Exclusive
offenses and cannot occur with Sodomy. The
prior two offenses involve consent, while the
latter involves action against the victim’s will.
6/30/2023 2023.0 NIBRS Technical Specification 177
Victim Segment Errors
Error
Error Message Error Description
Number
8) Sexual Assault With An Object – Aggravated
Assault, Simple Assault, Intimidation, and
Fondling are Lesser Included offenses of
Sexual Assault With An Object. Incest and
Statutory Rape are Mutually Exclusive
offenses and cannot occur with Sexual
Assault With An Object. The prior two
offenses involve consent, while the latter
involves action against the victim’s will.
9) Fondling – Simple Assault and Intimidation
are Lesser Included offenses of Fondling.
Incest and Statutory Rape are mutually
exclusive offenses and cannot occur with
Fondling. The prior two offenses involve
consent, while the latter involves forced action
against the victim’s will. Note: Fondling is a
Lesser Included offense of Rape, Sodomy,
and Sexual Assault With An Object.
10) Incest – Rape, Sodomy, Sexual Assault With
An Object, and Fondling are Mutually
Exclusive offenses. Incest involves consent,
while the prior offenses involve sexual
relations against the victim’s will.
11) Statutory Rape – Rape, Sodomy, Sexual
Assault With An Object, and Fondling are
Mutually Exclusive offenses. Statutory Rape
involves consent, while the prior offenses
involve sexual relations against the victim’s
will.
12) Robbery – Aggravated Assault, Simple
Assault, Intimidation, and all Theft offenses
(including Motor Vehicle Theft) are Lesser
Included offenses of Robbery.
A Simple Assault (13B) was THE ONLY CRIME
AGAINST PERSON OFFENSE committed against
a victim, but the victim had major injuries/trauma
SIMPLE ASSAULT(13B) CANNOT entered for Data Element 33 (Type Injury). Either
479
HAVE MAJOR INJURIES the offense should have been classified as an
13A = Aggravated Assault or the victim’s injury
should not have been entered as major.
6/30/2023 2023.0 NIBRS Technical Specification 178
Victim Segment Errors
Error
Error Message Error Description
Number
Data Element 31 (Aggravated Assault/Homicide
Circumstances) has 08 = Other Felony Involved
but the incident has only one offense. For this code
WHEN ASSAULT/HOMICIDE (31) to be used, there must be an Other Felony. Either
480 IS 08, INCIDENT MUST HAVE multiple entries for Data Element 6 (UCR Offense
TWO OR MORE OFFENSES Code) should have been submitted, or multiple
individual victims should have been submitted for
the incident report.
VICTIM'S AGE IS 18 OR OVER Data Element 26 (Age of Victim) should be under
481 FOR STATUTORY RAPE 18 when Data Element 24 (Victim Connected to
OFFENSE UCR Offense Code) is 36B = Statutory Rape.
Data Element 25 (Type of Victim) cannot be
L = Law Enforcement Officer unless Data Element
24 (Victim Connected to UCR Offense Code) is
LEOKA VICTIM MUST BE one of the following:
482 CONNECTED TO MURDER OR
ASSAULT OFFENSE 09A = Murder & Nonnegligent Manslaughter
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
Data Element 25A (Type of Officer Activity/
Circumstance), Data Element 25B (Officer
VICTIM MUST BE LAW Assignment Type), Data Element 25C (Officer–ORI
483 ENFORCEMENT OFFICER TO Other Jurisdiction), may be entered only when
ENTER LEOKA DATA Data Element 25 (Type of Victim) is L = Law
Enforcement Officer.
Segment Length for the Victim Segment (Level 4)
must be 129 characters (not reporting LEOKA) or
141 characters (reporting LEOKA). Once an
agency begins participation in reporting the LEOKA
via NIBRS data elements 25A/25B/25C, indicated
by 0141 in the RDW, then all future Victim
THIS VICTIM SEGMENT HAS A
484 Segments within that ORI must be formatted using
CONFLICTING LENGTH
0141.
Note: The only exception would be that data prior
to the agency starting to report LEOKA via the
NIBRS data elements, could be submitted with the
original 0129 RDW.
485 OFFENDER NUMBER TO BE (Offender Number to be Related) cannot be 00 =
RELATED CANNOT BE 00 FOR Unknown when Data Element 24 (Victim
THIS OFFENSE Connected to UCR Offense Code) is 360 = Failure
to Register as a Sex Offender*.
*Denotes offenses for federal and tribal LEA
reporting only
6/30/2023 2023.0 NIBRS Technical Specification 179
Victim Segment Errors
Error
Error Message Error Description
Number
(Type of Victim) when Type of Victim is L = Law
Enforcement Officer and Data Element 24 (Victim
Connected to UCR Offense Code) is one of the
following:
INCIDENT DATE/HOUR MUST
09A = Murder & Nonnegligent Manslaughter
CONTAIN A VALID ENTRY WHEN
490 13A = Aggravated Assault
VICTIM IS L = LAW
13B = Simple Assault
ENFORCEMENT OFFICER
13C = Intimidation
Data Element 3 (Incident Date/Hour) must be
populated with a valid hour (00-23) and cannot be
blank.
Each “X” on the chart where offenses intersect denotes that those two offenses cannot occur to
the same victim in the same incident. This chart corresponds to Error Code 478.
6/30/2023 2023.0 NIBRS Technical Specification 180
Table 5-7 Mutually Exclusive Offenses for Error Code 478 Chart
23G - Theft of Motor Vehicle Part
09C Justifiable Homicide cannot
23E - Theft From Coin Machine
23F - Theft From Motor Vehicle
11C - Sexual Assault w/Object
09B - Negligent Manslaughter
occur with any other offense
23D - Theft From Building
13A - Aggravated Assault
240 - Motor Vehicle Theft
23H - All Other Larceny
23B - Purse-snatching
36B - Statutory Rape
13B - Simple Assault
23A - Pocket-picking
13C - Intimidation
23C - Shoplifting
11D - Fondling
11B - Sodomy
120 - Robbery
09A - Murder
36A - Incest
11A - Rape
09A - Murder X X X X X
09B - Negligent Manslaughter X X X X X
11A - Rape X X X X X X X
11B - Sodomy X X X X X X X
11C - Sexual Assault w/Object X X X X X X X
11D - Fondling X X X X X X X X
120 - Robbery X X X X X X X X X X X X X
13A - Aggravated Assault X X X X X X X X X
13B Simple Assault X X X X X X X X X X
13C - Intimidation X X X X X X X X X X
23A - Pocket-picking X X
23B - Purse-snatching X X
23C - Shoplifting X X
23D - Theft From Building X X
23E - Theft From Coin Machine X X
23F - Theft From Motor Vehicle X X
23G - Theft of Motor Vehicle Part X X
23H - All Other Larceny X X
240 - Motor Vehicle Theft X X
36A - Incest X X X X X
36B - Statutory Rape X X X X X
6/30/2023 2023.0 NIBRS Technical Specification 181
5.2.6 Offender Segment Errors
Table 5-8 Offender Segment Errors
Offender Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element is
MUST BE PRESENT—
501 mandatory or when the conditions are met for data
MANDATORY FIELD
that must be entered into a conditionally mandatory
field.
Data Element 36 (Offender Sequence Number)
502 CONTAINS NONNUMERIC ENTRY must contain numeric entry (00 through 99) with
zero left-fill.
The referenced data element must contain a valid
504 INVALID DATA VALUE data value when it is entered; blank is permissible
on nonmandatory fields.
Data Element 37 (Age of Offender) contains data
EXACT AGE MUST BE IN FIRST
508 but is not left-justified. A single two-character age
TWO POSITIONS
must be in positions 1 through 2 of the field.
Data Element 37 (Age of Offender) contains more
than two characters indicating a possible age-
509 CONTAINS NONNUMERIC ENTRY
range is being attempted. If so, the field must
contain a numeric entry of four digits.
Data Element 37 (Age of Offender) was entered as
FIRST AGE MUST BE LESS THAN
510 an age-range. Accordingly, the first age component
SECOND FOR AGE RANGE
must be less than the second age.
CANNOT HAVE EMBEDDED Must be blank right-fill if under 12 characters in
515 BLANKS BETWEEN FIRST AND length. Cannot have embedded blanks between
LAST NON-BLANK CHARACTERS the first and last characters entered.
MUST BE LEFT-JUSTIFIED–
Must be left-justified with blank right-fill if under 12
516 BLANK DETECTED IN FIRST
characters in length.
POSITION
Must contain a valid character combination of the
following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
517 OTHER THAN A–Z, 0–9, AND/OR • 0–9
HYPHEN, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not
valid.
Data Element 37 (Age of Offender) was entered as
AGE RANGE CANNOT HAVE 00
522 an age-range. Therefore, the first age component
IN FIRST TWO POSITIONS
cannot be 00 = Unknown.
Data Element 37 (age of Offender) cannot be less
OFFENDER IS SPOUSE, BUT than 13 years old when Data Element 35
550
AGE IS LESS THAN 13 (Relationship of Victim to Offender) contains a
relationship of SE = Spouse.
6/30/2023 2023.0 NIBRS Technical Specification 182
Offender Segment Errors
Error
Error Message Error Description
Number
When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot
DUPLICATE OFFENDER
551 contain duplicates. In this case, two Offender
SEGMENT
Segments were submitted having the same entry in
Data Element 36 (Offender Sequence Number).
CANNOT BE PRESENT WHEN Data Element 37 (Age of Offender) cannot be
552 OFFENDER NUMBER IS 00 entered when Data Element 36 (Offender
UNKNOWN Sequence Number) is 00 = Unknown.
Data Element 35 (Relationship of Victim to
Offender) has a relationship that is inconsistent
with the offender’s age. The age of the victim
and/or offender must reflect the implied
relationship. For example, if the relationship of the
victim to offender is PA = Parent, then the victim’s
AGE OF VICTIM AND OFFENDER age must be greater than the offender’s age. The
554 DOES NOT REFLECT THE following relationships must be consistent with the
RELATIONSHIP victim’s age in relation to the offender’s age:
Relationship Victim’s Age Is:
CH = Victim was Child (Younger)
PA = Victim was Parent (Older)
GP = Victim was Grandparent (Older)
GC = Victim was Grandchild (Younger)
When multiple Offender Segments are submitted,
none can contain a 00 = Unknown value because
OFFENDER 00 EXISTS-CANNOT the presence of 00 indicates that the number of
555
SUBMIT MORE OFFENDERS offenders is unknown. In this case, multiple
offenders were submitted, but one of the segments
contains the 00 = Unknown value.
OFFENDER AGE MUST BE Data Element 37 (Age of Offender) must contain
556
NUMERIC DIGITS numeric entry of 00 through 99.
Data Element 36 (Offender Sequence Number)
contains 00 indicating that nothing is known about
OFFENDER SEQUENCE NUMBER
the offender(s) regarding number and any
CANNOT BE UNKNOWN IF
557 identifying information. To exceptionally clear the
INCIDENT CLEARED
incident, the value cannot be 00. The incident was
EXCEPTIONALLY
submitted with Data Element 4 (Cleared
Exceptionally) having a value of A through E.
None of the Offender Segments contain all known
values for age, sex, and race. When an incident is
AT LEAST ONE OFFENDER
558 cleared exceptionally (Data Element 4 contains an
MUST HAVE KNOWN VALUES
A through E), one offender must have all known
values.
6/30/2023 2023.0 NIBRS Technical Specification 183
Offender Segment Errors
Error
Error Message Error Description
Number
The incident was submitted with Data Element 6
(UCR Offense Code) value of 09C = Justifiable
OFFENDER DATA MUST BE Homicide or 360 = Failure to Register as a Sex
PRESENT IF OFFENSE CODE IS Offender*, but unknown information was submitted
559 09C = JUSTIFIABLE HOMICIDE for all the offender(s). At least one of the offenders
OR 360 = FAILURE TO REGISTER must have known information for age, sex, and
AS A SEX OFFENDER* race.
*Denotes offenses for federal and tribal LEA
reporting only
Segment Length for the Offender Segment (Level
5) must be 45 characters (not reporting Offender
Ethnicity) or 46 characters (reporting Offender
Ethnicity).Once an agency begins participation in
THIS OFFENDER SEGMENT HAS reporting the Offender Ethnicity, indicated by 0046
584 in the RDW, then all future Offender Segments
A CONFLICTING LENGTH
within that ORI must be formatted using 0046.
Note: The only exception would be that data prior
to the agency starting to report Offender Ethnicity
could be submitted with the original 0045 RDW.
5.2.7 Arrestee Segment Errors
Table 5-9 Arrestee Segment Errors
Arrestee Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an Incident must
contain data when the referenced data element is
MUST BE PRESENT—
601 mandatory or when the conditions are met for
MANDATORY FIELD
data that must be entered into a conditionally
mandatory field.
(Arrestee Sequence Number) must be numeric
602 CONTAINS NONNUMERIC ENTRY
entry of 01 to 99 with zero left-fill.
The referenced data element must contain a valid
604 INVALID DATA VALUE data value when it is entered; blank is permissible
on nonmandatory fields.
6/30/2023 2023.0 NIBRS Technical Specification 184
Arrestee Segment Errors
Error
Error Message Error Description
Number
Data Element 42 (Arrest Date) Each component
of the date must be valid; that is, months must be
01 through 12, days must be 01 through 31, and
year must include the century (i.e., 19xx, 20xx). In
addition, days cannot exceed maximum for the
month (e.g., June cannot have 31 days). The date
cannot exceed the current date.
605 INVALID ARREST DATE
The date cannot be later than that entered within
the Month of Electronic submission and Year of
Electronic submission fields on the data record.
For example, if Month of Electronic submission
and Year of Electronic submission are 06/1999,
the arrest date cannot contain any date
07/01/1999 or later.
Data Element 46 (Arrestee Was Armed With) The
referenced data element in error is one that
ERROR-DUPLICATE VALUE =
606 contains multiple data values. When more than
[value]
one code is entered, none can be duplicate
codes.
Data Element 46 (Arrestee Was Armed With) can
ERROR-MUTUALLY EXCLUSIVE have multiple data values and was entered with
607
VALUE = [value] multiple values. However, 01 = Unarmed cannot
be entered with any other data value.
Data Element 47 (Age of Arrestee) contains data,
EXACT AGE MUST BE IN FIRST
608 but is not left-justified. A single two-character age
TWO POSITIONS
must be in positions 1 through 2 of the field.
Data Element 47 (Age of Arrestee) contains more
than two characters indicating a possible age-
609 CONTAINS NONNUMERIC ENTRY
range is being attempted. If so, the field must
contain a numeric entry of four digits.
Data Element 47 (Age of Arrestee) was entered
FIRST AGE MUST BE LESS THAN
610 as an age-range. Accordingly, the first age
SECOND FOR AGE RANGE
component must be less than the second age.
CANNOT HAVE EMBEDDED Must be blank right-fill if under 12 characters in
615 BLANKS BETWEEN FIRST AND length. Cannot have embedded blanks between
LAST NON-BLANK CHARACTERS the first and last characters entered.
Data Element 2 (Incident Number) and Data
MUST BE LEFT-JUSTIFIED-
Element 41 (Arrest Transaction Number) must be
616 BLANK DETECTED IN FIRST
left justified with blank right-fill when less than 12
POSITION
characters in length.
Data Element 2 (Incident Number) Must contain a
valid character combination of the following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
617 OTHER THAN A-Z, 0-9, • 0–9
HYPHENS, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
6/30/2023 2023.0 NIBRS Technical Specification 185
Arrestee Segment Errors
Error
Error Message Error Description
Number
Data Element 42 (Arrest Date) The UCR Program
ARREST DATE CANNOT BE ON has determined that an ORI will no longer be
618 OR AFTER THE INACTIVE DATE submitting data to the FBI as of an inactive date.
OF THE ORI The FBI will not accept arrest data from this ORI
after this date.
Data Element 47 (Age of Arrestee) was entered
AGE RANGE CANNOT HAVE 00
622 as an age-range. Therefore, the first age
IN FIRST TWO POSITIONS
component cannot be 00 = Unknown.
(UCR Arrest Offense Code) The following values
for Data Element 45 (UCR Arrest Offense Code)
are valid only for use by federal and tribal
agencies:
26H = Money Laundering*
101 = Treason*
103 = Espionage*
30A = Illegal Entry into the United States*
30B = False Citizenship*
30C = Smuggling Aliens*
30D = Re-entry after Deportation*
360 = Failure to Register as a Sex Offender*
49A = Harboring Escapee/Concealing from
ARREST OFFENSE CODE CAN Arrest*
650 ONLY BE USED BY FEDERAL 49B = Flight to Avoid Prosecution*
AND TRIBALAGENCIES 49C = Flight to Avoid Deportation*
521 = Violation of National Firearm Act of 1934*
522 = Weapons of Mass Destruction*
526 = Explosives *
58A = Import Violations*
58B = Export Violations*
61A = Federal Liquor Offenses*
61B = Federal Tobacco Offenses*
620 = Wildlife Trafficking*
90K = Failure to Appear*
90L = Federal Resource Violations*
90M = Perjury*
*Denotes offenses for federal and tribal LEA
reporting only
Data Element 52 (Disposition of Arrestee Under
DISPOSITION MUST BE 18) was not entered, but Data Element 47 (Age of
652 ENTERED WHEN AGE IS LESS Arrestee) is under 18. Whenever an arrestee’s
THAN 18 age indicates a juvenile, the agency must enter
the disposition..
Data Element 52 (Disposition of Arrestee Under
FOR AGE GREATER THAN 17 18) was entered, but Data Element 47 (Age of
653 DISPOSITION SHOULD NOT BE Arrestee) is 18 or greater. Whenever an arrestee’s
ENTERED age indicates an adult, the agency cannot enter
the juvenile disposition because it does not apply.
Data Element 46 (Arrestee Was Armed With)
AUTOMATIC INDICATOR MUST
654 does not have A = Automatic or a blank in the
BE BLANK OR A
third position of field.
6/30/2023 2023.0 NIBRS Technical Specification 186
Arrestee Segment Errors
Error
Error Message Error Description
Number
In Data Element 46 (Arrestee Was Armed With), A
= Automatic is the third character of code. It is
valid only with codes:
11 = Firearm (Type Not Stated)
WEAPON TYPE MUST = 11, 12, 12 = Handgun
655 13, 14, OR 15 FOR AN A IN THE 13 = Rifle
AUTO INDICATOR 14 = Shotgun
15 = Other Firearm
A weapon code other than those mentioned was
entered with the automatic indicator. An automatic
weapon is, by definition, a firearm.
A Group A Incident Report was submitted with
more arrestees than offenders. The number (nn)
of offenders is shown within the message. The
incident must be resubmitted with additional
Offender Segments. This message will also occur
if an arrestee was submitted and Data Element 36
(Offender Sequence Number) was 00 = Unknown.
THIS ARRESTEE EXCEEDED THE
656 NUMBER OF OFFENDERS ON The exception to this rule is when an additional
THE GROUP A INCIDENT arrest is reported for a pre-NIBRS incident. In this
case, Segment Level 6 (Arrestee Segment) will
contain A = Add, but the data value in Data
Element 2 (Incident Number) will not match an
incident already on file in the national UCR
database. The segment will be processed but
used only for SRS purposes and will not be
included in the agency’s NIBRS figures.
Segment Level 6 (Arrestee Segment) cannot
contain duplicate data values in Data Element 40
(Arrestee Sequence Number) when two or more
Arrestee Segments are submitted for the same
incident. Data Element 41 (Arrest Transaction
Number) is the number assigned by the reporting
ARRESTEE SEQUENCE NUMBER
661 agency to an arrest report to identify it uniquely. If
ALREADY EXISTS
multiple arrestees are reported, each having the
same data value in Data Element 40 (Arrestee
Sequence Number), ensure that Data Element
(Arrest Transaction) is unique for each arrestee
submitted to ensure that duplication does not
occur.
Data Element 47 (Age of Arrestee) does not
ARRESTEE AGE MUST BE
664 contain a numeric entry of 00 through 99 for an
NUMERIC DIGITS
exact age.
6/30/2023 2023.0 NIBRS Technical Specification 187
Arrestee Segment Errors
Error
Error Message Error Description
Number
Data Element 42 (Arrest Date) cannot be earlier
than Data Element 3 (Incident Date/Hour). A
person cannot be arrested before the incident
occurred.
The exception to this rule is when an additional
ARREST DATE CANNOT BE arrest is reported for a pre-NIBRS incident. In this
665 BEFORE THE INCIDENT START case, Segment Level 6 (Arrestee Segment) will
DATE contain I = Incident Report, but the data value in
Data Element 2 (Incident Number) will not match
an incident already on file in the national UCR
database. The segment will be processed, but
used only for SRS purposes and will not be
included in the agency’s NIBRS figures.
Data Element 48 (Sex of Arrestee) does not
contain a valid code of M = Male or F = Female.
667 INVALID ARRESTEE SEX VALUE
Note: U = Unknown (if entered) is not a valid sex
for an arrestee.
Group A Incident Reports cannot have arrests
when Data Element 6 (UCR Offense Code) is
NO ARRESTEE RECORDS
09C = Justifiable Homicide. By definition a
669 ALLOWED FOR A JUSTIFIABLE
justifiable homicide never involves an arrest of the
HOMICIDE
offender (the person who committed the justifiable
homicide).
Data Element 45 (UCR Arrest Offense Code) was
JUSTIFIABLE HOMICIDE CANNOT
670 entered with 09C = Justifiable Homicide. This is
BE AN ARREST OFFENSE CODE
not a valid arrest offense.
5.2.8 Group B Arrest Report Segment Errors
Table 5-10 Group B Arrest Report Segment Errors
Group B Arrest Report Segment Errors
Error
Error Message Error Description
Number
The referenced data element in an incident must
contain data when the referenced data element
MUST BE PRESENT—
701 is mandatory or when the conditions are met for
MANDATORY FIELD
data that must be entered into a conditionally
mandatory field.
Data Element 40 (Arrestee Sequence Number)
702 CONTAINS NONNUMERIC ENTRY must be numeric entry of 01 to 99 with zero left-
fill.
The referenced data element must contain a
704 INVALID DATA VALUE valid data value when it is entered; blank is
permissible on nonmandatory fields.
Data Element 42 (Arrest Date) Each component
of the date must be valid; that is, months must be
705 INVALID ARREST DATE
01 through 12, days must be 01 through 31, and
year must include the century (i.e., 19xx, 20xx).
6/30/2023 2023.0 NIBRS Technical Specification 188
Group B Arrest Report Segment Errors
Error
Error Message Error Description
Number
In addition, days cannot exceed maximum for the
month (e.g., June cannot have 31 days). The
date cannot exceed the current date.
The date cannot be later than that entered within
the Month of Electronic submission and Year of
Electronic submission fields on the data record.
For example, if Month of Electronic submission
and Year of Electronic submission are 06/1999,
the arrest date cannot contain any date
07/01/1999 or later.
Data Element 46 (Arrestee Was Armed With)
ERROR-DUPLICATE VALUE =
706 cannot contain duplicate data values although
[value]
more than one data value is allowed.
Data Element 46 (Arrestee Was Armed With) can
ERROR-MUTUALLY EXCLUSIVE have multiple data values and was entered with
707
VALUE = [value] multiple values. However, 01 = Unarmed cannot
be entered with any other data value.
Data Element 47 (Age of Arrestee) contains data,
EXACT AGE MUST BE IN FIRST
708 but is not left-justified. A single two-character age
TWO POSITIONS
must be in positions 1 through 2 of the field.
Data Element 47 (Age of Arrestee) contains
more than two characters indicating a possible
709 CONTAINS NONNUMERIC ENTRY
age-range is being attempted. If so, the field
must contain numeric entry of four digits.
Data Element 47 (Age of Arrestee) was entered
FIRST AGE MUST BE LESS THAN
710 as an age-range. Accordingly, the first age
SECOND FOR AGE RANGE
component must be less than the second age.
CANNOT HAVE EMBEDDED Must be blank right-fill if under 12 characters in
715 BLANKS BETWEEN FIRST AND length. Cannot have embedded blanks between
LAST NON-BLANK CHARACTERS the first and last characters entered.
MUST BE LEFT-JUSTIFIED–
Must be left-justified with blank right-fill if under
716 BLANK DETECTED IN FIRST
12 characters in length.
POSITION
Must contain a valid character combination of the
following:
CANNOT HAVE CHARACTERS • A–Z (capital letters only)
717 OTHER THAN A-Z, 0-9, AND/OR • 0–9
HYPHENS, AND/OR BLANKS • Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
Data Element 42 (Arrest Date) The UCR
ARREST DATE CANNOT BE ON Program has determined that an ORI will no
718 OR AFTER THE INACTIVE DATE longer be submitting data to the FBI as of an
OF THE ORI inactive date. The FBI will not accept arrest data
from this ORI after this date.
GROUP B ADD CANNOT Group B Arrest Report (Level 7) submitted with a
720
PREDATE NIBRS START DATE Segment Action Type of A = Add cannot have
6/30/2023 2023.0 NIBRS Technical Specification 189
Group B Arrest Report Segment Errors
Error
Error Message Error Description
Number
Data Element 42 (Arrest Date) earlier than the
Base Date.
Data Element 47 (Age of Arrestee) was entered
AGE RANGE CANNOT HAVE 00
722 as an age-range. Therefore, the first age
IN FIRST TWO POSITIONS
component cannot be 00 = Unknown.
(UCR Arrest Offense Code) The following values
for Data Element 45 (UCR Arrest Offense Code)
are only valid for use by federal and tribal
agencies:
26H = Money Laundering
101 = Treason
103 = Espionage
30A = Illegal Entry into the United States
30B = False Citizenship
30C = Smuggling Aliens
30D = Re-entry after Deportation
360 = Failure to Register as a Sex Offender
ARREST OFFENSE CODE CAN 49A = Harboring Escapee/Concealing from
750 ONLY BE USED BY FEDERAL Arrest
AND TRIBAL AGENCIES 49B = Flight to Avoid Prosecution
49C = Flight to Avoid Deportation
521 = Violation of National Firearm Act of 1934
522 = Weapons of Mass Destruction
526 = Explosives
58A = Import Violations
58B = Export Violations
61A = Federal Liquor Offenses
61B = Federal Tobacco Offenses
620 = Wildlife Trafficking
90K = Failure to Appear
90L = Federal Resource Violations
90M = Perjury
(Group B Arrest Report Segment) When a Group
B Arrest Report (Level 7) has two or more
arrestees, the individual segments comprising
the report cannot contain duplicates. In this case,
two arrestee segments were submitted having
the same entry in Data Element 40 (Arrestee
Sequence Number). Error should only be thrown
when the action type is A = Add.
ARRESTEE SEQUENCE NUMBER
751 The Data Element 41 (Arrest Transaction
ALREADY EXISTS
Number) is the number assigned by the reporting
agency to an arrest report to identify it uniquely.
If multiple arrestees are reported, each having
the same data value in Data Element 40
(Arrestee Sequence Number), ensure that Data
Element 41 (Arrest Transaction Number) is
unique for each arrestee submitted to ensure that
duplication does not occur.
6/30/2023 2023.0 NIBRS Technical Specification 190
Group B Arrest Report Segment Errors
Error
Error Message Error Description
Number
Data Element 52 (Disposition of Juvenile) was
DISPOSITION MUST BE not entered, but Data Element 47 (Age of
752 ENTERED WHEN AGE IS LESS Arrestee) is under 18. Whenever an arrestee’s
THAN 18 age indicates a juvenile, the agency must enter a
disposition.
Data Element 52 (Disposition of Juvenile) was
FOR AGE GREATER THAN 17 entered, but Data Element 47 (Age of Arrestee)
753 DISPOSITION SHOULD NOT BE is 18 or greater. Whenever an arrestee’s age
ENTERED indicates an adult, the agency cannot enter the
juvenile disposition because it does not apply.
Data Element 46 (Arrestee Was Armed With)
AUTOMATIC INDICATOR MUST
754 does not have A = Automatic or a blank in the
BE BLANK OR A
third position of field.
If Data Element 46 (Arrestee Was Armed With)
weapon is an Automatic, add A as the third
character of code; valid only with codes of:
11 = Firearm (Type Not Stated)
WEAPON TYPE MUST = 11, 12, 12 = Handgun
755 13, 14, OR 15 FOR AN A IN THE 13 = Rifle
AUTO INDICATOR 14 = Shotgun
15 = Other Firearm
A weapon code other than those mentioned was
entered with the automatic indicator. An
automatic weapon is, by definition, a firearm.
Data Element 47 (Age of Arrestee) does not
ARRESTEE AGE MUST BE
757 contain a numeric entry of 00 through 99 for an
NUMERIC DIGITS
exact age.
Data Element 48 (Sex of Arrestee) does not
contain a valid code of M = Male or F = Female.
758 INVALID ARRESTEE SEX VALUE
Note: that U = Unknown (if entered) is not a valid
sex for an arrestee.
The Group B Arrest Report (Level 7) submitted
as an A = Add is currently active in the FBI’s
database; therefore, it was rejected. If multiple
DUPLICATE GROUP B ARREST
759 arrestees are involved in the incident, ensure that
REPORT SEGMENT ON FILE
Data Element 40 (Arrestee Sequence Number) is
unique for each Arrestee Segment submitted so
that duplication does not occur.
Group B Arrest Reports (Level 7) must contain a
LEVEL 7 ARRESTS MUST HAVE A Group B Offense Code in Data Element 45 (UCR
760
GROUP B OFFENSE Arrest Offense). The offense code submitted is
not a Group B offense code.
Data Element 42 (Arrest Date) is missing for a
MISSING ARREST DATE FOR Group B Arrest Report with a Segment Action
797
DELETE OF GROUP B ARREST Type of D = Delete; must be populated with a
valid data value and cannot be blank.
MISSING ARREST DATE FOR Data Element 42 (Arrest Date) is missing for a
798
DELETE - ARREST Group B Arrest Report with a Segment Action
6/30/2023 2023.0 NIBRS Technical Specification 191
Group B Arrest Report Segment Errors
Error
Error Message Error Description
Number
TRANSACTION NUMBER Type of D = Delete; at least one Group B Arrest
MATCHES GROUP B ARREST Report is on file that matches Data Element 41
REPORT WITH ARREST DATE (Arrest Transaction Number) with an Arrest Date
OUTSIDE TWO YEAR WINDOW outside the two year window.
Data Element 42 (Arrest Date) is missing for a
MISSING ARREST DATE FOR
Group B Arrest Report with a Segment Action
DELETE-ARREST TRANSACTION
799 Type of D = Delete; multiple Group B Arrest
NUMBER MATCHES MULTIPLE
Reports are on file that match Data Element 41
GROUP B ARREST REPORTS
(Arrest Transaction Number).
5.2.9 Zero Report Segment Errors
Table 5-11 Zero Report Segment Errors
Error Error Message Error Description
Number
MUST BE POPULATED WITH A Mandatory Data Elements (Mandatory = Yes)
001 VALID DATA VALUE- must be populated with a valid data value and
MANDATORY FIELD cannot be blank.
CANNOT ADD ZERO REPORT - An agency cannot submit a Zero Report segment
028 GROUP A INCIDENT ON FILE when a Group A Incident Report is already on file
FOR THIS MONTH for the month/year.
CANNOT ADD ZERO REPORT- An agency cannot submit a Zero Report segment
029 GROUP B ARREST REPORT ON when a Group B Arrest Report is already on file for
FILE FOR THIS MONTH the month/year.
CANNOT DELETE ZERO REPORT An agency cannot delete a Zero Report when a
030 - GROUP A INCIDENT ON FILE Group A Incident was already on file for the
FOR THIS MONTH month.
CANNOT DELETE ZERO REPORT An agency cannot delete a Zero Report when a
031 - GROUP B INCIDENT ON FILE Group B Incident was already on file for the
FOR THIS MONTH month.
090 ZERO REPORT MONTH IS NOT Zero Report Month must be a valid month, data
01–12 values 01 through 12.
A Segment Level 0 was submitted that did not
091 ZERO-REPORTING YEAR IS
have four numeric digits in positions 40 through
INVALID
43.
092 ZERO REPORT INCIDENT Data Element 2 (Incident Number) in the Zero
NUMBER MUST BE ALL ZEROS Report Segment (Level 0) must contain 12 zeros.
ZERO REPORT MONTH/YEAR IS Zero Report Month and Zero Report Year cannot
093 PRIOR TO AGENCY precede the month and year in the date the LEA
CONVERSION TO THE NIBRS converted to NIBRS.
A Segment Level 0 was submitted with a month
ZERO REPORT MONTH/YEAR and year entered into positions 38 through 43 that
094 EXCEEDED MONTH/YEAR OF was later than the Month of Electronic submission
SUBMISSION and Year of Electronic submission entered into
positions 7 through 12.
6/30/2023 2023.0 NIBRS Technical Specification 192
Error Error Message Error Description
Number
The combined Zero Report Month and Zero
Report Year cannot be on or after the date a LEA
ZERO REPORT MONTH & ZERO is placed in Covered-by Status. When Zero Report
REPORT YEAR CANNOT BE ON data are received for a LEA in Covered-by Status,
096 OR AFTER DATE AGENCY IS the FBI will remove the agency from Covered-by
PLACED ON COVERED-BY Status, process the submission, and notify the
STATUS Agency. Additionally, adjustments to previously
submitted data from an agency now in Covered-by
Status will be processed and no error generated.
5.2.10 Data Quality Checks
The FBI’s UCR Program performs a series of data quality checks on the information that is
provided by the state UCR programs. Unlike an error, which stops the data from entering the
database completely, data quality checks are processed on data that has been accepted into the
system. In most cases, these checks are automated processes that look for data submissions that
are outside of the normal reporting parameters. This does not mean that the data is incorrect; it
simply means the data requires further analysis to ensure the information provided was accurate.
The table below addresses the warning number and a descriptions of the data quality checks that
are currently automated. The FBI’s UCR Program will be adding more data quality checks to this
table over time.
6/30/2023 2023.0 NIBRS Technical Specification 193
Warning Warning Message
Description
Number
A delete record was submitted but the incident
number matched more than one incident number
for that agency in our database. Multiple incidents
were totally removed from the database if no
DELETED MULTIPLE
1197 replacement incident was submitted on the current
INCIDENTS
file. If the incident number in question had a
replacement incident following the deletion record
on the current file, then multiple incidents were
removed and replaced with that incident.
Delete record was submitted with an incident date
INCIDENT DATE IN DELETE
that does not match the incident date on the
1198 DOES NOT MATCH INCIDENT
previously submitted incident that resides in our
DATE ON FILE
database.
The burglary incident referenced has a Data
WARNING - BURGLARY Element 9 (Location Type) of 14 = Hotel/Motel Etc.
INCIDENTS WITH LOCATION or 19 = Rental Storage Facility and 99 in Data
1201
14/19 AND 14/19/99 Element 10 (Number of Premises Entered). Please
PREMISES ENTERED verify the location and/or number of premises
entered is correct.
Homicides and Negligent Manslaughters are being
reported which occurred with a motor vehicle in
Data Element 13 (Type Weapon/Force Involved).
WARNING - HOMICIDE OR
The offenses of Homicide and Negligent
MANSLAUGHTER INCIDENTS
1202 Manslaughter does not include accidental traffic
WITH VEHICLE WEAPON
fatalities. Negligent Homicide offenses using a
TYPE
vehicle/vessel are valid in fatalities involving
driving under the influence, cell/smart phone use,
or reckless driving incidents.
Data Value 40 = Personal Weapons and/or
99 = None are being reported in Data Element 13
(Type Weapon/Force Involved). These weapon
WARNING - WEAPONS LAW types do not meet the criteria for this offense.
1203 OFFENSES WITH PERSONAL Weapon Law Violations are defined as the
WEAPONS violation of laws or ordinances prohibiting the
manufacture, sale, purchase, transportation,
possession, concealment or use of firearms,
cutting instruments, explosives, incendiary devices
or other deadly weapons.
Agencies are reporting Data Element 25 (Type of
Victim) Robberies with only a business as the
victim. The victims of a robbery include not only
WARNING - ROBBERY
those persons and other entities (businesses,
1204 INCIDENTS WITH NO
financial institutions, etc.) from whom property was
INDIVIDUAL VICTIM
taken (or was attempted to be taken), but also
those persons toward whom the robber(s) directed
force or threat of force in perpetrating the offense.
The offense has Data Element 13 (Type
WARNING - OFFENSE Weapon/Force Involved) with a weapon indicator
1209 CONTAINS AUTOMATIC of A = Automatic, e.g., 13A = Automatic Rifle. An
WEAPONS automatic firearm is defined as any firearm which
shoots, or is designed to shoot, more than one
6/30/2023 2023.0 NIBRS Technical Specification 194
shot at a time by a single pull of the trigger without
manual reloading. Please verify the weapon was
an automatic firearm.
Data Element 8A (Bias Motivation) indicates a
WARNING - INCIDENT Bias code 99 = Unknown and indicates a
1220 REPORTED WITH BIAS CODE suspected Hate Crime bias and should be
99 OR UNKNOWN resubmitted after investigation, either as
88 = None (no bias), or the appropriate bias code.
Data Element 8A (Bias Motivation) was entered
WARNING - INCIDENT
with multiple bias codes (up to 5). Please verify
1221 REPORTED WITH MULTIPLE
that the multiple bias codes are correct as
BIAS CODES
reported.
WARNING - INCIDENT Data Element 6 (UCR Offense Code)
CONTAINS AN OFFENSE OF 09A = Murder and Nonnegligent Manslaughter
MURDER AND with a valid bias code(s) in Data Element 8A (Bias
1222 NONNEGLIGENT Motivation) other than 88 = None (no bias).
MANSLAUGHTER Please verify that the incident is correct as
ASSOCIATED WITH HATE reported.
CRIME
Data Element 6 (UCR Offense Code)
WARNING - INCIDENT
11A = Rape with a valid bias code(s) in Data
REPORTED WITH OFFENSE
1223 Element 8A (Bias Motivation) other than 88 =
RAPE ASSOCIATED WITH
None (no bias). Please verify that the incident is
HATE CRIME
correct as reported.
Data Element 6 (UCR Offense Code)
WARNING - INCIDENT
11B = Sodomy with a valid bias code(s) in Data
REPORTED WITH OFFENSE
1224 Element 8A (Bias Motivation) other than
SODOMY ASSOCIATED WITH
88 = None (no bias). Please verify that the incident
HATE CRIME
is correct as reported.
WARNING - INCIDENT Data Element 6 (UCR Offense Code)
REPORTED WITH OFFENSE 11C = Sexual Assault With An Object with a valid
1225 SEXUAL ASSAULT WITH AN bias code(s) in Data Element 8A (Bias Motivation)
OBJECT ASSOCIATED WITH other than 88 = None (no bias). Please verify that
HATE CRIME the incident is correct as reported.
WARNING - INCIDENT Data Element 6 (UCR Offense Code) has multiple
REPORTED WITH MULTIPLE offense segments associated with Data Element
1226 OFFENSE SEGMENTS 8A (Bias Motivation) other than 88 = None (no
ASSOCIATED WITH A HATE bias). Please verify that the incident is correct as
CRIME reported.
Data Value 77 = Other; all property not fitting any
of the other specific descriptions) is being listed in
Data Element 15 (Property Description). Although
it is not uncommon to encounter “other property”
as the only property being burned, etc., the
WARNING - ARSON
incidents contained large dollar values. When
PROPERTY TYPE 77 OTHER
1302 utilizing property description 77 = Other up to ten
WITH HIGH DOLLAR VALUES
property descriptions can be entered for each
- 10,000
Property Segment (i.e., each type of property
loss/etc.) involved in the incident. If more than ten
types of property are involved, the nine most
valuable specifically codable types of property
should be entered and the remaining types of
6/30/2023 2023.0 NIBRS Technical Specification 195
property should be combined and entered as
77 = Other.
The incidents of Burglary also contain a larceny-
theft. Offenses locally known as burglary (any
degree); unlawful entry with intent to commit a
larceny or felony; breaking and entering with intent
WARNING - LARCENY WITH
1303 to commit a larceny; housebreaking; and
BURGLARY
safecracking should be classified as burglary.
Burglary is defined in terms of theft, therefore only
the burglary is to be reported, not the
accompanying Larceny.
In Data Element 15 (Property Description) the
stolen property being reported is 01 = Aircraft. It is
WARNING - LARCENY THEFT
1304 uncommon in an offense of larceny-theft to contain
- AIRCRAFT
an aircraft as the stolen property in the property
description.
In Data Element 15 (Property Description) the
stolen property being reported is improbable;
01 = Aircraft
03 = Automobiles
05 = Buses
12 = Farm Equipment
13 = Firearms
15 = Heavy Construction/Industrial Equipment
18 = Livestock
24 = Other Motor Vehicles
28 = Recreational Vehicles
29 = Structures-single dwellings
30 = Structures-other dwellings
31= Structures-other commercial/business
32= Structures-industrial/manufacturing
WARNING - LARCENY THEFT 33 = Structures-public/community
1305
- COIN OPERATED MACHINE
34 = Structures-storage
35 = Structures-other
37 = Trucks
39 = Watercraft
43 = Building Materials
47 = Crops
49 = Explosives
64 = Fuel
65 = Identity Documents
66 = Identity-Intangible
67 = Law Enforcement Equipment
68 = Lawn/Yard/Garden Equipment
69 = Logging Equipment
71 = Metals, Non-Precious
72 = Musical Instruments
6/30/2023 2023.0 NIBRS Technical Specification 196
Incidents of larceny-theft with Commercial/
Business, Single Occupancy Dwellings, Other
Dwellings, Industrial/Manufacturing, and
WARNING - LARCENY THEFT
1306 Public/Community are reported as stolen property
- STOLEN STRUCTURES
in Data Element 15 (Property Description). It is
uncommon for an offense of larceny-theft to
contain a structure as the stolen property.
Stolen property 99 = Blank is being reported in
Data Element 15 (Property Description);
WARNING - SPECIAL 99 = Blank is a special data value which will
1307
PROPERTY CODE - 99 capture statistics on certain theft fads, i.e., pet
rocks, if necessary. The FBI does not currently use
this code.
WARNING - MOTOR VEHICLE Data Element 18 (Number of Motor Vehicles
THEFT INCIDENTS WITH Stolen) is greater than five. Please verify the
1308
GREATER THAN 5 VEHICLES number of vehicles stolen.
STOLEN
Data Element 15 (Property Description)
WARNING - CREDIT
09 = Credit/Debit Cards are being reported stolen.
1310 CARD/AUTOMATIC TELLER
The fraudulent use of the credit/debit card should
MACHINE FRAUD
be reported, and not the theft of the card.
There are a number of entries for Property
Description (Data Element 15) 26 = Radios/TVs/
VCRs being reported. The 23F = Theft From Motor
WARNING - LARCENY-THEFT Vehicle is the theft of articles from a motor vehicle
1312 23F AND 23G - and the 23G = Theft of Motor Vehicle Parts and
RADIOS/TVs/VCRs Accessories is the theft of any part or accessory
affixed to the interior or exterior of a motor vehicle
necessary for its operation.
Data Element 12 (Type Criminal Activity) is
reported as P = Possessing/Concealing with Data
WARNING - DRUG Element 14 (Type Property Loss) 1 = None.
1314
EQUIPMENT VIOLATIONS Typically with this Type of Criminal Activity, the
Type of Property Loss is 5 = Recovered or
6 = Seized.
Data Element 22 (Type Drug Measurement)
DU = Dosage Unit is being used for crack,
WARNING - DRUG QUANTITY cocaine, and marijuana. Usually a weight
1316 MEASUREMENTS OF measurement like GM = Gram, KG = Kilogram,
DOSAGE UNIT OZ = Ounce, or LB = Pound is used. The
NP = Number of Plants is sometimes used for
marijuana.
When Data Element 15 (Property Description)
contains a value that exceeds an FBI-assigned
threshold amount, a warning message will be
WARNING - PROPERTY DESC created. The participant is asked to check to see if
(15) HAD VALUE (16) THAT the value entered was a data entry error, or if it
1342 EXCEEDED THRESHOLD OF was intended to be entered. A warning message is
$1,000,000 always produced when the value is $1,000,000 or
greater. For example, if the value of a property is
$12,000.99 but is inadvertently entered as
$1,200,099 in the computer record sent to the FBI,
6/30/2023 2023.0 NIBRS Technical Specification 197
the FBI will generate a warning message. In this
case, the cents were entered as whole dollars.
A warning is generated when the incident contains
an Offense Segment where Data Element 6 (UCR
Offense Code) is 280 = Stolen Property Offense,
another Offense Segment where Data Element 6
(UCR Offense Code) is 240 = Motor Vehicle Theft,
a Property Segment where Data Element 14 (Type
Property Loss/Etc.) is 5 = Recovered and Data
Element 15 (Property Description) is a vehicle (see
below for vehicle property descriptions), but no
Property Segment exist where Data Element 14
(Type Property Loss) is 7 = Stolen/Etc. and Data
WARNING - 280 OFFENSE Element 15 (Property Description) is a vehicle.
HAS RECOVERED VEHICLE
1343
BUT 240 DOESNT SHOW Data Element 15 (Property Description) for
STOLEN vehicles:
03 = Automobiles
05 = Buses
24 = Other Motor Vehicles
28 = Recreational Vehicles
37 = Trucks
The agency should review the incident. If there
was indeed a stolen vehicle, the agency should
resubmit the incident to reflect both stolen and
recovered vehicles.
WARNING - CONTAINS NON- Contains nonnumeric entry; must be zero left fill.
1350 NUMERIC ENTRY - MUST BE
ZERO LEFT FILL
Data Element 35 (Relationship of Victim to
Offender) is nonfamily. Incest is the sexual
WARNING - INCEST intercourse between persons who are related to
1401 WITHOUT FAMILY each other within the degrees wherein marriage is
RELATIONSHIP prohibited by law. Because the relationship is
nonfamily, the agency should classify the offense
as a Statutory Rape and/or Rape.
Statutory rape is the sexual intercourse with a
WARNING - STATUTORY person who is under the statutory age of consent.
1402 RAPE WITH VICTIMS UNDER Based upon Data Element 26 (Age of Victim), the
AGE 13 FBI is questioning if the child is capable of giving
consent.
The Relationship of Data Element 35 (Victim to
Offender) is a family member. Statutory Rape is
WARNING - STATUTORY
the sexual intercourse with a person who is under
1403 RAPE WITH VICTIM AS
the statutory age of consent. Based upon the
FAMILY MEMBER
definition of Statutory Rape, the agency should
classify these incidents as Incest or Rape.
WARNING - AGGRAVATED Incidents are being reported in Data Element 33
ASSAULT WITH MINOR OR (Type Injury) where the victim sustained minor or
1404 no injuries and either personal or no weapons
NO INJURY AND PERSONAL
OR NO WEAPONS were involved.
6/30/2023 2023.0 NIBRS Technical Specification 198
Aggravated Assault is an unlawful attack by one
person upon another wherein the offender uses a
weapon or displays it in a threatening manner, or
the victim suffers obvious severe or aggravated
bodily injury involving apparent broken bones, loss
of teeth, possible internal injury, severe laceration,
or loss of consciousness.
Based on the definition, the agency should classify
these as Simple Assaults.
The victims sustained minor injuries, but there
WARNING - SIMPLE ASSAULT were no weapons used when the assaults were
1405 WITH INJURY AND NO committed. At the very least, the weapon reported
WEAPON should be 40 = Personal Weapons.
Incidents are being reported with unknown victim
information in Data Element 26 (Age of Victim),
Data Element 27 (Sex of Victim), and Data
Element 28 (Race of Victim). Generally, the victim
WARNING - UKNOWN VICTIM information should be known. If the agency cannot
1407
INFORMATION determine an exact age, the agency may enter an
age range to approximate the victim’s age. The
age, sex, and race of victims provide important
statistical information, and every effort should be
made to collect this data.
WARNING - PROPERTY Please verify Data Element 26 (Age of Victim).
1408 CRIME WITH THE ONLY The only victim is under the age of 7 and listed as
VICTIM UNDER AGE 7 the victim of a property crime.
WARNING - VICTIM IS If Data Element 25 (Type Victim) is L = Law
OFFICER OF ASSAULT OR Enforcement Officer, then one of the two possible
HOMICIDE WITHOUT VICTIM Data Element 31 (Aggravated Assault/Homicide
1409
CIRCUMSTANCE BEING Circumstances) should be 02 = Assault on Law
ASSAULT ON LAW Enforcement Officer.
ENFORCEMENT OFFICER
Data Element 35 (Relationship of Victim to
Offender) is:
CH = Child
PA = Parent
WARNING - CHILD/PARENT GP = Grandparent
1413 RELATIONSHIPS WITH GC = Grandchild
POSSIBLE AGE PROBLEMS SP = Step-parent
SC = Step-child
CF = Child of Boyfriend/Girlfriend
The age difference between the victim and the
offender was less than 11 years.
Data Element 25 (Type of Victim) is S = Society
WARNING - INCIDENT
and Data Element 8A (Bias Motivation) is other
1427 REPORTED WITH SOCIETY
than 88 = None (no bias). Please verify that the
AS VICTIM OF A HATE CRIME
incident is correct as reported.
WARNING – VICTIM HAD AGE The agencies may have a reporting problem when
1441
OVER 98 utilizing Data Element 26 (Age of Victim). The
6/30/2023 2023.0 NIBRS Technical Specification 199
agency may be misusing the age code of 99 when
the age is 00 = Unknown.
Data Element 26 (Age of Victim) cannot be 13, 14,
WARNING - VICTIM IS
15, 16, or 17 when Data Element 35 (Relationship
1449 SPOUSE BUT AGE IS LESS
of Victim to Offender) contains a relationship of
THAN 18
SE = Spouse.
Data Element 26 (Age of Victim) was submitted
WARNING - VICTIM AGE
1451 with an unreasonable range span from the
RANGE OF 01-98 AND 01-99
youngest age of 01 to the oldest age of 98 or 99.
The agencies may have a reporting problem when
WARNING - AGE OF using Data Element 37 (Age of Offender). The
1501
OFFENDER LESS THAN 3 agency may be confusing the age code of 01 and
02 as the Victim/Offender Sequence Number.
Incidents involve Data Element 37 (Age of
Offender) ranging from 1 to 12 years of age.
Fondling is the touching of the private body parts
WARNING - FONDLING WITH of another person for the purpose of sexual
1508
OFFENDERS UNDER AGE 13 gratification, without the consent of the victim,
including instances where the victim is incapable
of giving consent because of his/her temporary or
permanent mental or physical incapacity.
Please verify Data Element 37 (Age of Offender).
WARNING - VIOLENT CRIME
1509 The offender is listed as under age 11 and the
WITH OFFENDER UNDER 11
offense is homicide, rape, or robbery.
The agency may have a reporting problem when
WARNING – OFFENDER HAD using Data Element 37 (Age of Offender). The
1541
AGE OVER 98 agency may be misusing the age code of 99 when
the age is 00 = Unknown.
Data Element 37 (Age of Offender) cannot be 13,
WARNING–OFFENDER IS
14, 15, 16, or 17 when Data Element 35
1549 SPOUSE, BUT AGE IS LESS
(Relationship of Victim to Offender) contains a
THAN 18
relationship of SE = Spouse.
Data Element 37 (Age of Offender) was submitted
WARNING - OFFENDER AGE
1551 with an unreasonable range span from the
RANGE OF 01-98 AND 01-99
youngest age of 01 to the oldest age of 98 or 99.
The agency may have a reporting problem when
WARNING - AGE OF using Data Element 47 (Age of Arrestee). The
1601
ARRESTEE LESS THAN 3 agency may be confusing the age code of 01, 02,
and 03 as the Victim/Offender Sequence Number.
Data Element 36 (Offender Sequence Number)
are being reported as 01, 02, etc. with Data
Element 37 (Unknown Offender Age), Data
WARNING - OFFENDER
Element 38 (Sex of Offender), and Data Element
SEQUENCE NUMBER WITH
1607 39 (Race of Offender). If nothing is known about
ALL UNKNOWN
the offender(s), the agency should enter 00 =
INFORMATION
Unknown in Data Element 36 (Offender Sequence
Number), and Data Elements 37 through 39
should be blank.
Please verify Data Element 47 (Age of Arrestee).
WARNING - DUI WITH
1608 The arrestee is listed as under age 13 and the
ARRESTEE UNDER 13
offense is driving under the influence.
6/30/2023 2023.0 NIBRS Technical Specification 200
Please verify Data Element 47 (Age of Arrestee).
WARNING - VIOLENT CRIME
1609 The arrestee is listed as under age 11 and the
WITH ARRESTEE UNDER 11
offense is homicide, rape, or robbery.
Data Element 52 (Disposition of Arrestee Under
18) was not entered, but Data Element 47 (Age of
Arrestee) indicates an age range for a juvenile.
The low age is a juvenile and the high age is an
WARNING - NO DISPOSITION adult, but the average age is a juvenile.
1640 FOR POSSIBLE JUVENILE Note: When an age range is not entered and the
ARRESTEE age is a juvenile, then the disposition must be
entered. The computer these circumstances as a
possible discrepancy between age and disposition
and should be checked for possible correction by
the participant.
Data Element 47 (Age of Arrestee) was entered
with a value of 99 which means the arrestee was
WARNING - ARRESTEE HAD
1641 over 98 years old. Verify that the submitter of data
AN AGE OF 99 OR OLDER
is not confusing the 99 = Over 98 Years Old with
00 = Unknown.
Data Element 47 (Age of Arrestee) in a Group A
WARNING - ARRESTEE AGE Incident Report was submitted with an
1651
RANGE OF 01-98 AND 01-99 unreasonable range span from the youngest age
of 01 to the oldest age of 98 or 99.
WARNING - AGE OF The agency may have a reporting problem when
1701
ARRESTEE LESS THAN 3 using Data Element 47 (Age of Arrestee).
Please verify Data Element 47 (Age of Arrestee).
WARNING - DUI WITH
1708 The arrestee is listed as under age 13, and the
ARRESTEE UNDER 13
offense is driving under the influence.
Data Element 52 (Disposition of Arrestee Under
18) was not entered, but Data Element 47 (Age of
Arrestee) indicates an age range for a juvenile.
The low age is a juvenile and the high age is an
WARNING - NO DISPOSITION adult, but the average age is a juvenile.
1740 FOR POSSIBLE JUVENILE Note: When an age range is not entered and the
ARRESTEE age is a juvenile, the disposition must be entered.
The computer flagged these circumstances as
a possible discrepancy between age and
disposition and should be checked for possible
correction by the participant.
Data Element 47 (Age of Arrestee) was entered
with a value of 99, which means the arrestee is
WARNING - ARRESTEE IS
1741 over 98 years old. The submitter should verify that
OVER AGE 98
99 = Over 98 Years Old is not being confused with
00 = Unknown.
Data Element 47 (Age of Arrestee) in a Group B
WARNING - ARRESTEE AGE arrest was submitted with an unreasonable range
1751
RANGE OF 01-98 AND 01-99 span from the youngest age of 01 to the oldest
age of 98 or 99.
6/30/2023 2023.0 NIBRS Technical Specification 201
6 RECORD LAYOUTS
6.1 Administrative Segment Layout (Level 1)
Segment Length: 0087 (without Cargo Theft)
0088 (with Cargo Theft)
0088 (Federal Agency Reporting Only - Judicial District Code)
*NOTE: The Line Length for Federal Agency will be 91 characters long; however, the Segment Length for the
transaction will be 0088.
SEGMENT INCIDENT
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2)
1-4 5 6 7-8 9-12 13-16 17-25 26-37
DATA ELEMENT 3 INCLUDES 3 ELEMENTS
REPORT EXCEPTIONAL
INCIDENT DATE INCIDENT CLEARED CLEARANCE
DATE INDICATOR HOUR EXCEPTIONALLY DATE
(3) (3) (3) (4) (5)
38-45 46 47-48 49 50-57
FEDERAL
AGENCY
EXCEPTIONAL CLEARANCE OFFENSE CODE REPORTING
OCCURS 10 TIMES OPTIONAL ONLY
EXCEPTIONAL EXCEPTIONAL FEDERAL
CLEARNCE CLEARANCE CARGO JUDICIAL
OFFENSE CODE THROUGH OFFENSE CODE THEFT DISTRICT
#1 #10 (2A) CODE (A1)
58-60 85-87 88 89-91
Figure 6-1 Administrative Segment Layout (Level 1)
6/30/2023 2023.0 NIBRS Technical Specification 202
6.2 Offense Segment Layout (Level 2)
Segment Length: 0063 (1 Bias Motivation)
0071 (5 Bias Motivations)
UCR OFFENSE
SEGMENT YEAR OF INCIDENT OFFENSE ATTEMPTED/
SEGMENT SEGMENT ACTION MONTH OF SUBMISSIO CITY ORI NUMBER CODE COMPLETED
LENGTH LEVEL TYPE SUBMISSION N INDICATOR (1) (2) (6) (7)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-40 41
DATA ELEMENT 8 OCCURS 3 TIMES NUMBER DATA ELEMENT 12 OCCURS 3 TIMES
OFFENDER OFFENDER OF TYPE TYPE
SUSPECTED SUSPECTED LOCATION PREMISES METHOD CRIMINAL CRIMINAL
OF USING #1 THROUGH OF USING #3 TYPE ENTERED OF ENTRY ACTIVITY #1 THROUGH ACTIVITY #3
(8) (8) (9) (10) (11) (12) (12)
42 44 45-46 47-48 49 50 52
DATA ELEMENT 13 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 3 TIMES
TYPE
WEAPON AUTOMATIC TYPE WEAPON AUTOMATIC
FORCE WEAPON FORCE WEAPON
THROUGH
INVOLVED #1 INDICATOR #1 INVOLVED #3 INDICATOR #3
(13) (13) (13) (13)
53-54 55 59-60 61
BIAS MOTIVATION #2 - #5 ARE OPTIONAL
DATA ELEMENT 8A OCCURS 4 TIMES
BIAS BIAS BIAS
MOTIVATION #1 MOTIVATION #2 THROUGH MOTIVATION #5
(8A) (8A) (8A)
62-63 64-65 70-71
Figure 6-2 Offense Segment Layout (Level 2)
6/30/2023 2023.0 NIBRS Technical Specification 203
6.3 Property Segment Layout (Level 3)
Segment Length: 0307
TYPE
SEGMENT INCIDENT PROPERTY
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER LOSS/ETC
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (14)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38
DATA ELEMENTS 15, 16, & 17 AS A GROUP OCCUR 10 TIMES
PROPERTY VALUE OF DATE PROPERTY VALUE OF DATE
DESCRIPTION #1 PROPERTY #1 RECOVERED #1 THROUGH DESCRIPTION #10 PROPERTY #10 RECOVERED
(15) (16) (17) (15) (16) #10 (17)
39-40 41-49 50-57 210-211 212-220 221-228
NUMBER OR NUMBER OF DATA ELEMENTS 20, 21, & 22 AS A GROUP OCCUR 3 TIMES
STOLEN RECOVERED ESTIMATED
MOTOR MOTOR SUSPECTED DRUG TYPE DRUG
VEHICLES VEHICLES DRUG TYPE #1 QUANTITY #1 MEASUREMENT #1 THROUGH
(18) (19) (20) (21) (22)
229-230 231-232 233 234-245 246-247
DATA ELEMENTS 20,21, & 22
ESTIMATED
SUSPECTED DRUG TYPE DRUG
DRUG TYPE #3 QUANTITY #3 MEASUREMENT #3
(20) (21) (22)
263 264-275 276-277 278-307
Figure 6-3 Property Segment Layout (Level 3)
6/30/2023 2023.0 NIBRS Technical Specification 204
6.4 Victim Segment Layout (Level 4)
Segment Length: 0129 (without LEOKA)
0141 (with LEOKA)
VICTIM
SEGMENT INCIDENT SEQUENCE
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (23)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-40
DATA ELEMENT 24 OCCURS 10 TIMES
VICTIM CONNECTED VICTIM CONNECTED TO TYPE OF AGE OF SEX OF RACE OF ETHNICITY
TO UCR OFFENSE #1 THROUGH UCR OFFENSE #10 VICTIM VICTIM VICTIM VICTIM OF VICTIM
(24) (24) (25) (26) (27) (28) (29)
41-43 68-70 71 72-75 76 77 78
RESIDENT DATA ELEMENT 31 OCCURS 2 TIMES ADDITIONAL DATA ELEMENT 33 OCCURS 5 TIMES
STATUS AGGRAVATED AGGRAVATED JUSTIFIABLE
OF ASSAULT/HOMICIDE ASSAULT/HOMICIDE HOMICIDE TYPE TYPE
VICTIM CIRCUMSTANCES #1 CIRCUMSTANCES #2 CIRCUMSTANCES INJURY #1 THROUGH INJURY #5
(30) (31) (31) (32) (33) (33)
79 80-81 82-83 84 85 89
DATA ELEMENTS 34 & 35 AS A GROUP OCCUR 10 TIMES LEOKA DATA ELEMENTS ARE OPTIONAL
OFFENDER RELATIONSHIP OFFENDER RELATIONSHIP TYPE OF OFFICER OFFICER OFFICER –
NUMBER TO BE OF VICTIM TO NUMBER TO BE OF VICTIM TO ACTIVITY/ ASSIGNMENT ORI OTHER
RELATED #1 OFFENDER #1 THROUGH RELATED #10 OFFENDER #10 CIRCUMSTANCE TYPE JURISDICTION
(34) (35) (34) (35) (25A) (25B) (25C)
90-91 92-93 126-127 128-129 130-131 132 133-141
Figure 6-4 Victim Segment Layout (Level 4)
6/30/2023 2023.0 NIBRS Technical Specification 205
6.5 Offender Segment Layout (Level 5)
Segment Length: 0045 (without Offender Ethnicity)
0046 (with Offender Ethnicity)
INCIDENT
SEGMENT SEGMENT SEGMENT MONTH OF YEAR OF CITY ORI NUMBER
LENGTH LEVEL ACTION TYPE SUBMISSION SUBMISSION INDICATOR (1) (2)
1-4 5 6 7-8 9-12 13-16 17-25 26-37
OFFENDER OPTIONAL
SEQUENCE AGE OF SEX OF RACE OF ETHNICITY OF
NUMBER OFFENDER OFFENDER OFFENDER OFFENDER
(36) (37) (38) (39) (39A)
38-39 40-43 44 45 46
Figure 6-5 Offender Segment Layout (Level 5)
6/30/2023 2023.0 NIBRS Technical Specification 206
6.6 Arrestee Segment Layout (Level 6)
Segment Length: 0110
ARRESTEE ARREST
SEGMENT INCIDENT SEQUENCE TRANSACTION
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER NUMBER
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) (40) (41)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-51
MULTIPLE UCR DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE ARREST ARRESTEE AUTOMATIC ARRESTEE AUTOMATIC
ARREST TYPE OF SEGMENTS OFFENSE WAS ARMED WEAPON WAS ARMED WEAPON
DATE ARREST INDICATOR CODE WITH #1 INDICATOR #1 WITH #2 INDICATOR #2
(42) (43) (44) (45) (46) (46) (46) (46)
52-59 60 61 62-64 65-66 67 68-69 70
RESIDENT DISPOSITION
AGE OF SEX OF RACE OF ETHNICITY OF STATUS OF OF ARRESTEE
ARRESTEE ARRESTEE ARRESTEE ARRESTEE ARRESTEE UNDER 18 CLEARANCE
(47) (48) (49) (50) (51) (52) INDICATOR
71-74 75 76 77 78 79 80
CLEARANCE OFFENSE CODE OCCURS 10 TIMES
CLEARANCE
CLEARANCE
OFFENSE OFFENSE
THROUGH
CODE #1 CODE #10
81-83 108-110
Figure 6-6 Arrestee Segment Layout (Level 6)
6/30/2023 2023.0 NIBRS Technical Specification 207
6.7 Group B Arrest Report Segment Layout (Level 7)
Segment Length: 0066 (State, Local, and Tribal)
0066 (Federal Agency Reporting Only - Judicial District Code)
*NOTE: The Line Length for Federal Agency will be 69 characters long; however, the Segment Length of the
transaction will be 0066.
ARREST ARRESTEE
SEGMENT TRANSACTION SEQUENCE ARREST
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER NUMBER DATE
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (41) (40) (42)
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-47
UCR DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARREST ARRESTEE AUTOMATIC ARRESTEE AUTOMATIC
TYPE OF OFFENSE WAS ARMED WEAPON WAS ARMED WEAPON AGE OF SEX OF
ARREST CODE WITH #1 INDICATOR #1 WITH #2 INDICATOR #2 ARRESTEE ARRESTEE
(43) (45) (46) (46) (46) (46) (47) (48)
48 49-51 52-53 54 55-56 57 58-61 62
FEDERAL
AGENCY
REPORTING
ONLY
RESIDENT DISPOSITION FEDERAL
RACE OF ETHNICITY OF STATUS OF OF ARRESTEE JUDICIAL
ARRESTEE ARRESTEE ARRESTEE UNDER 18 DISTRICT
(49) (50) (51) (52) CODE (A1)
63 64 65 66 67-69
Figure 6-7 Group B Arrest Report Segment Layout (Level 7)
6/30/2023 2023.0 NIBRS Technical Specification 208
6.8 Zero Report Segment Layout (Level 0)
Segment Length: 0043
SEGMENT INCIDENT ZERO ZERO
SEGMENT SEGMENT ACTION MONTH OF YEAR OF CITY ORI NUMBER REPORT REPORT
LENGTH LEVEL TYPE SUBMISSION SUBMISSION INDICATOR (1) (2) MONTH YEAR
1-4 5 6 7-8 9-12 13-16 17-25 26-37 38-39 40-43
Figure 6-8 Zero Report Segment Layout (Level 0)
6.9 EDS Layout
Segment Length: 0146
SUBMISSIO SEGMENT UCR PERSON TYPE
MONT N RECORD ACTION INCIDENT SEGMENT OFFENSE SEQUENCE PROPERTY
YEAR H NUMBER TYPE ORI NUMBER LEVEL CODE NUMBER LOSS/ETC.
1-4 5-6 7-13 14 15-23 24-35 36 37-39 40-42 43
DATA
ELEMENT ERROR DATA VALUE ERROR UNUSED
NUMBER NUMBER IN ERROR MESSAGE FIELD
44-46 47-49 50-61 62-140 141-146
Figure 6-9 EDS Layout
6/30/2023 2023.0 NIBRS Technical Specification 209
6.10 WDS Layout
Segment Length: 0149
SUBMISSION SEGMENT UCR PERSON TYPE
REPORT REPORT INCIDENT PUBLICATION SEGMENT
RECORD ACTION ORI OFFENSE SEQUENCE PROPERTY
YEAR MONTH NUMBER EFFECT LEVEL
NUMBER TYPE CODE NUMBER LOSS/ETC.
15-
1-4 5-6 7-13 14 24-35 36 37-39 40 41-43 44
23
VIOLATION VIOLATION
DATA ELEMENT NUMBER DATA VALUE IN VIOLATION
NUMBER MESSAGE
45-47 48-59 60-71 72-149
Figure 6-10 WDS Layout
6/30/2023 2023.0 NIBRS Technical Specification 210
OFFENSE CODES
A.1 Group A Offenses
Group A Offenses
Offense Code Offense Description Crime Against
Animal Cruelty Offenses 720 Animal Cruelty Society
Arson 200 Arson Property
Assault Offenses 13A Aggravated Assault Person
Assault Offenses 13B Simple Assault Person
Assault Offenses 13C Intimidation Person
Bribery 510 Bribery Property
Burglary/Breaking & Entering 220 Burglary/Breaking & Entering Property
Commerce Violations 58A Import Violations* Society
Commerce Violations 58B Export Violations* Society
Commerce Violations 61A Federal Liquor Offenses* Society
Commerce Violations 61B Federal Tobacco Offenses* Society
Commerce Violations 620 Wildlife Trafficking* Society
Counterfeiting/Forgery 250 Counterfeiting/Forgery Property
Destruction/Damage/Vandalism Destruction/Damage/Vandalism
290 Property
of Property of Property
Drug/Narcotic Offenses 35A Drug/Narcotic Violations Society
Drug/Narcotic Offenses 35B Drug Equipment Violations Society
Embezzlement 270 Embezzlement Property
Espionage 103 Espionage* Society
Extortion/Blackmail 210 Extortion/Blackmail Property
6/30/2023 2023.0 NIBRS Technical Specification A-1
Group A Offenses
Offense Code Offense Description Crime Against
False
Fraud Offenses 26A Pretenses/Swindle/Confidence Property
Game
Credit Card/Automated Teller
Fraud Offenses 26B Property
Machine Fraud
Fraud Offenses 26C Impersonation Property
Fraud Offenses 26D Welfare Fraud Property
Fraud Offenses 26E Wire Fraud Property
Fraud Offenses 26F Identity Theft Property
Fraud Offenses 26G Hacking/Computer Invasion Property
Fraud Offenses 26H Money Laundering* Society
Gambling Offenses 39A Betting/Wagering Society
Operating/Promoting/Assisting
Gambling Offenses 39B Society
Gambling
Gambling Equipment
Gambling Offenses 39C Society
Violations
Gambling Offenses 39D Sports Tampering Society
Murder & Nonnegligent
Homicide Offenses 09A Person
Manslaughter
Homicide Offenses 09B Negligent Manslaughter Person
Homicide Offenses 09C Justifiable Homicide Not a Crime
Illegal Entry into the United
Immigration Violations 30A Society
States*
Immigration Violations 30B False Citizenship* Society
Immigration Violations 30C Smuggling Aliens* Society
6/30/2023 2023.0 NIBRS Technical Specification A-2
Group A Offenses
Offense Code Offense Description Crime Against
Immigration Violations 30D Re-entry after Deportation* Society
Human Trafficking,
Human Trafficking 64A Person
Commercial Sex Acts
Human Trafficking,
Human Trafficking 64B Person
Involuntary Servitude
Kidnapping/Abduction 100 Kidnapping/Abduction Person
Harboring Escapee/ Concealing
Fugitive Offenses 49A Society
from Arrest*
Fugitive Offenses 49B Flight to Avoid Prosecution* Society
Fugitive Offenses 49C Flight to Avoid Deportation* Society
Larceny/Theft Offenses 23A Pocket-picking Property
Larceny/Theft Offenses 23B Purse-snatching Property
Larceny/Theft Offenses 23C Shoplifting Property
Larceny/Theft Offenses 23D Theft From Building Property
Theft From Coin-Operated
Larceny/Theft Offenses 23E Property
Machine or Device
Larceny/Theft Offenses 23F Theft From Motor Vehicle Property
Theft of Motor Vehicle Parts or
Larceny/Theft Offenses 23G Property
Accessories
Larceny/Theft Offenses 23H All Other Larceny Property
Motor Vehicle Theft 240 Motor Vehicle Theft Property
Pornography/Obscene Material 370 Pornography/Obscene Material Society
Prostitution Offenses 40A Prostitution Society
Assisting or Promoting
Prostitution Offenses 40B Society
Prostitution
6/30/2023 2023.0 NIBRS Technical Specification A-3
Group A Offenses
Offense Code Offense Description Crime Against
Prostitution Offenses 40C Purchasing Prostitution Society
Robbery 120 Robbery Property
Sex Offenses 11A Rape Person
Sex Offenses 11B Sodomy Person
Sex Offenses 11C Sexual Assault With An Object Person
Sex Offenses 11D Fondling Person
Sex Offenses 36A Incest Person
Sex Offenses 36B Statutory Rape Person
Sex Offenses 360 Failure to Register as a Sex Society
Offender*
Stolen Property Offenses 280 Stolen Property Offenses Property
Treason 101 Treason* Society
Weapon Law Violations 520 Weapon Law Violations Society
Violation of National Firearm
Weapon Law Violations 521 Society
Act of 1934*
Weapon Law Violations 522 Weapons of Mass Destruction* Society
Weapon Law Violations 526 Explosives* Society
6/30/2023 2023.0 NIBRS Technical Specification A-4
A.2 Group B Offenses
Group B Offenses
Offense Code Offense Description Crime Against
Curfew/Loitering/ Curfew/Loitering/Vagrancy
90B Society
Vagrancy Violations Violations
Disorderly Conduct 90C Disorderly Conduct Society
Driving Under the
90D Driving Under the Influence Society
Influence
Family Offenses,
90F Family Offenses, Nonviolent Society
Nonviolent
Liquor Law Violations 90G Liquor Law Violations Society
Trespass of Real Property 90J Trespass of Real Property Society
Bond Default 90K Failure to Appear* Society
Federal Resource
90L Federal Resource Violations* Society
Violations
Perjury 90M Perjury* Society
Person, Property,
All Other Offenses 90Z All Other Offenses
or Society
*Denotes offenses for federal and tribal LEA reporting only
6/30/2023 2023.0 NIBRS Technical Specification A-5
SUMMARY OF FEDERAL ADDITIONS
The changes to the NIBRS includes an additional Data Element 1A (Federal Judicial District)
and additional offenses, reported by federal and tribal LEAs only, listed in the Group A (A.1)
and Group B (A.2) tables. Other changes include removing segment specific language that
referred to flat file details and modifying error messages, warnings messages, and data element
edits to reflect the same. Also, in the “Types of NIBRS Report” section of the 2023.0 NIBRS
XML Developer’s Guide, details of the XML structure of a NIBRS submission are visually
shown in figures.
6/30/2023 2023.0 NIBRS Technical Specification B-1
PRE-NIBRS INCIDENTS
The NIBRS start date is established when the first NIBRS incident is received for an agency by
the UCR system. The start date for an agency will be established by the submission of a Group B
Arrest or Zero Report to the UCR system. Regardless of the day within the month, the NIBRS
start date will reflect the month and year of the incident, Group B Arrest, or Zero Report. For
example, a submission is received from Texas. In this submission, there is an incident for an
agency within Example City, TX, with the following ORI (TX0180000). The incident date
within the NIBRS record is March 3, 2018, and represents the first NIBRS incident the FBI UCR
Program ever received for Example City, TX. The NIBRS start date for Example City, TX, will
be 03/2018 and the system will automatically generate this date and reference it for the purpose
of handling pre-NIBRS Incidents and Window Records in future submissions.
Once the NIBRS start date is established, the NIBRS reporting flag will be set within the UCR
system. The UCR system will automatically flip the reporting flag when the agency is associated
to a State Agency Identifier (SAI) that has a NIBRS certification date. The NIBRS start date
cannot be set prior to the NIBRS certification date.
If a complete NIBRS incident is received for Example City, TX, that is before the NIBRS start
date, the system will accept the incident into the database as a pre-NIBRS Incident. The FBI
UCR Program will only count arrest, clearance, or recovered property for each pre-NIBRS
Incident within a submission. The counts obtained from the three data elements will only be used
during a current reporting year. If the complete incident is outside of the current reporting year,
the data will be stored, but ignored for all publication purposes. To clarify the term current
reporting year, the FBI UCR Program establishes the timeframe in which crime data is accepted
for annual publication. This timeframe is a general reference to accept annual crime data past the
calendar year. In practice, the 2018 Crime in the United States publication is sourced by
submissions from January 2018 to May 2019 to construct the tables within the publication.
Therefore, it is imperative the federal/state UCR programs and FBI UCR Program work closely
to determine the correct NIBRS start dates for each agency to avoid confusion and duplication of
count. As a safeguard against duplication, the UCR system will count SRS data in the unlikely
event NIBRS data was reported for the same month.
The following statements for the stated policy:
• If a NIBRS agency submits SRS data that is dated prior to the NIBRS start date, the
system will accept the data.
• If a NIBRS agency submits SRS data that is dated after the NIBRS start date, the
system will automatically reject the data.
• If Example City, TX, has a NIBRS start date of June 2019 and a complete NIBRS
incident is submitted with an arrest date of May 30, 2019, this incident will not be
used for arrests, clearances, and/or property recovery in that the agency was not
NIBRS certified until June 2019. This data should be submitted via SRS.
• If Example City, TX, reports a homicide in December 2018 via SRS submission and
has a NIBRS start date of January 2019 and a complete NIBRS incident is submitted
with an arrest date of January 31, 2019. The arrest data will be applied to 2019
reporting and the homicide offense within the complete January 31st NIBRS incident
will not be counted.
6/30/2023 2023.0 NIBRS Technical Specification C-1
TIME-WINDOW SUBMISSIONS
Time Window is a fragment, or piece of an incident, used to update an existing incident that is
outside of the two-year reporting window of the UCR program. This limitation is a result of the
legacy UCR technical solution. The Window record can execute adds, modifies, or deletes. The
segments that are allowed within a Window Record are: Administrative, Property, and Arrestee.
When a Window Record is received by the UCR system (both legacy and Tech Refresh), the
added data does not append to an existing incident. The data is stored within an orphan table.
The system does not, and will not, provide a notification to the contributor regarding status
within the database. Simply due to the limitation of not appending or attaching to an incident. To
confirm, the UCR Tech Refresh solution will execute the Window Record instruction in the
same manner as the UCR legacy system up to December 31, 2020. Starting January 1, 2021, the
FBI’s UCR Program will use the pre-NIBRS policy to collect and report, when applicable, arrest,
clearance, and recovered property.
Error 159 – Positions 58-87 must be blank for Group A Incident Report
Administrative Segments submitted with a Segment Action Type that is not W = Time-Window
Submission cannot have an entry in the Window UCR Offense Code Section.
Given the structure of NIBRS, the W (Window) and D (Delete) both occupy the same position in
the administrative segment. This makes it difficult to determine if a submitted delete is for a
Window record or for an incident. When a delete is received that contains exceptional clearance
codes, it is assumed, in legacy, to be a delete for the window record. In the new system, if a
delete is received with exceptional clearance codes but there is no corresponding window record
it will be ignored. If a matching window record is found in the orphan table, it will be deleted
from the orphan table. If a delete is received without exceptional clearance codes, it is assumed
to be a delete for an incident.
Please contact the UCR Program for further information regarding Time-Window Submissions.
MANDATORIES
This section sets forth the requirements for reporting data elements to the FBI.
A. Data Element Requirements
There are two sets of reporting requirements:
1. Group A Incident Report Data Elements - There are two subsets of these data elements:
• Common Data Elements - These are data elements which are applicable to all
Group A offenses.
• Additional Data Elements - These are data elements that are also applicable to
individual Group A offenses. They are in addition to the common data elements
and complete the reporting requirements for Group A offenses.
2. Group B Arrest Report Data Elements - These data elements are applicable to arrests for
Group B offenses. They are a subset of the data elements used for Group A offenses.
B. Mandatory versus Optional Data Elements
6/30/2023 2023.0 NIBRS Technical Specification E-1
Data elements designated as mandatory must have data values entered for them in data
records submitted to the FBI, or the reports to which they relate will be rejected as containing
errors. Examples of mandatory data elements are ORI, Incident Number, and Incident
Date/Hour. If an incident report submitted on the electronic submission lacks entries for the
ORI Number, Incident Number, or Incident Date/Hour, the report will be rejected.
Some mandatory data elements require a condition to arise before they must have data
entered.
They have an If statement associated with them stating the condition to be fulfilled which
will require their presence.
• Example: If Cleared Exceptionally does not = Not Applicable
Exceptional Clearance Date = Date of the clearance
This means that if any code but N = Not Applicable was entered into Data Element 4
(Cleared Exceptionally); the date of the clearance must be entered into Data Element 5
(Exceptional Clearance Date).
Data elements designated as optional may or may not have data values entered into them, at
the option of the agency submitting the data records to the FBI. The lack of a data value will
not cause the report to be rejected as an error. The five optional data elements are:
1. Data Element 29 (Ethnicity of Victim)
2. Data Element 30 (Resident Status of Victim)
3. Data Element 50 (Ethnicity of Arrestee)
4. Data Element 51 (Resident Status of Arrestee)
5. Data Element 39A (Ethnicity of Offender)
The following example shows that it is up to the submitting agency’s discretion whether
Victim Ethnicity (Data Element 29) and Victim Resident Status (Data Element 30) will be
reported, but the age, race, and sex of the victim must be reported. However, in order to be
reported, the victim must be an Individual or Law Enforcement Officer.
• If Type of Victim = Individual
Age of Victim
Sex of Victim
Race of Victim
Ethnicity of Victim (Optional)
Resident Status of Victim (Optional)
C. Required Data Values
In some instances, one or more data values appear within parentheses immediately following
a data element assigned to an offense. This means that those data values are required in the
sections (i.e., Property, Victim, etc.) submitted to the FBI for that offense, and if other data
values are entered, the FBI’s computer will reject the report as containing an error.
Note: When more than one offense is involved in an incident, there can be different data
value requirements for the segments relating to them.
6/30/2023 2023.0 NIBRS Technical Specification E-2
Example 1: For all Crimes Against Persons (Assault Offenses, Homicide Offenses, etc.),
Type of Victim (I) or (L) means that the submitting agency must enter I = Individual or L =
Law Enforcement Officer into Data Element 25 (Type of Victim) of the Victims relating to
those offenses. If any other type of victim code is entered into the victim submitted for one of
these offenses (B = Business or S = Society/Public), the FBI’s computer will reject the report
as containing an error.
Example 2: For all Crimes Against Society (Drug/Narcotic Offenses, Gambling Offenses,
etc.), Type of Victim (S) means that the submitting agency must enter S = Society/Public into
Data Element 25 (Type of Victim) of the Victims relating to those offenses. If any other type
of victim code is entered into the Victim submitted for one of these offenses (I = Individual
or B = Business), the FBI’s computer will reject the report as containing an error.
Example 3: If both a Crime Against Person and a Crime Against Society were involved in
the same incident, I = Individual should be entered into the victim for the Crime Against
Person, and S = Society/Public should be entered into the victim for the Crime Against
Society.
Example 4: The following example shows that if the offense (e.g., arson) was only attempted
(no fire resulted), then the type of property loss/etc. designated within the quotation marks
must be either None or Unknown.
• If Offense Attempted/Completed = Attempted
Type Property Loss = None or Unknown
Example 5: The following example shows if the offense (e.g., arson) is completed, then a
Property must be submitted which has the type of property loss/etc. designated within the
quotations (Burned) entered into Data Element 14 (Type of Property Loss), provide Data
Element 15 (Property Description), and provided Data Element 16 (Value of Property). If
any other type of property loss/etc. was entered by the submitting agency (e.g., None,
Counterfeited, Destroyed/Damaged/Vandalized, Stolen, etc.), the FBI’s computer will reject
the report as containing an error.
Note: In a multiple-offense incident, other Crimes Against Property may be involved which
could call for the other types of property loss/etc. For example, if a single incident involved
both arson and burglary, then a Property containing burned and another property containing
stolen could be submitted for the incident.
• If Offense Attempted/Completed = Completed
Type Property Loss = Burned
Property Description
Value of Property
Example 6: The following example shows if an Offender Sequence Number was assigned
data were entered describing a subject), then victim-to-offender association data must be
entered Data Element 34 (Offender Numbers to be Related) and subject-to-victim
relationship data must also be present Data Element 35 (Relationships of Victim to
Offenders).
6/30/2023 2023.0 NIBRS Technical Specification E-3
• If Offender Sequence Number does not = Unknown
Offender Number to be Related
Relationship of Victim to Offender
D. Group A Incident Report
Common data elements are applicable to all Group A offenses, i.e., offenses for which Group
A Incident Reports are submitted.
Common data elements are provided below for all initial Group A Incident Reports and
deletes to previously submitted Group A Incident Reports. Supplemental Common Data
Elements are provide below for initial Group A Incident Reports containing arrestees and
updates containing arrestees.
• Common data elements for all initial Group A Incident Reports
Mandatory:
• ORI Number
• Incident Number
• Judicial District* (For federal reporting only)
• Incident Date/Hour
• Cleared Exceptionally
If any code but N = Not Applicable in Cleared Exceptionally:
• Exceptional Clearance Date
• UCR Offense Code
• Offense Attempted/Completed
• Offender(s) Suspected of Using
• Bias Motivation
• Location Type
• Victim (Sequence) Number
• Victim Connected to UCR Offense Code(s)
• Type of Victim
If Individual in Type of Victim:
Age of Victim
Sex of Victim
Race of Victim
Ethnicity of Victim (Optional)
Resident Status of Victim (Optional)
If Law Enforcement in Type of Victim:
Age of Victim >= 17 and <=98
Offender Sequence Number
If any code but 00 = Unknown in Offender Sequence Number:
Age of Offender
Sex of Offender
Race of Offender
6/30/2023 2023.0 NIBRS Technical Specification E-4
Ethnicity of Offender (Optional)
• Supplemental common data elements for initial Group A Incident Reports containing
arrestees
Mandatory:
• Arrestee Sequence Number
• Arrest Transaction Number
• Arrest Date
• Type of Arrest
• Multiple Arrestee Segments Indicator
• UCR Arrest Offense Code
• Arrestee Was Armed With
• Age of Arrestee
• If Age of Arrestee is less than 18:
Disposition of Arrestee Under 18
• Sex of Arrestee
• Race of Arrestee
• Ethnicity of Arrestee (Optional)
• Resident Status of Arrestee (Optional)
Common data elements for deletes to previously submitted Group A Incident Reports
Mandatory:
• ORI Number
• Judicial District* (For federal reporting only)
• Incident Number
Supplemental common data elements for updates containing arrestee:
Mandatory:
• Arrestee (Sequence) Number
• Arrest (Transaction) Number
• Arrest Date
• Type of Arrest Multiple Arrestee Segments Indicator
• UCR Arrest Offense Code
• Arrestee Was Armed With
• Age of Arrestee
• If Age of Arrestee is less than 18: Disposition of Arrestee Under 18
• Sex of Arrestee
• Race of Arrestee
• Ethnicity of Arrestee (Optional)
• Resident Status of Arrestee (Optional)
6/30/2023 2023.0 NIBRS Technical Specification E-5
E. Group A Incident Report—Additional Data Elements
Additional data elements are applicable to certain Group A offenses and are in addition to the
Group A Incident Report. They complete the data element reporting requirements for the
individual offenses. These must be entered for the specified offense.
1. Animal Cruelty
Offense Code 720 - Crime Against Society
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Information = Simple/Gross Neglect, Intentional
Abuse/Torture, Organized Abuse, or Animal Sexual Abuse
2. Location Type cannot = Cyberspace
2. Arson
Offense Code 200 – Crime Against Property
Mandatory Elements/Values:
1. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
2. If Offense Attempted/Completed = Completed
a. Type Property Loss = Burned
b. Property Description
c. Value of Property
3. Location Type cannot = Cyberspace
3. Assault Offenses
Offense Code Aggravated Assault, Simple Assault, and Intimidation - Crime Against Persons
Mandatory Elements/Values:
1. Offense Attempted/completed = Completed
2. Type of Victim = Individual or Law Enforcement Officer
3. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
4. If Offense Code = Aggravated Assault or Simple Assault
a. Type Weapon/Force Involved
b. If Offense Code=Simple Assault
c. Type Weapon/Force Involved=Personal Weapons, Other, Unknown, None
d. Type Injury
5. Location Type cannot = Cyberspace (except Intimidation)
6. If Offense Code = Aggravated Assault
6/30/2023 2023.0 NIBRS Technical Specification E-6
a. Aggravated Assault/Homicide Circumstances = Argument, Assault on LEO,
Drug Dealing, Gangland, Juvenile Gang, Domestic Violence, , Other Felony
Involved, Other Circumstances, or Unknown Circumstances
7. If Type of Victim = Law Enforcement Officer
a. Type of Activity (Officer)/Circumstance
b. Assignment Type (Officer)
c. ORI-Other Jurisdiction (Officer) only if Reporting Agency ORI Number
differs from officer’s regular jurisdiction
8. If Type Criminal Activity/Gang Information provided
a. Type Criminal Activity/Gang Information = Juvenile Gang, Other Gang, or
None/Unknown
9. If Type of Weapon/Force Involved = Firearm, Firearm Automatic, Handgun,
Handgun Automatic, Rifle, Rifle Automatic, Shotgun, Shotgun Automatic, Other
Firearm, or Other Firearm Automatic
a. Offense Code = Aggravated Assault
4. Bribery
Offense Code 510 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = None, Recovered, Stolen, or Unknown
4. If Type Property Loss = Recovered or Stolen
a. Property Description
b. Value of Property
c. If Type Property Loss = Recovered
i. Date Recovered
5. Burglary/Breaking and Entering
Offense Code 220 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. Location Type cannot = Cyberspace
3. If Location Type = Hotel/Motel/Etc. or Rental Storage Facility
a. Number of Premises Entered = 1 to 99
4. Method of Entry = Force or No Force
6/30/2023 2023.0 NIBRS Technical Specification E-7
5. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
6. If Offense Attempted/Completed = Completed
a. Type Property Loss = None, Recovered, Stolen, or Unknown
7. If Type Property Loss = Recovered or Stolen
a. Property Description
b. Value of Property
c. If Type Property Loss = Recovered
i. Date Recovered
6. Commerce Violations* and Import and Export Violations* (For federal and tribal
reporting only)
Offense Code Import Violations (58A) and Export Violations (58B) – Crime Against Society
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Involvement = Buying/Receiving,
Cultivating/Manufacturing/Publishing, Distributing/Selling, Exploiting Children,
Operating/Promoting/Assisting, Possessing/Concealing,
Transporting/Transmitting/Importing, or Using/Consuming
2. Type of Victim = Government
3. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
4. For Import Violations - If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized or None
b. Property Description
c. Value of Property
5. For Export Violations - If Offense Attempted/Completed = Completed
a. Type Property Loss = Counterfeited/Forged, Recovered, or Seized
b. Property Description
c. Value of Property
d. If Type Property Loss=Recovered
i. Date Recovered
6. Location Type cannot = Cyberspace
7. Liquor and Tobacco Violations* (For federal and tribal reporting only)
Offense Code Liquor Offenses (61A) and Tobacco Offenses (61B) - Crime Against Society
Mandatory Elements/Values:
6/30/2023 2023.0 NIBRS Technical Specification E-8
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. Type of Victim = Government
3. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
4. If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized or None
b. If Type Property Loss=Seized
i. Property Description
ii. Value of Property
5. Location Type cannot = Cyberspace
8. Wildlife Trafficking* (For federal and tribal reporting only)
Offense Code 620 – Crime Against Society
Mandatory Elements/Values:
1. Type of Victim = Society
2. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
3. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
4. If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized or None
If Type Property Loss=Seized
i. Property Description
ii. Value of Property
5. Location Type cannot = Cyberspace
9. Counterfeiting/Forgery
Offense Code 250 – Crime Against Property
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = Counterfeited/Forged, Recovered, or Seized
b. Property Description
c. Value of Property
6/30/2023 2023.0 NIBRS Technical Specification E-9
d. If Type Property Loss = Recovered
i. Date Recovered
10. Destruction/Damage/Vandalism of Property
Offense Code 290 – Crime Against Property
Mandatory Elements/Values:
1. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
2. If Offense Attempted/Completed = Completed
a. Type Property Loss = Destroyed/Damaged/Vandalized
b. Property Description
c. Value of Property
11. Drug/Narcotic Offenses
Offense Code Drugs/Narcotic Violations 35A and Drug Equipment Violations 35B – Crime
Against Society
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. Type of Victim=Society
3. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
4. If Offense Attempted/Completed = Completed
a. Type Property Loss = None or Seized
5. If Property Description does not equal Drugs/Narcotic Violations
Value of Property
6. If Offense Code is Drug/Narcotic Violations
a. If Type Property Loss = Seized
i. Property Description cannot = Drug Equipment
b. If Type Property Loss = None
i. Suspected Drug Type
c. If Type Property Loss = Seized and If Property Description = Drugs/Narcotic
i. Suspected Drug Type
ii. Estimated Drug Quantity
iii. Type Drug Measurement
7. If Offense Code = Drug Equipment Violations
a. If Type Property Loss = Seized
6/30/2023 2023.0 NIBRS Technical Specification E-10
i. Property Description cannot = Drugs/Narcotic
12. Embezzlement
Offense Code 270 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
d. If Type Property Loss = Recovered
i. Date Recovered
13. Espionage* (For federal and tribal reporting only)
Offense Code 103 – Crime Against Society
Mandatory Elements/Values:
1. Type of Victim = Society
14. Extortion/Blackmail
Offense Code 210 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. Type Weapon/Force Involved
3. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
4. If Offense Attempted/Completed = Complete
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
d. If Type Property Loss = Recovered
i. Date Recovered
5. If Type of Victim = Individual
a. Type Injury
15. Fraud Offenses
Offense Codes False Pretenses (26A), Credit Card/ATM (26B), Impersonation (26C),
Welfare Fraud (26D), Wire Fraud (26E), Identity Theft (26F), Hacking (26G), Money
Laundering* (26H) (For federal and tribal reporting only) – Crime Against Property
6/30/2023 2023.0 NIBRS Technical Specification E-11
Mandatory Elements/Values:
1. If offense is not = Welfare Fraud
a. Cargo Theft = True or False
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
d. If Type Property Loss = Recovered
i. Date Recovered
4. If Offense Code = Money Laundering
a. Type of Victim = Government
16. Fugitive Offenses* (For federal and tribal reporting only)
Offense Code Harboring Escapee (49A), Flight to Avoid Prosecution (49B), Flight to Avoid
Deportation (49C) – Crime Against Society
Mandatory Elements/Values:
1. Type of Victim = Society
2. If Offense Code = Harboring Escapee/Concealing from Arrest
a. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
3. Location Type cannot = Cyberspace
17. Gambling Offenses
Offense Code Betting/Wagering (39A), Operating/Promoting Gambling (39B), Gambling
Equipment Violation (39C), Sports Tampering (39D) – Crime Against Society
Mandatory Elements/Values:
1. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
2. If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized
b. Property Description
c. Value of Property
3. Type of Victim = Society
4. If Offense Code = Gambling Equipment Violations
a. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
6/30/2023 2023.0 NIBRS Technical Specification E-12
18. Homicide Offenses
Offense Codes Murder and Nonnegligent (09A), Negligent Manslaughter (09B), Justifiable
Homicide (09C) – Crime Against Persons
Mandatory Elements/Values:
Note: Attempted murder is to be classified as aggravated assault.
1. Offense Attempted/Completed = Completed
2. Type Weapon/Force Involved/Automatic Indicator cannot = None
3. Type of Victim = Individual or Law Enforcement Officer
a. Law Enforcement Officer can only be reported for Murder and Nonnegligent
Manslaughter
4. If Type of Victim = Law Enforcement Officer
a. Type of Activity (Officer)/Circumstance
b. Assignment Type (Officer)
c. If Reporting Agency ORI Number differs from the ORI of the Officer’s
regular jurisdiction:
i. ORI-Other Jurisdiction (Officer)
5. If Offense Code = Murder and Nonnegligent Manslaughter
a. Aggravated Assault/Homicide Circumstances = Argument, Assault on LEO,
Drug Dealing, Gangland, Juvenile Gang, Domestic Violence, Mercy Killing,
Other Felony Involved, Other Circumstances, or Unknown Circumstances
6. If Offense Code = Negligent Manslaughter
a. Aggravated Assault/Homicide Circumstances = Child Playing with Weapon,
Gun-Cleaning Accident, Hunting Accident, Other Negligent Weapon
Handling, or Other Negligent Killing
7. If Offense Code = Justifiable Homicide
a. Aggravated Assault/Homicide Circumstances = Criminal Killed by Private
Citizen or Criminal Killed by Police
b. Additional Justifiable Homicide Circumstances=Criminal Attacked Police
Officer and That Officer Killed Criminal, Criminal Attacked Police Officer
and Criminal Killed by Another Police Officer, Criminal Attacked a Civilian,
Criminal Attempted Flight from a Crime, Criminal Killed in Commission of a
Crime, Criminal Resisted Arrest, or Unable to Determine/Not Enough
Information
8. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
9. If Offense Code = Murder Nonnegligent or Negligent Manslaughter and Type
Criminal Activity/Gang Information is provided
6/30/2023 2023.0 NIBRS Technical Specification E-13
a. Type Criminal Activity/Gang Information = Juvenile, Other Gang, or
None/Unknown
10. Location Type cannot = Cyberspace
19. Human Trafficking Offenses
Offense Codes Commercial Sex Acts (64A) and Involuntary Servitude (64B) – Crime
Against Persons
Mandatory Elements/Values:
1. Offense Attempted/Completed = Attempted or Completed
2. Type Weapon/Force Involved/Automatic Indicator
3. Type of Victim = Individual
4. Type Injury
5. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
20. Immigration Violations* (For federal and tribal reporting only)
Offense Codes Illegal Entry (30A), False Citizenship (30B), Smuggling Aliens (30C), Re-
entry after Deportation (30D)
Mandatory Elements/Values:
1. Type of Victim = Society
2. If Offense Code = Smuggling Aliens
a. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
3. Location Type cannot = Cyberspace
21. Kidnapping/Abduction
Offense Code 100 – Crime Against Person
Mandatory Elements/Values:
1. Type Weapon/Force Involved/Automatic Indicator
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = None, Recovered, Stolen, or Unknown
4. If Type Property Loss = Recovered or Stolen
a. Property Description
b. Value of Property
c. If Type Property Loss = Recovered
i. Date Recovered
5. Type of Victim = Individual
6. Type Injury
6/30/2023 2023.0 NIBRS Technical Specification E-14
7. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
8. Location Type cannot = Cyberspace
9. If Type Criminal Activity/Gang Information is provided:
a. Type Criminal Activity/Gang Information = Juvenile Gang, Other Gang, or
None/Unknown
22. Larceny/Theft Offenses
Offense Codes Pocket-picking (23A), Purse-snatching (23B), Shoplifting (23C), Theft from
Building (23D), Theft from Coin-Operated Machine (23E), Theft from Motor Vehicle (23F),
Theft of Motor Vehicle Parts/Accessories (23G), All Other Larceny (23H) – Crime Against
Property
Mandatory Elements/Values:
1. If Offense Code = Theft From Building, Theft from Motor Vehicle, or All Other
Larceny
a. Cargo Theft = True or False
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
4. If Type Property Loss = Recovered
a. Date Recovered
5. Location Type cannot = Cyberspace
23. Motor Vehicle Theft
Offense Code 240 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = Recovered or Stolen
b. Value of Property
c. Property Description=Automobiles, Buses, Other Motor Vehicles,
Recreational Vehicles, or Trucks
6/30/2023 2023.0 NIBRS Technical Specification E-15
d. If Type Property Loss = Recovered
i. Date Recovered
4. If Property Description = Automobiles, Buses, Other Motor Vehicles, Recreational
Vehicles, or Trucks
a. Number of Recovered Motor Vehicles = 00 – 99
5. If Type Property Loss = Stolen
a. Property Description = any valid codes, but one must be Automobiles, Buses,
Other Motor Vehicles, Recreational Vehicles, or Trucks
b. Number of Stolen Motor Vehicles = 00 – 99
6. Location Type cannot = Cyberspace
24. Pornography/Obscene Material
Offense Code 370 – Crime Against Society
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. Type of Victim = Society
25. Prostitution Offenses
Offense Codes Prostitution (40A), Assisting or Promoting Prostitution (40B), Purchasing
Prostitution (40C) – Crime Against Society
Mandatory Elements/Values:
1. Type of Victim = Society
26. Robbery
Offense Code 120 – Crime Against Property
Mandatory Elements/Values:
1. Cargo Theft = True or False
2. Type Weapon/Force Involved/Automatic Indicator
3. If Type of Victim = Individual
o Type Injury
4. Location Type cannot = Cyberspace
5. If Offense Attempted/Completed = Attempted
o Type Property Loss = None or Unknown
6. If Offense Attempted/Completed = Completed
o Type Property Loss = Recovered or Stolen
o Property Description
o Value of Property
o If Type Property Loss = Recovered
i. Date Recovered
6/30/2023 2023.0 NIBRS Technical Specification E-16
7. If Type of Victim = Individual and Offender Sequence Number does not = Unknown
o Offender Number to be Related
o Relationship of Victim to Offender
8. If Type Criminal Activity/Gang Information is present:
o Type Criminal Activity/Gang Information = Juvenile Gang, Other Gang, or
None/Unknown
27. Sex Offenses
Offense Codes Rape (11A), Sodomy (11B), Sex Assault With An Object (11C), Fondling
(11D) – Crime Against Persons
Mandatory Elements/Values:
1. Location Type cannot = Cyberspace
2. Type Weapon/Force Involved/Automatic Indicator
3. If Type Criminal Activity/Gang Information is present:
a. Type Criminal Activity/Gang Information = Juvenile Gang, Other Gang, or
None/Unknown
4. Type of Victim = Individual
5. Type Injury
6. If Offender Sequence Number does not = 00 (Unknown)
a. Offender Number to be Related
b. Relationship of Victim to Offender
28. Sex Offenses
Offense Codes Incest (36A), Statutory Rape (36B) – Crime Against Persons
Mandatory Elements/Values:
1. Location Type cannot = Cyberspace
2. Type of Victim = Individual
3. If Offender Sequence Number does not = 00 (Unknown)
a. Offender Number to be Related
b. Relationship of Victim to Offender
29. Sex Offenses, Failure to Register as a Sex Offender* (For federal and tribal reporting
only)
Offense Code 360 – Crime Against Society
Mandatory Elements/Values:
1. Offense Attempted/Completed = Attempted
2. Type of Victim = Society
3. Offender Number to be Related cannot be Unknown
4. Location Type cannot = Cyberspace
30. Stolen Property Offenses
Offense Code 280 – Crime Against Property
Mandatory Elements/Values:
6/30/2023 2023.0 NIBRS Technical Specification E-17
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed = Completed
a. Type Property Loss = None or Recovered
b. If Type Property Loss = Recovered
i. Property Description
ii. Value of Property
iii. Date Recovered
31. Treason* (For federal and tribal reporting only)
Offense Code 101 – Crime Against Society
Mandatory Elements/Values:
1. Type of Victim = Society
32. Weapon Law Violations
Offense Codes Weapon Law Violations (520), Violation of National Firearms Act of 1934*
(521), Weapons of Mass Destruction* (522), Explosives* (526) - Crime Against Society
*Denotes offenses for federal and tribal LEA reporting only
Mandatory Elements/Values:
1. Type Criminal Activity/Gang Information = Buying/Receiving, Cultivating,
Distributing, Exploiting, Operating, Promoting, Transporting, or Using
2. Type Weapon/Force Involved
3. Type of Victim = Government (For Federal Offenses)
a. If Offense Attempted/Completed = Attempted
i. Type Property Loss = None or Unknown
b. If Offense Attempted/Completed = Completed
i. Type Property Loss = Seized or None
1. If Seized
a. Property Description
b. Value of Property
4. If Offense Code = Weapon Law Violations (520):
a. Type of Victim = Society
F. Group B Arrest Report data elements
These data elements are applicable to all Group B offenses, i.e., those offenses for which
only Group B Arrest Reports are submitted.
6/30/2023 2023.0 NIBRS Technical Specification E-18
The data elements used in the Group B Arrest Report are the same as those used in the
Arrestee Section of the Group A Incident Report, except for the Data Element 44 (Multiple
Arrestee Segments Indicator) which is not applicable.
Group B Arrest Report mandatory elements:
• ORI Number
• Judicial District* (For federal reporting only)
• Arrest Transaction Number
• Arrestee Sequence Number
• Arrest Date
• Type of Arrest
• UCR Arrest Offense Code
• Arrestee Was Armed With
• Age of Arrestee
• Sex of Arrestee
• Race of Arrestee
• If Age of Arrestee is less than 18
Disposition of Arrestee Under 18
• Ethnicity of Arrestee (Optional)
• Resident Status of Arrestee (Optional)
6/30/2023 2023.0 NIBRS Technical Specification E-19
LEGACY TIME-WINDOW ERRORS
053: RECORD NOT ON FILE
057: ACTION TYPE IS NOT VALID FOR THIS RECORD LEVEL
064: ARRESTEE ALREADY ON FILE
087: WINDOW SEGMENTS ALREADY ON FILE WITH THIS INCIDENT NUMBER
089: PRE NIBRS PROPERTY SEGMENTS ALREADY EXIST FOR THIS INCIDENT NUMBER
120: EXCEPTIONAL CLEARANCE DATE CANNOT PREDATE BASE DATE
121: JUSTIFIABLE HOMICIDE (09C) IS NOT A VALID WINDOW OFFENSE CODE
154: CLEARED EXCEPTIONALLY CANNOT CONTAIN N WITH SEGMENT ACTION TYPE W
157: MUST BE PRESENT FOR TIME-WINDOW SEGMENT
158: OFFENSE CODE FIELD MUST HAVE ENTRY WITH SEGMENT ACTION TYPE W
159: POSITIONS 58-87 MUST BE BLANK FOR GROUP A INCIDENT REPORT
160: INCIDENT NOT ON FILE
161: CANNOT MODIFY GROUP A INCIDENT DATE THIS WAY
162: CANNOT MODIFY GROUP A REPORT FLAG THIS WAY
163: CANNOT MODIFY GROUP A INCIDENT HOUR THIS WAY
164: CLEARED EXCEPTIONALLY FIELD MUST CONTAIN N WHEN ARRESTEES WERE REPORTED
165: CANNOT BE BLANK OR EQUAL N FOR NON GROUP A SEGMENT
166: CANNOT HAVE ENTRY IN EXCEPTIONAL CLEARANCE DATE IF CLEARED EXCEPTIONALLY
IS N
167: DATE CANNOT BE BLANK FOR NON GROUP A SEGMENT
168: GROUP A CANNOT HAVE OFFENSES IN POSITIONS 58-87 ON MAGNETIC MEDIA SEGMENT
169: TIME-WINDOW SEGMENT BEING MODIFIED MUST HAVE OFFENSE CODE
171: INCIDENT DATE IS OUTSIDE THE BASE DATE CALCULATION
174: EXCEPTIONAL CLEARANCE DATE PREDATES DATE ORI WENT IBR
176: INCIDENT DATE FOR WINDOW RECORDS CANNOT BE WITHIN BOUNDARIES OF GROUP A
INCIDENT
177: GROUP B OFFENSE CODES CANNOT BE ENTERED IN POSITIONS 58-87 ON SE320:
RECOVERED DATE CANNOT PREDATE BASE DATE
320: RECOVERED DATE CANNOT PREDATE BASE DATE
321: JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE CODE
369: MUST BE BLANK WHEN ACTION TYPE = I (INITIAL)
370: MUST HAVE AN ENTRY WITH AN ACTION TYPE OF W (WINDOW)
371: GAMBLING, KIDNAPING, AND CRIMES AGAINST PROPERTY ARE THE ONLY VALID
OFFENSES
6/30/2023 2023.0 NIBRS Technical Specification F-1
377: PROPERTY SEGMENT A-O-F
378: ATTEMPT TO ADD OTHER THAN RECOVERED PROPERTY IS NOT ALLOWED
379: ATTEMPT TO MODIFY OTHER THAN RECOVERED PROPERTY IS NOT ALLOWED
380: CANNOT MODIFY PROPERTY-GROUP A ADDED
381: CANNOT DELETE PROPERTY-GROUP A ADDED
393: WARNING-NIBRS INCIDENT NOT ON FILE DATA WILL BE CONSIDERED TO BE PRE-NIBRS
620: ARREST DATE CANNOT PREDATE BASE DATE
621: JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE
657: VALID VALUES FOR WINDOW CLEARANCE INDICATOR ARE Y OR N
658: CLEARANCE INDICATOR AND CLEARANCE OFFENSE CODE MUST BE BLANK
659: CLEARANCE OFFENSE CODE MUST CONTAIN AT LEAST ONE GROUP A OFFENSE
660: GROUP A INCIDENT REPORT NOT ON FILE
662: CANNOT DELETE AN ARREST WHEN GROUP A INCIDENT REPORT ON FILE
663: CANNOT MODIFY AN ARREST WHEN GROUP A INCIDENT REPORT ON FILE
668: ARRESTEE RECORD PREVIOUSLY SUBMITTED WITH A Y IN THE CLEARANCE BYTE
671: GROUP B OFFENSE CODES CANNOT BE ENTERED IN POSITIONS 81-110 ON SEGMENT
762: GROUP B ARREST REPORT IS NOT ON FILE TO MODIFY
6/30/2023 2023.0 NIBRS Technical Specification F-2
Source: NIBRS 2023.0 Technical Specification.docx