Download:
pdf |
pdfU. S. Department of Justice
Federal Bureau of Investigation
Criminal Justice Information Services Division
Criminal Justice Information Services Division
Uniform Crime Reporting Program
2019.2.1
National Incident-Based Reporting System
Technical Specification
06/15/2020
Prepared by:
Global Law Enforcement Support Section
Crime Statistics Management Unit
CHANGE DESCRIPTION FORM
06/15/2020
Revision
Change Description
Date
1.0
UCRRP Initial Release
04/16/2012
1.0
Attaching CJIS Template and
formatting.
08/27/2013
1.1
2015 Bias Motivation Code
Additions
09/17/2014
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
2.1
Edit/format correction to CJIS
template
11/03/2015
3.0
Business rules updates,
verification, and formatting
7/18/2016
8/15/2015
3.1
Technical Changes
1/09/2017
3.2
Alignment with user manual
(version 2.0).
8/30/2017
2019.0
2019 Additions
03/22/2018
2019.1
UCR-TR Modifications
06/30/2018
2019.2
Inclusion of new offenses
(reported by federal and tribal
LEAs only), Judicial Districts and
reconciliation with UCR Tech
Refresh system processing.
Additional updates as noted in the
Change Description Details below.
05/15/2020
2019.2.1
Correction to the alignment of
Data Structure Errors Table and
Change Description Details.
06/15/2020
2019.2.1 NIBRS Technical Specification
i
VERSION 2019.2 CHANGE DESCRIPTION DETAILS
Table
Change Description
3-26
5-2
072 Minor error wording change to concur with UCRTR: Changed
“FIRST” to “ALSO”
076 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
077 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
078 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
5-2
3-26
5-2
3-26
5-2
3-2
3-38
5-2
080 Minor error wording change to concur with UCRTR: Added 26H =
Money Laundering and 526 = Explosives*
5-2
5-11
5-11
5-11
5-3
5-3
081 Minor error wording change to concur with UCRTR: Added new
offenses, reported by federal and tribal LEAs only, per Type of
Property Loss
088 Minor error wording change to concur with UCRTR
093 Minor error wording change to concur with UCRTR
094 Minor error wording change to concur with UCRTR
096 Minor error wording change to concur with UCRTR
104 Minor error wording change to concur with UCRTR
118 Minor error wording change to concur with UCRTR
5-3
155 Minor error wording change to concur with UCRTR
5-3
170 Minor error wording change to concur with UCRTR
171 INCIDENT DATE IS OUTSIDE THE BASE DATE CALCULATION was
listed twice in Appendix F, removed duplicate entry
175 Minor error wording change to concur with UCRTR
3-26
5-2
Appendix F
5-3
5-4
207 Added specific error types: 207A ERROR MUTUALLY EXCLUSIVE
VALUE - SUSPECTED OF USING 207B ERROR MUTUALLY EXCLUSIVE
VALUE - BIAS MOTIVATION 207C ERROR MUTUALLY EXCLUSIVE VALUE
- CRIMINAL ACTIVITY / GANG INFORMATION 207D ERROR MUTUALLY
EXCLUSIVE VALUE - WEAPON CODE
3-23
5-4
219 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
3-23
5-4
220 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
3-24
5-4
221 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
3-24
5-4
222 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
06/15/2020
2019.2.1 NIBRS Technical Specification
ii
Section 3.3.3.9
Data Element 13
Type of Weapon/Force Involved Mandatories section updated with
federal additions
3-16
5-4
250 New error message: OFFENSE CODE CAN ONLY BE USED BY
FEDERAL AGENCIES
3-17
5-4
256 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
5-4
5-4
5-4
5-5
5-5
5-5
5-5
5-5
5-5
5-6
5-6
3-38
5-6
3-38
5-6
5-6
265 Minor error wording change to concur with UCRTR
266 Minor error wording change to concur with UCRTR
267 Minor error wording change to concur with UCRTR
354 Minor wording change to concur with UCRTR
355 Minor error wording change to concur with UCRTR
356 Minor error wording change to concur with UCRTR
357 Wording change
363 Minor error wording change to concur with UCRTR
376 Minor error wording change to concur with UCRTR
415 Minor error wording change to concur with UCRTR
452 Minor error wording change to concur with UCRTR
461 New error message: ENTRY FOR TYPE OF VICTIM MUST BE "G"
WHEN THIS OFFENSE CODE IS ENTERED
465 Minor error wording change to concur with UCRTR: Added new
offenses (reported by federal and tribal LEAs only).
481 Minor error wording change to concur with UCRTR
485 Added missing error and modified to include new offenses
(reported by federal and tribal LEAs only): OFFENDER NUMBER TO
3-50
5-6
BE RELATED CANNOT BE “00” FOR THIS OFFENSE
3-62
5-9
5-9
5-10
3-62
5-10
650 Added message: ARREST OFFENSE CODE CAN ONLY BE USED BY
FEDERAL AND TRIBAL AGENCIES
656 Minor error wording change to concur with UCRTR
720 Minor error wording change to concur with UCRTR
750 Added message: ARREST OFFENSE CODE CAN ONLY BE USED BY
FEDERAL AND TRIBAL AGENCIES
Section 5.2.10
Warning Table
1402 Corrected misspelling
Section 5.2.10
Warning Table
1403 Corrected misspelling
Section 5.2.10
Warning Table
1413 Minor error wording change to concur with UCRTR
Section 5.2.10
Warning Table
1640 Minor error wording change to concur with UCRTR
Section 5.2.10
Warning Table
1708 Minor error wording change to concur with UCRTR
06/15/2020
2019.2.1 NIBRS Technical Specification
iii
Section 5.2.10
Warning Table
5-2
Appendix F
5-2
5-2
5-2
5-2
5-2
5-2
5-2
5-2
5-2
5-2
5-2
1740 Minor error wording change to concur with UCRTR
933 Minor error wording change to concur with UCRTR
320 RECOVERED DATE CANNOT PREDATE BASE DATE-Added to
Appendix F
931 Incorrect message & description. Corrected
932 Incorrect message & description. Corrected
933 Incorrect message. Corrected
934 Incorrect message & description. Corrected
935 New error message: NIBRS CERTIFICATION DATE DOES NOT EXIST
937 New error message: PRE-NIBRS INCIDENT RECEIVED
938 New error message: MULTIPLE INCIDENTS ON FILE
939 New error message: CANNOT MODIFY PRE-NIBRS GROUP B
INCIDENT
940 New error message: EXCEPTIONAL CLEARANCE ALREADY ON FILE
941 New error message: WEB SERVICE SUBMISSION ALREADY IN
PROCESS
952 Wording changed to: INVALID ORI FORMAT - NOT A VALID ORI NOT IN UCR ORI FILE
3.3.5.15 Data
Element 34
Offender Number to be Related, changed from mandatory to optional
3.3.5.16 Data
Element 35
Relationship of Victim to Offender, changed from mandatory to
optional
Section 5.2.10
Warning Table
1197 Added Data Quality Warning 1197 DELETED MULTIPLE
INCIDENTS
Section 5.2.10
Warning Table
1198 Added Data Quality Warning 1198 INCIDENT DATE IN DELETE
DOES NOT MATCH INCIDENT DATE ON FILE
Section 5.2.10
Warning Table
1350 Added Data Quality Warning 1350 WARNING - CONTAINS NONNUMERIC ENTRY - MUST BE ZERO LEFT FILL
Section 5.2.10
Warning Table
1451 Added Data Quality Warning 1451 WARNING - VICTIM AGE
RANGE OF 01-98 AND 01-99
Section 5.2.10
Warning Table
1551 Added Data Quality Warning 1551 WARNING - OFFENDER AGE
RANGE OF 01-98 AND 01-99
Section 5.2.10
Warning Table
1651 Added Data Quality Warning 1651 WARNING - ARRESTEE AGE
RANGE OF 01-98 AND 01-99
Section 5.2.10
Warning Table
1751 Added Data Quality Warning 1751 WARNING - ARRESTEE AGE
RANGE OF 01-98 AND 01-99
06/15/2020
2019.2.1 NIBRS Technical Specification
iv
Appendix B
Added new offenses, reported by federal and tribal LEAs only, noted
with asterisk "*"
3.3.2.2 Data
Element 1AFederal Judicial
District
Added Federal Judicial Districts for Federal Submissions
Only
Added Figure 610
2.2.1.1
Administrative
Segment Layout
(Level 1).
Flat file WDS layout table
Addition of Federal Judicial District Code in positions 89, 90, 91 and
updated the Segment Length description for Federal Agency Reporting
Only.
2.3.1 Group B
Arrest Report
Segment Layout
(Level 7).
Addition of Federal Judicial District Code in positions 67, 68, 69 and
updated the Segment Length description for Federal Agency Reporting
Only
Appendix E:
Mandatories
Addition of Federal Judicial District Code, new offenses (reported by
federal and tribal LEAs only), removed duplicate data, corrected errors
in logic, modified codes to element and value names
Addition of 58B
= Export
Violations*
Addition of 58B = Export Violations* exception 1 in Tables 3-26 Type
Property Loss/Etc. Edit Description, Table 3-2 Segment Level Edit
Description, and Table 3-27 Property Description Edits
3-2 Segment
Level Edit
Description
Removed Error 930 to align with system functionality
5-2 Structure
Check Errors
Removed Error 930 to align with system functionality
3-2 Segment
Level Edit
Descriptions
Edit Description for Associated Error Code 072: Minor error wording
change to concur with UCRTR
3-26 Type
Property
Loss/Etc. Edit
Description
Edit Description for Associated Error Code 072: Minor error wording
change to concur with UCRTR
3-27 Property
Description Edit
Description
Edit Description for Associated Error Code 072: Minor error wording
change to concur with UCRTR
06/15/2020
2019.2.1 NIBRS Technical Specification
v
3-7 ORI Edit
Description
Add Associated Error Codes 931-934 to align with UCR-TR
5-2 Structure
Check Errors
Add Error Description for 096
5-2 Structure
Check Errors
Add Error Description for Error 938
5-2 Structure
Check Errors
Add Error Description for Error 939
5-2 Structure
Check Errors
Add Error Description for Error 940
5-2 Structure
Check Errors
Add Error Description for Error 941
APPENDIX F
Remove Error number 095
5-2 Structure
Check Errors
Insertion of Error Number 095, Error Message, and Error Description
Table of
Contents and
Sex Offenses
Removed the word Forcible from Sex Offenses in the Table of
Contents and from Sex Offenses where applicable
Edit Descriptions
Insertion of NIBRS codes within Edit Descriptions for new offenses
Error 559
Update to Error 559 in Table 3-2 Segment Level Edit Descriptions,
Table 3-52 Offender Sequence Number Edit Description, and Table 5-8
Offender Segment Errors
Error 080
Update to Edit Description for Error 080 in Segment Level Edit
Descriptions, Type of Victim Element Edits, and Structure Check Errors
Appendix E
Update to Fraud Offenses to concur with URCTR
2019.2.1
In error 081, was missing Type Property Loss is 1 and conditions in the
Description, shifting all cells down with misalignment. Corrected
missing text and realigned Description cells with proper Error number.
Removed 3-53 Age of Offender Edit from Change Description Details
as no changes were made to the documented age of 13.
06/15/2020
2019.2.1 NIBRS Technical Specification
vi
TABLE OF CONTENTS
1
2
Background ........................................................................................................................... 1
Incident Reports .................................................................................................................... 3
2.1
Header Data Elements..................................................................................................... 3
2.2
Group A Incident Reports ............................................................................................... 4
2.2.1 Level 1–Administrative Segment ............................................................................... 4
Administrative Segment Layout (Level 1) ........................................................ 5
2.2.2
Level 2–Offense Segment ........................................................................................... 5
Offense Segment Layout (Level 2) ................................................................... 6
2.2.3
Level 3–Property Segment .......................................................................................... 6
Property Segment Layout (Level 3) .................................................................. 7
2.2.4
Level 4–Victim Segment ............................................................................................ 7
Victim Segment Layout (Level 4) ..................................................................... 8
2.2.5
Level 5–Offender Segment ......................................................................................... 8
Offender Segment Layout (Level 5) .................................................................. 9
2.2.6
Level 6–Arrestee Segment .......................................................................................... 9
Arrestee Segment Layout (Level 6)................................................................. 10
2.3
Level 7–Group B Arrest Report Segment ..................................................................... 10
2.3.1 Group B Arrest Report Segment Layout (Level 7) ................................................... 11
2.4
Level 0–Zero Report Segment ...................................................................................... 11
2.4.1 Zero Report Segment Layout (Level 0) .................................................................... 12
3 Data Element Definitions ................................................................................................... 13
3.1
Data Elements ............................................................................................................... 13
3.2
Data Values ................................................................................................................... 13
3.3
Data Element Descriptions ........................................................................................... 13
3.3.1 Header Data Elements............................................................................................... 14
Segment Length ............................................................................................... 14
Segment Level ................................................................................................. 15
Segment Action Type ...................................................................................... 20
Month of Submission....................................................................................... 21
Year of Submission ......................................................................................... 22
City Indicator ................................................................................................... 23
3.3.2
Administrative Segment............................................................................................ 23
Data Element 1-ORI ........................................................................................ 23
Data Element 1A-Federal Judicial District (JD) [Federal Submissions Only] 24
Data Element 2-Incident Number .................................................................... 27
Data Element 2A-Cargo Theft ......................................................................... 28
Data Element 3-Incident Date ......................................................................... 30
Data Element 3-Report Date Indicator ............................................................ 32
06/15/2020
2019.2.1 NIBRS Technical Specification
vii
Data Element 3-Incident Hour ......................................................................... 32
Data Element 4-Cleared Exceptionally ........................................................... 33
Data Element 5-Exceptional Clearance Date .................................................. 34
3.3.3
Offense Segment ....................................................................................................... 35
Data Element 6-UCR Offense Code ................................................................ 36
Data Element 7-Offense Attempted/Completed .............................................. 37
Data Element 8-Offender Suspected of Using ................................................ 38
Data Element 8A-Bias Motivation .................................................................. 39
Data Element 9-Location Type........................................................................ 41
Data Element 10-Number of Premises Entered ............................................... 43
Data Element 11-Method of Entry .................................................................. 44
Data Element 12-Type Criminal Activity/Gang Information.......................... 45
Data Element 13-Type Weapon/Force Involved ............................................. 48
Data Element 13-Automatic Weapon Indicator .............................................. 51
3.3.4
Property Segment ...................................................................................................... 52
Data Element 14-Type Property Loss/Etc. ...................................................... 52
Data Element 15-Property Description............................................................ 61
3.3.4.2.1 Illogical Property Description for the Offense(s) Submitted ...................... 65
Data Element 16-Value of Property ................................................................ 67
Data Element 17-Date Recovered ................................................................... 69
Data Element 18-Number of Stolen Motor Vehicles ...................................... 70
Data Element 19-Number of Recovered Motor Vehicles ............................... 71
Data Element 20-Suspected Drug Type .......................................................... 72
Data Element 21-Estimated Drug Quantity ..................................................... 75
Data Element 22-Type Drug Measurement ..................................................... 76
3.3.5
Victim Segment ........................................................................................................ 78
Data Element 23-Victim Sequence Number ................................................... 78
Data Element 24-Victim Connected to UCR Offense Code ........................... 79
Data Element 25-Type of Victim .................................................................... 83
Data Element 25A-Type of Officer Activity/Circumstance ............................ 85
Data Element 25B-Officer Assignment Type ................................................. 86
Data Element 25C-Officer-ORI Other Jurisdiction ......................................... 87
Data Element 26-Age of Victim ...................................................................... 87
Data Element 27-Sex of Victim....................................................................... 89
Data Element 28-Race of Victim..................................................................... 90
Data Element 29-Ethnicity of Victim .............................................................. 90
Data Element 30-Resident Status of Victim .................................................... 91
Data Element 31-Aggravated Assault/Homicide Circumstances .................... 91
Data Element 32-Additional Justifiable Homicide Circumstances ................. 93
Data Element 33-Type Injury .......................................................................... 94
Data Element 34-Offender Number to be Related .......................................... 96
Data Element 35-Relationship of Victim to Offender ..................................... 97
3.3.6
06/15/2020
Offender Segment ................................................................................................... 100
2019.2.1 NIBRS Technical Specification
viii
Data Element 36-Offender Sequence Number .............................................. 100
Data Element 37-Age of Offender................................................................. 101
Data Element 38-Sex of Offender ................................................................. 102
Data Element 39-Race of Offender ............................................................... 103
Data Element 39A-Ethnicity of Offender ...................................................... 104
3.3.7
Arrestee Segment/Group B Arrest Report Segment ............................................... 104
Data Element 40-Arrestee Sequence Number ............................................... 105
Data Element 41-Arrest Transaction Number ............................................... 106
Data Element 42-Arrest Date ........................................................................ 107
Data Element 43-Type of Arrest ................................................................... 108
Data Element 44-Multiple Arrestee Segments Indicator ............................... 109
Data Element 45-UCR Arrest Offense Code ................................................. 110
Data Element 46-Arrestee Was Armed With ................................................ 111
Data Element 46-Automatic Weapon Indicator ............................................ 112
Data Element 47-Age of Arrestee ................................................................. 113
Data Element 48-Sex of Arrestee .................................................................. 114
Data Element 49-Race of Arrestee ................................................................ 115
Data Element 50-Ethnicity of Arrestee ......................................................... 115
Data Element 51-Resident Status of Arrestee ............................................... 116
Data Element 52-Disposition of Arrestee Under 18 ...................................... 117
3.3.8
Zero Report Segment .............................................................................................. 117
Data Element (unnumbered)-Zero Report Month ......................................... 118
Data Element (unnumbered)-Zero Report Year ............................................ 119
4
Submission Specifications ................................................................................................ 120
4.1
Segment Length .......................................................................................................... 120
4.2
Data Records Must Be Initialized to Blanks ............................................................... 120
4.3
Codes Must Be Right-Justified With Zero Left-Fill ................................................... 120
4.4
Victim/Offender/Arrestee Sequence Numbers Can Have Gaps ................................. 120
4.5
Segment Levels ........................................................................................................... 120
4.6
Segment Action Types ................................................................................................ 121
4.6.1 I = Incident Report .................................................................................................. 121
4.6.2 A = Add .................................................................................................................. 121
4.6.3 D = Delete ............................................................................................................... 122
4.7
Zero Reporting ............................................................................................................ 123
5 Errors ................................................................................................................................. 124
5.1
Error-Data Set (EDS) .................................................................................................. 124
5.2
Error-Numbers and Messages ..................................................................................... 125
5.2.1 Structure Check Errors ............................................................................................ 126
5.2.2 Administrative Segment Errors............................................................................... 141
5.2.3 Offense Segment Errors .......................................................................................... 146
5.2.4 Property Segment Errors ......................................................................................... 154
5.2.5 Victim Segment Errors ........................................................................................... 162
5.2.6 Offender Segment Errors ........................................................................................ 173
5.2.7 Arrestee Segment Errors ......................................................................................... 175
5.2.8 Group B Arrest Report Segment Errors .................................................................. 179
06/15/2020
2019.2.1 NIBRS Technical Specification
ix
5.2.9 Zero Report Segment Errors ................................................................................... 183
5.2.10 Data Quality Checks ............................................................................................. 184
6 Record Layouts ................................................................................................................. 193
6.1
Administrative Segment Layout (Level 1) ................................................................. 193
6.2
Offense Segment Layout (Level 2) ............................................................................. 194
6.3
Property Segment Layout (Level 3) ............................................................................ 195
6.4
Victim Segment Layout (Level 4) .............................................................................. 196
6.5
Offender Segment Layout (Level 5) ........................................................................... 197
6.6
Arrestee Segment Layout (Level 6) ............................................................................ 198
6.7
Group B Arrest Report Segment Layout (Level 7) ..................................................... 199
6.8
Zero Report Segment Layout (Level 0) ...................................................................... 200
6.9
EDS Layout ................................................................................................................. 200
6.10 WDS Layout ............................................................................................................... 201
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
06/15/2020
2019.2.1 NIBRS Technical Specification
x
LIST OF TABLES
Table 3-1 Segment Length Edit Description ................................................................................ 14
Table 3-2 Segment Level Edit Description................................................................................... 15
Table 3-3 Segment Action Type Edit Description ........................................................................ 21
Table 3-4 Month of Submission Edit Description ........................................................................ 21
Table 3-5 Year of Submission Edit Description ........................................................................... 22
Table 3-6 City Indicator Edit Description .................................................................................... 23
Table 3-7 ORI Edit Description .................................................................................................... 24
Table 3-8 Judicial District Edit Description ................................................................................ 24
Table 3-9 Incident Number Edit Description............................................................................... 27
Table 3-10 Cargo Theft Edit Description .................................................................................... 29
Table 3-11 Incident Date Edit Description .................................................................................. 31
Table 3-12 Report Date Indicator Edit Description ...................................................................... 32
Table 3-13 Incident Hour Edit Description .................................................................................. 33
Table 3-14 Cleared Exceptionally Edit Description ..................................................................... 33
Table 3-15 Exceptional Clearance Date Edit Description ............................................................ 34
Table 3-16 UCR Offense Code Edit Description ......................................................................... 36
Table 3-17 Offense Attempted/Completed Edit Description........................................................ 37
Table 3-18 Offender Suspected of Using Edit Description .......................................................... 38
Table 3-19 Bias Motivation Edit Description ............................................................................... 39
Table 3-20 Location Type Edit Description ................................................................................. 41
Table 3-21 Number of Premises Entered Edit Description .......................................................... 44
Table 3-22 Method of Entry Edit Description .............................................................................. 44
Table 3-23 Type Criminal Activity/Gang Information Edit Description ..................................... 46
Table 3-24 Type Weapon/Force Involved Edit Description ......................................................... 49
Table 3-25 Automatic Weapon Indicator Edit Description .......................................................... 52
Table 3-26 Type Property Loss/Etc. Edit Description .................................................................. 53
Table 3-27 Property Description Edit Description ....................................................................... 62
Table 3-28 Illogical Property Description by Offense .................................................................. 65
Table 3-29 Value of Property Edit Description ............................................................................ 68
Table 3-30 Date Recovered Edit Description ............................................................................... 70
Table 3-31 Number of Stolen Motor Vehicles Edit Description .................................................. 71
Table 3-32 Number of Recovered Motor Vehicles Edit Description ........................................... 72
Table 3-33 Suspected Drug Type Edit Description ...................................................................... 73
Table 3-34 Estimated Drug Quantity Edit Description................................................................. 76
Table 3-35 Type Drug Measurement Edit Description................................................................. 77
Table 3-36 Victim Sequence Number Edit Description ............................................................... 79
Table 3-37 Victim Connected to UCR Offense Code Edit Description ....................................... 80
Table 3-38 Type of Victim Edit Description ................................................................................ 83
Table 3-39 Type of Officer Activity/Circumstance Edit Description .......................................... 85
Table 3-40 Officer Assignment Type Edit Description ................................................................ 86
Table 3-41 Jurisdiction Edit Description ...................................................................................... 87
Table 3-42 Age of Victim Edit Description.................................................................................. 88
Table 3-43 Sex of Victim Edit Description .................................................................................. 89
Table 3-44 Race of Victim Edit Description ................................................................................ 90
06/15/2020
2019.2.1 NIBRS Technical Specification
xi
Table 3-45 Ethnicity of Victim Edit Description.......................................................................... 91
Table 3-46 Resident Status of Victim Edit Description ............................................................... 91
Table 3-47 Aggravated Assault/Homicide Circumstances Edit Description ................................ 92
Table 3-48 Additional Justifiable Homicide Circumstances Edit Description ............................. 94
Table 3-49 Type of Injury Edit Description ................................................................................. 95
Table 3-50 Offender Number to be Related Edit Description ...................................................... 97
Table 3-51 Relationship of Victim to Offender Edit Description................................................. 98
Table 3-52 Offender Sequence Number Edit Description .......................................................... 100
Table 3-53 Age of Offender Edit Description ............................................................................ 101
Table 3-54 Sex of Offender Edit Description ............................................................................. 102
Table 3-55 Race of Offender Edit Description ........................................................................... 103
Table 3-56 Ethnicity of Offender Edit Description .................................................................... 104
Table 3-57 Arrestee Sequence Number Edit Description ........................................................... 105
Table 3-58 Arrest Transaction Number Edit Description ........................................................... 106
Table 3-59 Arrest Date Edit Description .................................................................................... 107
Table 3-60 Type of Arrest Edit Description ............................................................................... 108
Table 3-61 Multiple Arrestee Segments Indicator Edit Description .......................................... 109
Table 3-62 UCR Arrest Offense Code Edit Description ............................................................ 110
Table 3-63 Arrestee Was Armed With Edit Description ............................................................ 112
Table 3-64 Automatic Weapon Indicator Edit Description ........................................................ 113
Table 3-65 Age of Arrestee Edit Description ............................................................................. 114
Table 3-66 Sex of Arrestee Edit Description .............................................................................. 115
Table 3-67 Race of Arrestee Edit Description ............................................................................ 115
Table 3-68 Ethnicity of Arrestee Edit Description ..................................................................... 116
Table 3-69 Resident Status of Arrestee Edit Description ........................................................... 116
Table 3-70 Disposition of Arrestee Under 18 Edit Description ................................................. 117
Table 3-71 Zero Report Month Edit Description ........................................................................ 118
Table 3-72 Zero Report Year Edit Description........................................................................... 119
Table 5-1 EDS Record Layout .................................................................................................... 124
Table 5-2 Structure Check Errors ............................................................................................... 126
Table 5-3 Administrative Segment Errors .................................................................................. 141
Table 5-4 Offense Segment Errors ............................................................................................. 146
Table 5-5 Property Segment Errors ............................................................................................ 154
Table 5-6 Victim Segment Errors ............................................................................................... 162
Table 5-7 Mutually Exclusive Offenses for Error Code 478 Chart ............................................ 172
Table 5-8 Offender Segment Errors ............................................................................................ 173
Table 5-9 Arrestee Segment Errors............................................................................................. 175
Table 5-10 Group B Arrest Report Segment Errors ................................................................... 179
Table 5-11 Zero Report Segment Errors ..................................................................................... 183
06/15/2020
2019.2.1 NIBRS Technical Specification
xii
LIST OF FIGURES
Figure 2-1 Administrative Segment Layout (Level 1).................................................................... 5
Figure 2-2 Offense Segment Layout (Level 2) ............................................................................... 6
Figure 2-3 Property Segment Layout (Level 3) .............................................................................. 7
Figure 2-4 Victim Segment Layout (Level 4)................................................................................. 8
Figure 2-5 Offender Segment Layout (Level 5) ............................................................................. 9
Figure 2-6 Arrestee Segment Layout (Level 6) ............................................................................ 10
Figure 2-7 Group B Arrest Report Segment Layout (Level 7) ..................................................... 11
Figure 2-8 Zero Report Segment Layout (Level 0) ...................................................................... 12
Figure 6-1 Administrative Segment Layout (Level 1)................................................................ 193
Figure 6-2 Offense Segment Layout (Level 2) ........................................................................... 194
Figure 6-3 Property Segment Layout (Level 3) .......................................................................... 195
Figure 6-4 Victim Segment Layout (Level 4)............................................................................. 196
Figure 6-5 Offender Segment Layout (Level 5) ......................................................................... 197
Figure 6-6 Arrestee Segment Layout (Level 6) .......................................................................... 198
Figure 6-7 Group B Arrest Report Segment Layout (Level 7) ................................................... 199
Figure 6-8 Zero Report Segment Layout (Level 0) .................................................................... 200
Figure 6-9 EDS Layout ............................................................................................................... 200
Figure 6-10 WDS Layout............................................................................................................ 201
06/15/2020
2019.2.1 NIBRS Technical Specification
xiii
1 BACKGROUND
This National Incident-Based Reporting System (NIBRS) Technical Specification has been
developed in accordance with the Federal Bureau of Investigation (FBI) 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, 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_20161122_NIBRS Hate Crime_SubmitterID = Submitting Agency
Identifier (ORI)
Date = the date the submission was generated
Submission format is either NIBRS or SRS (Summary Reporting System)
06/15/2020
2019.2.1 NIBRS Technical Specification
1
Additional Information: Hate Crime, Cargo Theft, Arson, Homicide, etc.
Series Number = number of submission per year, 001 indicates the first submission of the year
06/15/2020
2019.2.1 NIBRS Technical Specification
2
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
3
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)
06/15/2020
2019.2.1 NIBRS Technical Specification
4
Administrative Segment Layout (Level 1)
Segment Length:
SEGMENT
LENGTH
1-4
SEGMENT
LEVEL
5
0087 (without Cargo Theft)
0088 (with Cargo Theft)
0091 (Federal Agency Reporting Only - Judicial District Code)
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
DATA ELEMENT 3 INCLUDES 3 ELEMENTS
REPORT
INCIDENT
DATE
INCIDENT
DATE
INDICATOR
HOUR
(3)
(3)
(3)
38-45
46
47-48
YEAR OF
SUBMISSION
9-12
CLEARED
EXCEPTIONALLY
(4)
49
EXCEPTIONAL CLEARANCE OFFENSE CODE OCCURS 10
TIMES
EXCEPTIONAL
CLEARANCE
EXCEPTIONAL
OFFENSE CODE
CLEARNCE
THROUGH
#10
OFFENSE CODE #1
58-60
85-87
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
EXCEPTIONAL
CLEARANCE
DATE
(5)
50-57
OPTIONAL
CARGO
THEFT
(2A)
88
FEDERAL
AGENCY
REPORTING
ONLY
FEDERAL
JUDICIAL
DISTRICT
CODE
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
06/15/2020
2019.2.1 NIBRS Technical Specification
5
Offense Segment Layout (Level 2)
Segment Length:
SEGMENT
LENGTH
1-4
SEGMENT
LEVEL
5
0063 (1 Bias Motivation)
0071 (5 Bias Motivations)
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
DATA ELEMENT 8 OCCURS 3 TIMES
OFFENDER
OFFENDER
SUSPECTED OF
SUSPECTED OF
USING #1
USING #3
THROUGH
(8)
(8)
42
44
YEAR OF
SUBMISSION
9-12
LOCATION
TYPE
(9)
45-46
CITY
INDICATOR
13-16
NUMBER OF
PREMISES
ENTERED
(10)
47-48
ORI
(1)
17-25
METHOD
OF ENTRY
(11)
49
INCIDENT
NUMBER
(2)
26-37
UCR
OFFENSE
CODE
(6)
38-40
OFFENSE
ATTEMPTED/
COMPLETED
(7)
41
DATA ELEMENT 12 OCCURS 3 TIMES
TYPE
TYPE
CRIMINAL
CRIMINAL
ACTIVITY #1
ACTIVITY #3
THROUGH
(12)
(12)
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
INVOLVED #3
INDICATOR #3
THROUGH
(13)
(13)
(13)
(13)
53-54
55
59-60
61
BIAS MOTIVATION #2 - #5 ARE OPTIONAL
DATA ELEMENT 8A OCCURS 4 TIMES
BIAS
MOTIVATION #1
(8A)
62-63
BIAS
MOTIVATION #2
(8A)
64-65
THROUGH
BIAS
MOTIVATION #5
(8A)
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
06/15/2020
2019.2.1 NIBRS Technical Specification
6
Property Segment Layout (Level 3)
Segment Length:
SEGMENT
LENGTH
1-4
0307
SEGMENT
LEVEL
5
SEGMENT
ACTION
TYPE
6
PROPERTY
DESCRIPTION
#1 (15)
39-40
VALUE OF
PROPERTY #1
(16)
41-49
NUMBER OR
STOLEN
MOTOR
VEHICLES
(18)
NUMBER OF
RECOVERED
MOTOR
VEHICLES
(19)
229-230
231-232
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
DATA ELEMENTS 15, 16, & 17 AS A GROUP OCCUR 10 TIMES
DATE
PROPERTY
VALUE OF
RECOVERED #1
DESCRIPTION #10
PROPERTY #10
THROUGH
(17)
(15)
(16)
50-57
210-211
212-220
TYPE
PROPERTY
LOSS/ETC.
(14)
38
DATE
RECOVERED #10
(17)
221-228
DATA ELEMENTS 20, 21, & 22 AS A GROUP OCCUR 3 TIMES
ESTIMATED
SUSPECTED
DRUG
TYPE DRUG
DRUG TYPE #1
QUANTITY #1
MEASUREMENT #1
THROUGH
(20)
(21)
(22)
233
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
234-245
246-247
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
06/15/2020
2019.2.1 NIBRS Technical Specification
7
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:
SEGMENT
LENGTH
1-4
SEGMENT
LEVEL
5
0129 (without LEOKA)
0141 (with LEOKA)
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
DATA ELEMENT 24 OCCURS 10 TIMES
VICTIM
VICTIM
CONNECTED TO
CONNECTED TO
UCR OFFENSE #1 THROUGH
UCR OFFENSE #10
(24)
(24)
41-43
68-70
YEAR OF
SUBMISSION
9-12
TYPE OF
VICTIM
(25)
71
DATA ELEMENT 31 OCCURS 2 TIMES
AGGRAVATED
AGGRAVATED
ASSAULT/HOMICIDE
ASSAULT/HOMICIDE
CIRCUMSTANCES #1
CIRCUMSTANCES #2
(31)
(31)
80-81
82-83
RESIDENT
STATUS
OF
VICTIM
(30)
79
OFFENDER
NUMBER TO BE
RELATED #1
(34)
90-91
CITY
INDICATOR
13-16
AGE OF
VICTIM
(26)
72-75
ADDITIONAL
JUSTIFIABLE
HOMICIDE
CIRCUMSTANCES
(32)
84
ORI
(1)
17-25
SEX OF
VICTIM
(27)
76
INCIDENT
NUMBER
(2)
26-37
RACE OF
VICTIM
(28)
77
VICTIM
SEQUENCE
NUMBER
(23)
38-40
ETHNICITY
OF VICTIM
(29)
78
DATA ELEMENT 33 OCCURS 5 TIMES
TYPE
INJURY #1
(33)
85
DATA ELEMENTS 34 & 35 AS A GROUP OCCUR 10 TIMES
RELATIONSHIP
OFFENDER
RELATIONSHIP
OF VICTIM TO
NUMBER TO BE
OF VICTIM TO
OFFENDER #1
RELATED #10
OFFENDER #10
THROUGH
(35)
(34)
(35)
92-93
126-127
128-129
THROUGH
TYPE
INJURY #5
(33)
89
LEOKA DATA ELEMENTS ARE OPTIONAL
TYPE OF OFFICER
OFFICER
OFFICER –
ACTIVITY/
ASSIGNMENT
ORI OTHER
CIRCUMSTANCE
TYPE
JURISDICTION
(25A)
(25B)
(25C)
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
06/15/2020
2019.2.1 NIBRS Technical Specification
8
Offender Segment Layout (Level 5)
Segment Length:
0045 (without Offender Ethnicity)
0046 (with Offender Ethnicity)
SEGMENT
LENGTH
1-4
SEGMENT
LEVEL
5
OFFENDER
SEQUENCE
NUMBER
(36)
38-39
AGE OF
OFFENDER
(37)
40-43
SEGMENT
ACTION
TYPE
6
SEX OF
OFFENDER
(38)
44
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
RACE OF
OFFENDER
(39)
45
OPTIONAL
ETHNICITY OF
OFFENDER
(39A)
46
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
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
06/15/2020
2019.2.1 NIBRS Technical Specification
9
Arrestee Segment Layout (Level 6)
Segment Length:
SEGMENT
LENGTH
1-4
ARREST
DATE
(42)
52-59
AGE OF
ARRESTEE
(47)
71-74
SEGMENT
LEVEL
5
TYPE OF
ARREST
(43)
60
SEX OF
ARRESTEE
(48)
75
0110
SEGMENT
ACTION
TYPE
6
MULTIPLE
ARRESTEE
SEGMENTS
INDICATOR
(44)
61
RACE OF
ARRESTEE
(49)
76
MONTH OF
SUBMISSION
7-8
UCR
ARREST
OFFENSE
CODE
(45)
62-64
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
ARRESTEE
SEQUENCE
NUMBER
(40)
38-39
ARREST
TRANSACTION
NUMBER
(41)
40-51
DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE
AUTOMATIC
ARRESTEE
AUTOMATIC
WAS ARMED
WEAPON
WAS ARMED
WEAPON
WITH #1
INDICATOR #1
WITH #2
INDICATOR #2
(46)
(46)
(46)
(46)
65-66
67
68-69
70
ETHNICITY OF
ARRESTEE
(50)
77
RESIDENT
STATUS OF
ARRESTEE
(51)
78
DISPOSITION
OF ARRESTEE
UNDER 18
(52)
79
CLEARANCE
INDICATOR
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
06/15/2020
2019.2.1 NIBRS Technical Specification
10
2.3.1 Group B Arrest Report Segment Layout (Level 7)
Segment Length:
SEGMENT
LENGTH
1-4
TYPE OF
ARREST
(43)
48
SEGMENT
LEVEL
5
0066 (State, Local, and Tribal)
0069 (Federal Agency Reporting Only)
SEGMENT
ACTION
TYPE
6
UCR
ARREST
OFFENSE
CODE
(45)
49-51
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
ARREST
TRANSACTION
NUMBER
(41)
26-37
ARRESTEE
SEQUENCE
NUMBER
(40)
38-39
ARREST
DATE
(42)
40-47
DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE
WAS ARMED
WITH #1
(46)
52-53
AUTOMATIC
WEAPON
INDICATOR #1
(46)
54
RACE OF
ARRESTEE
(49)
ETHNICITY OF
ARRESTEE
(50)
RESIDENT
STATUS OF
ARRESTEE
(51)
DISPOSITION
OF ARRESTEE
UNDER 18
(52)
63
64
65
66
ARRESTEE
WAS ARMED
WITH #2
(46)
55-56
AUTOMATIC
WEAPON
INDICATOR #2
(46)
57
AGE OF
ARRESTEE
(47)
58-61
SEX OF
ARRESTEE
(48)
62
FEDERAL
AGENCY
REPORTING
ONLY
FEDERAL
JUDICIAL
DISTRICT
CODE
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.
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
11
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:
SEGMENT
LENGTH
1-4
SEGMENT
LEVEL
5
0043
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
ZERO
REPORT
MONTH
38-39
ZERO
REPORT
YEAR
40-43
Figure 2-8 Zero Report Segment Layout (Level 0)
06/15/2020
2019.2.1 NIBRS Technical Specification
12
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
13
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
4-Character Numeric
1–4
Once per Segment
Yes
Table 3-1 Segment Length Edit Description
Edit Description
The referenced data element in an incident must contain data when the
referenced data element is mandatory or when the conditions are met for
data that must be entered into a conditionally mandatory field.
Associated Error
Code
001, 101, 201,301,
401, 501,601, 701
Data Values:
Level 1
Level 1
Level 2
Level 2
Level 3
Level 4
Level 4
Level 5
Level 5
Level 6
06/15/2020
Administrative Segment WITHOUT Cargo Theft (Data Element 2A)
Administrative Segment WITH Cargo Theft (Data Element 2A)
Offense Segment WITH Bias Motivation #1 (Data Element 8A)
Offense Segment WITH Bias Motivations #2–#5 (Data Element 8A)
Property Segment
Victim Segment WITHOUT LEOKA (Data Elements 25A–C)
Victim Segment WITH LEOKA (Data Elements 25A–C)
Offender Segment WITHOUT Offender Ethnicity (Data Element 39A)
Offender Segment WITH Offender Ethnicity (Data Element 39A)
Arrestee Segment
2019.2.1 NIBRS Technical Specification
0087
0088
0063
0071
0307
0129
0141
0045
0046
0110
14
Level 7
Level 0
Group B Arrest Report Segment
Zero Report Segment
0066
0043
Segment Level
Segment Level identifies the segment in a submission.
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
1-Character Alphanumeric
5
Once per Segment
Yes
Table 3-2 Segment Level Edit Description
Segment Level Edit Descriptions
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 met for
data that must be entered into a conditionally mandatory field.
001, 101, 201,301,
401, 501,601, 701
The ORI already exists in the reference table for a different agency. Verify
that the ORI is accurate.
931
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
for the data submission.
932
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
that the submitting agency is now providing its own information and is no
longer in covered by status.
933
The ORI submitted is in delete status. Verification is needed to ensure this
is accurate.
934
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,
4, 5 must be written in that order, not as 1, 2, 2, 5, 3, 4, 4, 4.
050
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
Incident Report.
055
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
Data Element 6 (UCR Offense Code) in Data Element 24 (Victim Connected
to UCR Offense Code).
065
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
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).
070
06/15/2020
2019.2.1 NIBRS Technical Specification
15
Segment Level Edit Descriptions
Edit Description
Associated Error
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
(Exceptional Clearance Date) when Data Element 4 (Cleared Exceptionally)
contains a data value other than N = Not Applicable (indicating the incident
is cleared exceptionally).
071
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
incident (i.e., 250 = Counterfeiting/Forgery and 280 = Stolen Property
Offenses, 58B = Export Violations*).
072
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
Element 19 (Number of Recovered Motor Vehicles) within the same
incident.
073
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 =
Kidnapping/Abduction, 35A = Drug/Narcotic Offenses, or Gambling
Offenses.
074
Segment Levels 1, 2, 4, and 5 (Administrative Segment, Offense Segment,
Victim Segment, and Offender Segment) with Segment Action Type
I = Incident Report must be submitted for each Group A Incident Report;
they are mandatory.
075
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 =
Explosives*, 26H = Money Laundering*, Commerce Violations*, or
Gambling Offenses.
*Denotes offenses for federal and tribal LEA reporting only
076
06/15/2020
2019.2.1 NIBRS Technical Specification
16
Segment Level Edit Descriptions
Edit Description
Associated 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*
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
080
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 is a
Crime Against Property must contain at least two offender sequence
numbers in Data Element 34 (Offender Number to be Related) when there
are two or more 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.
085
Segment Level 6 (Arrestee Segment) and Segment Level 7 (Group B Arrest
Report Segment) cannot have the same data values entered in Data
Element 2 (Incident Number) and Data Element 41 (Arrest Transaction
Number), respectively, for the same ORI.
088
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
Administrative Segments within that ORI must be formatted using 0088.
178
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
this case, two Offense Segments were submitted having the same offense
in Data Element 6 (UCR Offense Code).
262
(Offense Segment) May be submitted only 10 times for each Group A
Incident Report; 10 offense codes are allowed for each incident.
263
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
17
Segment Level Edit Descriptions
Edit Description
Associated Error
Code
(Property Segment) When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot contain duplicates.
Example, two property segments cannot be submitted having the same
entry in Data Element 14 (Type Property Loss/Etc.).
376
(Property Segment) Cannot be submitted with 10 = Drugs/Narcotics in Data
Element 15 (Property Description) and blanks in Data Element 16 (Value of
Property) unless Data Element 6 (UCR Offense Code) is 35A = Drug/
Narcotic Violations.
382
(Victim Segment) When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot contain duplicates. In
this case, two victim segments were submitted having the same entry in
Data Element 23 (Victim Sequence Number).
451
(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
not submitted as Offense Segments. A victim cannot be connected to an
offense when the offense itself is not present.
466
(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
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.
However, there may be some situations where only one of the victims is
also the offender, but where the other victim(s) is not also the offender(s).
470
(Victim Segment) Cannot be submitted multiple times with VO = Victim Was
Offender in Data Element 35 (Relationship of Victim to Offender) when Data
Element 34 (Offender Number to be Related) contains the same data value
(indicating the same offender).
474
(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
same offender.
476
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
Data Element 6 (UCR Offense Code) should have been submitted, or
multiple individual victims should have been submitted for the incident
report.
480
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
18
Segment Level Edit Descriptions
Edit Description
Associated Error
Code
(Offender Segment) When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot contain duplicates. In
this case, two Offender Segments were submitted having the same entry in
Data Element 36 (Offender Sequence Number).
551
(Offender Segment) When multiple Offender Segments are submitted, none
can contain a 00 = Unknown value because the presence of 00 indicates
that the number of offenders is unknown. In this case, multiple offenders
were submitted, but one of the segments contains the 00 = Unknown value.
555
(Offender Segment) None of the Offender Segments contain all known
values for Age, Sex, and Race. When an incident is cleared exceptionally
(Data Element 4 contains an A through E), one offender must have all
known values.
558
(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
for age, sex, and race.
*Denotes offenses for federal and tribal LEA reporting only
559
Segment Level 5 (Offender Segment) must contain a data value for at least
one offender in Data Element 38 (Sex of Offender) that is not the same sex
that is entered in Data Element 27 (Sex of Victim) when Data Element 6
(UCR Offense Code) is 11A = Rape. The offender must be connected to the
victim in Data Element 34 (Offender Number to be Related) unless offender
number in Data Element 34 (Offender Number to be Related) is
00 = Unknown.
560
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
within that ORI must be formatted using 0046.
584
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
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
656
19
Segment Level Edit Descriptions
Edit Description
Associated Error
Code
(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
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.
661
(Arrestee Segment) Group A Incident Reports cannot have arrests when
Data Element 6 (UCR Offense Code) is 09C = Justifiable Homicide. By
definition, a justifiable homicide never involves an arrest of the offender (the
person who committed the justifiable homicide).
669
(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
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
Data Element 40 (Arrestee Sequence Number) is unique for each Arrestee
Segment submitted so that duplication does not occur.
751
759
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:
Format:
Position:
Occurrence:
06/15/2020
A, B
1-Character Alphabetic
6
Once per Segment
2019.2.1 NIBRS Technical Specification
20
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
met for data that must be entered into a conditionally mandatory
field.
001, 101, 201, 301, 401,
501, 601, 701
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
2-Character Numeric (MM)
7–8
Once per Segment
Yes
Table 3-4 Month of Submission Edit Description
Edit Description
The referenced data element in an incident must contain data when the
referenced data element is mandatory or when the conditions are met for
data that must be entered into a conditionally mandatory field.
06/15/2020
2019.2.1 NIBRS Technical Specification
Associated Error
Code
001, 101, 201, 301,
401, 501, 601, 701
21
Edit Description
Associated Error
Code
Month of Submission and Year of Submission must contain the same data
values for each segment in a NIBRS submission. The first segment
processed will be compared with all other segments to check for this
condition.
058
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
submitted for a future month/year.
060
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
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
4-Character Numeric (YYYY)
9–12
Once per Segment
Yes
Table 3-5 Year of Submission 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 met for data
that must be entered into a conditionally mandatory field.
001, 101, 201,
301, 401, 501,
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
will be compared with all other segments to check for this condition.
058
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
submitted for a future month/year.
060
Data Values: 1991–Current Year
06/15/2020
2019.2.1 NIBRS Technical Specification
22
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
4-Character Alphanumeric
13–16
Once per Segment
Conditional
Table 3-6 City Indicator Edit Description
Edit Description
The referenced data element must contain a valid data value when it
is entered; blank is permissible on nonmandatory fields.
Associated Error Code
104, 204, 304, 404, 504, 604,
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
06/15/2020
A, B
9-Character Alphanumeric
17–25
Once per Segment
Yes
2019.2.1 NIBRS Technical Specification
23
Table 3-7 ORI Edit Description
ORI Data Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 1
(ORI) The referenced data element in an incident must contain
data when the referenced data element is mandatory or when
the conditions are met for data that must be entered into a
conditionally mandatory field.
001, 101, 201,
301, 401, 501,
601, 701
Data Element 1
(ORI) Must be a valid nine-character NCIC ORI.
952, 931-934
Data Element 1
(ORI) First two positions must be the code of the state (e.g., SC,
MD) in which the incident occurred. For nonfederal participants,
every record must have the same code.
059
Data Values: Valid ORI values are assigned by the NCIC and contain the characters A–Z
(capital letters only) and 0–9.
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:
Format:
Position:
Position:
Occurrence:
Mandatory:
Edits:
A, B
3-Character Alphanumeric
89-91 in Level 1 – Administrative Segment
67-69 in Level 7 – Group B Arrest Report Segment
Once per Segment
Yes (Mandatory for federal agencies only)
Table 3-8 Judicial District Edit Description
Judicial District Data Element Edits
Data Element
Data Element
1A
Edit Description
(JD) The referenced data element in an incident must contain
data when the referenced data element is mandatory or when
the conditions are met for data that must be entered into a
conditionally mandatory field.
Associated
Error Code
101, 701
Data Values:
001 = Alabama, Northern District
002 = Alabama, Middle District
003 = Alabama, Southern District
004 = Florida, Southern District
06/15/2020
2019.2.1 NIBRS Technical Specification
24
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
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
06/15/2020
2019.2.1 NIBRS Technical Specification
25
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
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
06/15/2020
2019.2.1 NIBRS Technical Specification
26
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.
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
12-Character Alphanumeric
26–37
Once per Segment
Yes
Table 3-9 Incident Number Edit Description
Incident Number Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 2
(Incident Number) The referenced data element in an
Incident must contain data when the referenced data element
is mandatory or when the conditions are met for data that
must be entered into a conditionally mandatory field.
001, 101, 201, 301,
401, 501, 601
Data Element 2
(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
number. Some agencies ensure uniqueness by prefixing
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.
056
Data Element 2
A Group A Incident Number and a Group B Arrest Report
Arrest Transaction Number cannot have the same number
within the same ORI.
088
Data Element 2
(Incident Number) Zero-Reporting Segment (Level 0) must
contain 12 zeros as the Incident Number.
092
Data Element 2
(Incident Number) Must be blank right-fill if under 12
characters in length. Cannot have embedded blanks between
the first and last characters entered.
115, 215, 315, 415,
515, 615
Data Element 2
(Incident Number) Must be left-justified with blank right-fill if
under 12 characters in length.
116, 216, 316, 416,
516, 616
06/15/2020
2019.2.1 NIBRS Technical Specification
27
Incident Number Data Element Edits
Data Element
Edit Description
Associated Error
Code
(Incident Number) Must contain a valid character combination
of the following:
Data Element 2
• A–Z (capital letters only)
• 0–9
• Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not valid.
Data Values: Administrative Segment
Offense Segment
Property Segment
Victim Segment
Offender Segment
Arrestee Segment
A–Z (capital letters only)
0–9
Hyphen
117, 217, 317, 417,
517, 617
(Level 1)
(Level 2)
(Level 3)
(Level 4)
(Level 5)
(Level 6)
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
06/15/2020
2019.2.1 NIBRS Technical Specification
28
•
•
•
•
•
26E = Wire Fraud
26F = Identity Theft
26G = Hacking/Computer Invasion
510 = Bribery
270 = Embezzlement
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
88
Once per Administrative Segment
Optional/Conditional
Table 3-10 Cargo Theft Edit Description
Incident Number Data Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 2A
(Cargo Theft) The referenced data element must contain a valid data
value when it is entered; blank is permissible on nonmandatory fields.
104
(Cargo Theft) must be blank, unless Data Element 6 (UCR Offense
Code) includes at least one of the following:
Data Element 2A
06/15/2020
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
270 = Embezzlement
510 = Bribery
2019.2.1 NIBRS Technical Specification
119
29
Incident Number Data Element Edits
Data Element
Edit Description
Associated
Error Code
(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:
Data Element 2A
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
270 = Embezzlement
510 = Bribery
122
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.
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
06/15/2020
A
8-Character Numeric (YYYYMMDD)
38–45
Once per Administrative Segment
Yes
2019.2.1 NIBRS Technical Specification
30
Table 3-11 Incident Date Edit Description
Incident Date Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 3
The referenced data element in an incident must contain
data when the referenced data element is mandatory or
when the conditions are met for data that must be entered
into a conditionally mandatory field.
101
Data Element 3
(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
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).
Also, the date cannot exceed the current date.
105
Data Element 3
(Incident Date) The UCR Program has determined that an
ORI will no longer be submitting data to the FBI as of an
inactive date. The UCR Program will not accept data from
the ORI after this date.
118
Data Element 3
(Incident Date) The date cannot be later than the year and
month the electronic submission represents. For example,
the May 1999 electronic submission cannot contain
incidents happening after this date.
170
Data Element 3
(Incident Date) cannot be earlier than 01/01/1991. This edit
will preclude dates that are obviously incorrect since the
FBI began accepting NIBRS data on this date.
172
Data Element 3
A Group A Incident Report was submitted with Data
Element 3 (Incident Date/Hour) containing a date that
occurred before the agency converted to NIBRS. Because
of this, the record was rejected.
173
Data Element 3
(Incident Date) is missing for a Group A Incident Report
with a Segment Action Type of D = Delete; must be
populated with a valid data value and cannot be blank.
197
Data Element 3
(Incident Date) is missing for a Group A Incident Report
with a Segment Action Type of D = Delete; at least one
Group A Incident Report is on file that matches Data
Element 2 (Incident Number) with an Incident Date outside
the two year window.
198
Data Element 3
(Incident Date) is missing for a Group A Incident Report
with a Segment Action Type of D = Delete; must be
populated with a valid data value and cannot be blank.
Incident Number matches multiple Group A Incident
Reports.
199
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/15/2020
2019.2.1 NIBRS Technical Specification
31
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
46
Once per Administrative Segment
Conditional
Table 3-12 Report Date Indicator Edit Description
Report Date Indicator Element Edits
Data Element
Data Element
Data
Element
Data Element 3
(Report Date Indicator) The referenced data element must contain
a valid data value when it is entered; blank is permissible on
nonmandatory fields.
104
Data Element 3
(Report Date Indicator) This field must be blank if the Incident Date
is known. If the Incident Date is unknown, then the Report Date
would be entered instead and must be indicated with an “R” in the
Report Indicator field within the Administrative Segment.
151
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
06/15/2020
A
2-Character Numeric (HH)
47–48
Once per Administrative Segment
Conditional, if known it must be entered
2019.2.1 NIBRS Technical Specification
32
Table 3-13 Incident Hour Edit Description
Incident Hour Data Element Edits
Data Element
Edit Description
Data Element 3
(Incident Hour) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
Associated Error
Code
104
(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
Data Element 3
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.
(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 Element 3 (Incident Date/Hour)
must be populated with a valid hour (00-23). Incident Hour
Unknown (Blank) is not a valid entry.
152
106
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
49
Once per Administrative Segment
Yes
Table 3-14 Cleared Exceptionally Edit Description
Cleared Exceptionally Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 4
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 (Exceptional
Clearance Date) when Data Element 4 (Cleared Exceptionally)
contains a data value other than N = Not Applicable (indicating
the incident is cleared exceptionally).
071
06/15/2020
2019.2.1 NIBRS Technical Specification
33
Cleared Exceptionally Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 4
(Cleared Exceptionally) The referenced data element in an
incident must contain data when the referenced data element
is mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
101
Data Element 4
(Cleared Exceptionally) The referenced data element must
contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
104
Data Element 4
(Cleared Exceptionally) Cannot be N = Not Applicable if Data
Element 5 (Exceptional Clearance Date) is entered.
153
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:
Format:
Position:
Occurrence:
Mandatory:
A
8-Character Numeric (YYYYMMDD)
50–57
Once per Administrative Segment
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
Data Element
Data Element 5
06/15/2020
Edit Description
(Exceptional Clearance Date) The referenced data element
must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
2019.2.1 NIBRS Technical Specification
Associated Error
Code
104
34
Incident Hour Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 5
(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).
Also, the date cannot exceed the current date.
105
Data Element 5
(Exceptional Clearance Date) is earlier than Data Element 3
(Incident Date/Hour).
155
Data Element 5
(Exceptional Clearance Date) must be present if the case
was cleared exceptionally. Data Element 4 (Cleared
Exceptionally) has an entry of A through E; therefore, the
date must also be entered.
156
Data Element 5
(Exceptional Clearance Date) cannot contain a date earlier
than the date the LEA began submitting data via NIBRS.
173
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.
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
06/15/2020
2019.2.1 NIBRS Technical Specification
35
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
3-Character Alphanumeric
38–40
Once per Offense Segment
Yes
Table 3-16 UCR Offense Code Edit Description
UCR Offense Code Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 6
(UCR Offense Code) The referenced data element in an
incident must contain data when the referenced data element
is mandatory or when the conditions are met for data that
must be entered into a conditionally mandatory field.
201
Data Element 6
(UCR Offense Code) The referenced data element must
contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
204
Data Element 6
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
49A = Harboring Escapee/Concealing from Arrest
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
250
06/15/2020
2019.2.1 NIBRS Technical Specification
36
UCR Offense Code Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 6
When a Group A Incident Report is submitted, the individual
segments comprising the incident cannot contain duplicates.
In this case, two Offense Segments were submitted having
the same offense in Data Element 6 (UCR Offense Code).
262
Data Element 6
(UCR Offense Code) Data Element 6 (UCR Offense Code)
must be a Group A UCR Offense Code, not a Group B
Offense Code.
264
Data Element 6
When a Justifiable Homicide is reported, no other offense may
be reported in the Group A Incident Report. These should be
submitted on another Group A Incident Report.
266
Data Element 6
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,
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)
268
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.
Note: Attempted Murder should be reported as Aggravated Assault and all Assault Offenses
should be classified as C = Completed.
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
41
Once per Offense Segment
Yes
Table 3-17 Offense Attempted/Completed Edit Description
Offense Attempted/Completed Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 7
(Offense Attempted/Completed) The referenced data element
in an incident must contain data when the referenced data
element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
201
06/15/2020
2019.2.1 NIBRS Technical Specification
37
Offense Attempted/Completed Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 7
(Offense Attempted/Completed) Must be a valid code of
A = Attempted or C = Completed.
251
Data Element 7
(Offense Attempted/Completed) Code must be
C = Completed if Data Element 6 (UCR Offense Code) is an
Assault, Homicide, or 360 = Failure to Register as a Sex
Offender*.
*Denotes offenses for federal and tribal LEA reporting only
256
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:
Format:
Position:
A
1-Character Alphabetic
42-Activity 1
43-Activity 2
44-Activity 3
Occurrence: 3 times per Offense Segment
Mandatory: Yes
Edits:
Table 3-18 Offender Suspected of Using Edit Description
Offender(s) Suspected of Using Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 8
(Offender Suspected of Using) The referenced data element in
an incident must contain data when the referenced data
element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
201
Data Element 8
(Offender Suspected of Using) The referenced data element
must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
204
Data Element 8
(Offender Suspected of Using) 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.
206
06/15/2020
2019.2.1 NIBRS Technical Specification
38
Offender(s) Suspected of Using Data Element Edits
Data Element
Edit Description
Associated Error
Code
(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.
Data Element 8
•
•
•
•
207A ERROR MUTUALLY EXCLUSIVE VALUE SUSPECTED OF USING
207B ERROR MUTUALLY EXCLUSIVE VALUE BIAS MOTIVATION
207C ERROR MUTUALLY EXCLUSIVE VALUE CRIMINAL ACTIVITY / GANG INFORMATION
207D ERROR MUTUALLY EXCLUSIVE VALUE WEAPON CODE
207
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:
Format:
Position:
A
2-Character Numeric
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:
Table 3-19 Bias Motivation Edit Description
Bias Motivation Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 8A
(Bias Motivation) The referenced data element in an Incident
must contain data when the referenced data element is
mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
201
Data Element 8A
(Bias Motivation) The referenced data element must contain
a valid data value when it is entered; blank is permissible on
nonmandatory fields.
204
06/15/2020
2019.2.1 NIBRS Technical Specification
39
Bias Motivation Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 8A
(Bias Motivation) 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.
206
(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.
Data Element 8A
•
•
•
•
Data Element 8A
207A ERROR MUTUALLY EXCLUSIVE VALUE –
SUSPECTED OF USING
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
(UCR Offense Code) is 09C = Justifiable Homicide.
207
270
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
28 = Anti-Mormon
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
06/15/2020
2019.2.1 NIBRS Technical Specification
40
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
2-Character Numeric
45–46
Once per Offense Segment
Yes
Table 3-20 Location Type Edit Description
Location Type Data Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 9
(Location Type) The referenced data element in an Incident
must contain data when the referenced data element is
mandatory or when the conditions are met for data that must
be entered into a conditionally mandatory field.
201
Data Element 9
(Location Type) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
204
06/15/2020
2019.2.1 NIBRS Technical Specification
41
Location Type Data Element Edits
Data Element
Edit Description
Associated Error
Code
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:
Data Element 9
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
26H = Money Laundering*
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
205
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
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
06/15/2020
2019.2.1 NIBRS Technical Specification
42
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
22 = School/College
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.
Group:
Format:
Position:
Occurrence:
Mandatory:
06/15/2020
A
2-Character Numeric
47–48
Once per Offense Segment
Conditional
2019.2.1 NIBRS Technical Specification
43
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
Data Element
Associated
Error Code
Edit Description
Data Element 10
Data Element 10 (Number of Premises Entered) is not a numeric
entry of 01 through 99.
202
Data Element 10
(Number of Premises Entered) When Data Element 10 (Number of
Premises Entered) is entered, Data Element 9 (Location Type) must
be 14 = Hotel/Motel/Etc. or 19 = Rental Storage Facility, and Data
Element 6 (UCR Offense Code) must be 220 = Burglary/Breaking &
Entering.
252
Data Element 10
(Number of Premises Entered) Must be entered if offense code is
220 = Burglary/Breaking & Entering and if Data Element 9 (Location
Type) contains 14 = Hotel/Motel/Etc. or 19 = Rental Storage Facility.
257
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:
Format:
Position:
Occurrence:
Mandatory:
A
1-Character Alphabetic
49
Once per Offense Segment
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
Data Element
Edit Description
Associated
Error Code
Data Element 11
(Method of Entry) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
204
Data Element 11
(Method of Entry) Data element was not entered; it must be
entered when UCR Offense Code of 220 = Burglary/Breaking &
Entering has been entered.
253
Data Element 11
(Method of Entry) Data element only applies to UCR Offense
Code of 220 = Burglary/Breaking & Entering. Since a Burglary
offense was not entered, the Method of Entry should not have
been entered.
254
06/15/2020
2019.2.1 NIBRS Technical Specification
44
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:
Format:
Position:
A
1-Character Alphabetic
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
Edits:
06/15/2020
2019.2.1 NIBRS Technical Specification
45
Table 3-23 Type Criminal Activity/Gang Information Edit Description
Type of Criminal Activity/Gang Information Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 12
(Type Criminal Activity/Gang Information) The referenced
data element must contain a valid data value when it is
entered; blank is permissible on nonmandatory fields.
204
Data Element 12
(Type Criminal Activity/Gang Information) 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.
206
Data Element 12
(Type Criminal Activity/Gang Information) 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.
207
06/15/2020
2019.2.1 NIBRS Technical Specification
46
Type of Criminal Activity/Gang Information Element Edits
Data Element
Edit Description
Associated Error
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:
Data Element 12
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*
*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
06/15/2020
2019.2.1 NIBRS Technical Specification
47
Type of Criminal Activity/Gang Information Element Edits
Data Element
Edit Description
Associated Error
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:
Data Element 12
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
220
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
48
Group:
Format:
Position:
A
2-Character Numeric
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
Data Element
Edit Description
Associated Error
Code
Data Element 13
(Type Weapon/Force Involved) The referenced data element
must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
204
Data Element 13
(Type Weapon/Force Involved) 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.
206
Data Element 13
(Type Weapon/Force Involved) 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.
207
06/15/2020
2019.2.1 NIBRS Technical Specification
49
Type Weapon/Force Involved Element Edits
Data Element
Edit Description
Associated Error
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:
Data Element 13
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/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
221
(Type of Weapon/Force Involved) Type of Weapon/Force
Involved can only be entered when the UCR Offense Code is:
Data Element 13
Data Element 13
06/15/2020
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/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
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.
2019.2.1 NIBRS Technical Specification
222
265
50
Type Weapon/Force Involved Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 13
(Type Weapon/Force Involved) If a homicide offense is
submitted, Data Element 13 (Type Weapon/Force Involved)
cannot have 99 = None. Some type of weapon/force must be
used in a homicide offense.
267
Data Element 13
(Type Weapon/Force Involved) If Data Element 6 (UCR
Offense Code) is 13B = Simple Assault and the weapon
involved is 11 = Firearm, 12 = Handgun, 13 = Rifle,
14 = Shotgun, or 15 = Other Firearm, then the offense should
instead be classified as 13A = Aggravated Assault.
269
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:
Format:
Position:
A
1-Character Alphabetic
55
Indicator 1
58
Indicator 2
61
Indicator 3
Occurrence: 3 times per Offense Segment
Mandatory: Conditional
06/15/2020
2019.2.1 NIBRS Technical Specification
51
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
Data Element
Edit Description
Associated
Error Code
Data Element 13
(Automatic Weapon Indicator) The referenced data element must
contain a valid data value when it is entered; blank is permissible
on nonmandatory fields.
204
Data Element 13
(Automatic Weapon Indicator) Must be A = Automatic or
blank = Not Automatic.
255
(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:
Data Element 13
11 = Firearm (Type Not Stated)
12 = Handgun
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.
258
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:
Format:
Position:
Occurrence:
Mandatory:
06/15/2020
A
1-Character Numeric
38
Once per Property Segment
Conditional
2019.2.1 NIBRS Technical Specification
52
This data element is mandatory when Data Element 6 (UCR Offense Code) contains
Kidnapping/Abduction, Crimes against Property, Drug/Narcotic Offenses, or Gambling
Offenses.
Edits:
Table 3-26 Type Property Loss/Etc. Edit Description
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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:
Data Element 14
Data Element 14
Data Element 14
Data Element 14
Data Element 14
06/15/2020
1) When Data Element 6 (UCR Offense Code) contains an
offense that allows property to be 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
(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
Act of 1934*, 522 = Weapons of Mass Destruction*, 526 =
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
072
077
(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.
078
(Type Property Loss/Etc.) Must 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.
(Type Property Loss/Etc.) Must be 1 = None or 6 = Seized when
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
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
078
2019.2.1 NIBRS Technical Specification
078
53
Type Property Loss Element Edits
Data Element
Data Element 14
Data Element 14
Data Element 14
Edit Description
Associated
Error Code
(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.
(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, 58B = Export
Violations*, and Data Element 7 (Offense Attempted/Completed)
is C = Completed.
*Denotes offenses for federal and tribal LEA reporting only
078
(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.
078
078
(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:
Data Element 14
Data Element 14
06/15/2020
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
2019.2.1 NIBRS Technical Specification
078
078
54
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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:
Data Element 14
06/15/2020
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
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/Completed
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
2019.2.1 NIBRS Technical Specification
081
55
Type Property Loss Element Edits
Data Element
Data Element 14
Data Element 14
Data Element 14
06/15/2020
Edit Description
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
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.
2019.2.1 NIBRS Technical Specification
Associated
Error Code
081
081
081
56
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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:
Data Element 14
06/15/2020
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
2019.2.1 NIBRS Technical Specification
081
57
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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:
Data Element 14
06/15/2020
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 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
2019.2.1 NIBRS Technical Specification
081
58
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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.:
Data Element 14
06/15/2020
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
2019.2.1 NIBRS Technical Specification
081
59
Type Property Loss Element Edits
Data Element
Edit Description
Associated
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:
Data Element 14
06/15/2020
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
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
2019.2.1 NIBRS Technical Specification
081
60
Type Property Loss Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 14
The referenced data element in an incident must contain data
when the referenced data element is mandatory or when the
conditions are met for data that must be entered into a
conditionally mandatory field.
301
Data Element 14
(Type Property Loss/Etc.) The referenced data element must
contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
304
(Type Property Loss/Etc.) Referenced data elements must be
blank when one of the following criteria is met:
Data Element 14
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
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.
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., Data Elements 15 through 22
must have applicable entries in the segment.
372
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
06/15/2020
2019.2.1 NIBRS Technical Specification
61
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:
Format:
Position:
A
2-Character Numeric
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
Data Element
Edit Description
Associated 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. There are exceptions to this rule:
Data Element 15
1) When Data Element 6 (UCR Offense Code) contains an
offense that allows property to be recovered without first
being stolen in that same incident (i.e., 250 =
Counterfeiting/Forgery and 280 = Stolen Property Offenses,
58B = Export Violations*).
072
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
Data Element 15
06/15/2020
(Property Description) The referenced data element must
contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
2019.2.1 NIBRS Technical Specification
304
62
Property Description Element Edits
Data Element
Edit Description
Associated Error
Code
Data Element 15
(Property Description) 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. Refer to
individual data elements for exceptions.
306
Data Element 15
Data Element 15 (Property Description) is 88 = Pending
Inventory, but Data Element 16 (Value of Property) is not $1.
353
(Property Description) Must be one of the following:
Data Element 15
Data Element 15
Data Element 15
Data Element 15
06/15/2020
03 = Automobiles
05 = Buses
24 = Other Motor Vehicles
28 = Recreational Vehicles
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
3 = Counterfeited/Forged
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
Property Segment exist.
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 328: 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.) are illogical with 23A = Pocketpicking or 23B = Purse-snatching
2019.2.1 NIBRS Technical Specification
359
375
387
390
63
Property Description Element Edits
Data Element
Edit Description
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
Associated Error
Code
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
06/15/2020
2019.2.1 NIBRS Technical Specification
64
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
220 BURGLARY
240 MOTOR VEHICLE THEFT
06/15/2020
Allowed
NO
2019.2.1 NIBRS Technical Specification
Property Descriptions
29-Structures-Single Occupancy
Dwellings
65
Offense
Allowed
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
23A LARCENY/POCKET-PICKING
23B LARCENY/PURSE-SNATCHING
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
23C LARCENY/SHOPLIFTING
NO
NO
NO
NO
NO
NO
NO
NO
06/15/2020
2019.2.1 NIBRS Technical Specification
Property Descriptions
30-Structures-Other Dwellings
31-Structures-Commercial/Business
32-Structures-Industrial/Manufacturing
33-Structures-Public/Community
34-Structures- Storage
35-Structures-Other
01-Aircraft
03-Automobiles
04-Bicycles
05-Buses
12-Farm Equipment
15-Heavy Construction/Industrial
Equipment
18-Livestock
24-Other Motor Vehicles
28-Recreational Vehicles
29-Structures-Single Occupancy
Dwellings
30-Structures-Other Dwellings
31-Structures-Commercial/Business
32-Structures-Industrial/Manufacturing
33-Structures-Public/Community
34-Structures-Storage
35-Structures-Other
37-Trucks
39-Watercraft
66 - Identity–Intangible
78-Trailers
01-Aircraft
03-Automobiles
05-Buses
12-Farm Equipment
15-Heavy Construction/Industrial
Equipment
18-Livestock
24-Other Motor Vehicles
28-Recreational Vehicles
29-Structures-Single Occupancy
Dwellings
30-Structures-Other Dwellings
31-Structures-Commercial/Business
32-Structures-Industrial/Manufacturing
33-Structures-Public/Community
66
Offense
23D LARCENY/THEFT FROM BUILDING
23E LARCENY/THEFT FROM COIN-OPERATED
MACHINE OR DEVICE
23F LARCENY/THEFT FROM MOTOR VEHICLE
23G LARCENY/THEFT OF MOTOR VEHICLE
PARTS/ACCESSORIES
23H LARCENY/ALL OTHER LARCENY
Allowed
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
Property Descriptions
34-Structures-Storage
35-Structures-Other
37-Trucks
39-Watercraft
03-Automobiles
05-Buses
24-Other Motor Vehicles
28-Recreational Vehicles
29-Structures-Single Occupancy
Dwellings
30-Structures-Other Dwellings
31-Structures-Commercial/Business
32-Structures-Industrial/Manufacturing
33-Structures-Public/Community
34-Structures-Storage
35-Structures-Other
37-Trucks
NO
03-Automobiles
NO
NO
NO
NO
05-Buses
24-Other Motor Vehicles
28-Recreational Vehicles
37-Trucks
NO
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:
Format:
Position:
06/15/2020
A
9-Character Numeric
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
2019.2.1 NIBRS Technical Specification
67
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
Data Element
Edit Description
Associated
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.
Data Element 16
Note: An exception occurs when Data Element 6 (UCR Offense
Code) contains an offense that allows property to be recovered
without first being stolen in that same incident (i.e.,
250 = Counterfeiting/Forgery and 280 = Stolen Property
Offenses)
084
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.
Data Element 16
(Value of Property) Must be numeric entry with zero left-fill. Refer
to individual data element for specific formatting instructions.
302
(Value of Property) cannot be zero unless Data Element 15
(Property Description) is:
Data Element 16
Mandatory zero
09 = Credit/Debit Cards
22 = Nonnegotiable Instruments
48 = Documents–Personal or Business
65 = Identity Documents
66 = Identity–Intangible
351
Optional zero
77 = Other
Data Element 16
Data Element 15 (Property Description) is 88 = Pending
Inventory, but Data Element 16 (Value of Property) is not $1.
353
Data Element 16
(Property Description) Data Element 16 (Value of Property)
contains a value, but Data Element 15 (Property Description) was
not entered.
354
Data Element 16
(Value of Property) Must be blank when Data Element 15
(Property Description) code is 10 = Drugs/Narcotics and the only
offense submitted is a 35A = Drug/Narcotic Violations.
383
06/15/2020
2019.2.1 NIBRS Technical Specification
68
Value of Property Element Edits
Data Element
Edit Description
Data Element 16
(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
when Data Element 15 (Property Description) is:
Associated
Error Code
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:
Format:
Position:
06/15/2020
A
8-Character Numeric (YYYYMMDD)
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
2019.2.1 NIBRS Technical Specification
69
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
Edit Description
Associated
Error Code
Data Element 17
(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
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).
305
Data Element 17
(Type Property Loss/Etc.) Must be 5 = Recovered for Data
Element 17 (Date Recovered) to be entered.
355
Data Element 17
Data Element 17 (Date Recovered) was entered, but Data
Elements 15 (Property Description) and/or 16 (Value of Property)
were not entered.
356
Data Element
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:
Format:
Position:
06/15/2020
A
2-Character Numeric
229–230
2019.2.1 NIBRS Technical Specification
70
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
Data Element
Edit Description
Associated
Error Code
Data Element 18
(Number of Stolen Motor Vehicles) Must be numeric entry with zero
left-fill. Refer to individual data element for specific formatting
instructions.
302
Data Element 18
(Number of Stolen Motor Vehicles) was entered. However, Data
Element 14 (Type Property Loss/Etc.) 7 = Stolen/Etc. 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.
357
Data Element 18
(Number of Stolen Motor Vehicles) Entry must be made for Data
Element 18 (Number of Stolen Motor Vehicles) when Data Element
6 (UCR Offense Code) is 240 = Motor Vehicle Theft, Data Element
7 (Offense Attempted/Completed) is C = Completed, and Data
Element 14 (Type Property Loss/Etc.) is 7 = Stolen/Etc.
358
Data Element 18
(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
03 = Automobiles and 05 = Buses were entered as being stolen,
then the number stolen must be at least 2, unless the number
stolen was 00 = Unknown.
388
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:
Format:
Position:
Occurrence:
Mandatory:
06/15/2020
A
2-Character Numeric
231–232
Once per Property Segment
Conditional
2019.2.1 NIBRS Technical Specification
71
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
Data Element
Edit Description
Associated
Error Code
Data Element 19
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 Element 19 (Number of Recovered Motor
Vehicles) within the same incident.
073
Data Element 19
(Number of Recovered Motor Vehicles) Must be numeric entry with
zero left-fill. Refer to individual data element for specific formatting
instructions.
302
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. The exception
to this rule is when recovered 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.
360
Data Element 19
(Number of Recovered Motor Vehicles) must be entered when Data
Element 6 (UCR Offense Code) is 240 = Motor Vehicle Theft, Data
Element 7 (Offense Attempted/Completed) is C = Completed, Data
Element 14 (Type Property Loss/Etc.) is 5 = Recovered, and
vehicle codes were recovered.
361
Data Element 19
(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
codes of 03 = Automobiles and 05 = Buses were entered as being
recovered, then the number recovered must be at least 2, unless
the number recovered was 00 = Unknown.
389
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
72
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:
Format:
Position:
A
1-Character Alphabetic
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
Data Element
Edit Description
Associated
Error Code
Data Element 20
The referenced data element in an incident must contain data when
the referenced data element is mandatory or when the conditions
are met for data that must be entered into a conditionally mandatory
field.
301
Data Element 20
(Suspected Drug Type) The referenced data element must contain
a valid data value when it is entered; blank is permissible on
nonmandatory fields.
304
06/15/2020
2019.2.1 NIBRS Technical Specification
73
Suspected Drug Type Element Edits
Data Element
Edit Description
(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.
Associated
Error Code
There are two exceptions to this rule:
Data Element 20
1) When a data value is entered in both Drug Type 1 and Drug
Type 2, but different measurement categories are entered in
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.
306
Data Element 20
(Suspected Drug Type) Since X = Over 3 Drug Types was entered
in Data Element 20 (Suspected Drug Type), two other codes must
also be entered. Less than three codes are present.
362
Data Element 20
(Estimated Drug Quantity) Since Data Element 20 (Suspected Drug
Type) contains X = Over 3 Drug Types, Data Element 21
(Estimated Quantity) and 22 (Type Measurement) must be blank.
363
Data Element 20
(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
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.
364
Data Element 20
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
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.
365
Data Element 20
(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
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
B
C
D
E
= Crack Cocaine
= Cocaine (all forms except Crack)
= Hashish
= Heroin
= Marijuana
06/15/2020
2019.2.1 NIBRS Technical Specification
74
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:
Format:
Position:
A
12-Character Numeric
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:
06/15/2020
2019.2.1 NIBRS Technical Specification
75
Table 3-34 Estimated Drug Quantity Edit Description
Estimated Drug Quantity Type Element Edits
Edit Description
Associated
Error Code
Data Element 21
(Estimated Drug Quantity) Must be numeric entry with zero left-fill.
Refer to individual data element for specific formatting
instructions.
302
Data Element 21
(Estimated Drug Quantity) Since Data Element 20 (Suspected
Drug Type) contains X = Over 3 Drug Types, Data Element 21
(Estimated Quantity) and 22 (Type Measurement) must be blank.
363
Data Element 21
(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
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
364
Data Element 21
Data Element 21 (Estimated Quantity) was entered, but 20
(Suspected Drug Type) and/or 22 (Type Measurement) were not
entered; both must be entered.
366
Data Element 21
(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
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.
384
Data Element
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
76
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:
Format:
Position:
A
2-Character Alphabetic
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
Data Element
Edit Description
Associated
Error Code
Data Element 22
(Type Drug Measurement) The referenced data element must
contain a valid data value when it is entered; blank is permissible on
nonmandatory fields.
304
Data Element 22
(Type Drug Measurement) Since Data Element 20 (Suspected Drug
Type) contains X = Over 3 Drug Types, Data Element 21 (Estimated
Quantity) and 22 (Type Measurement) must be blank.
363
Data Element 22
(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
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.
364
Data Element 22
(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:
DRUG MEASUREMENT
E = Marijuana NP
G = Opium NP
K = Other Hallucinogens NP
367
All other Data Element 22 (Type Measurement) codes are
applicable to any Data Element 20 (Suspected Drug Type) code.
06/15/2020
2019.2.1 NIBRS Technical Specification
77
Drug Type Measurement Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 22
Data Element 22 (Type Drug Measurement) was entered, but Data
Elements 20 (Suspected Drug Type) and/or 21 (Estimated Quantity)
were not entered; both must be entered.
368
Data Element 22
(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
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.
384
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 23Victim 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:
Format:
06/15/2020
A
3-Character Numeric
2019.2.1 NIBRS Technical Specification
78
Position:
38–40
Occurrence: Once per Victim Segment
Mandatory: Yes
Edits:
Table 3-36 Victim Sequence Number Edit Description
Victim Sequence Number Element Edits
Edit Description
Associated
Error Code
Data Element 23
(Victim Sequence Number) The referenced data element in an
Incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
401
Data Element 23
Must contain numeric entry with zero left-fill.
402
Data Element 23
(Victim Sequence Number) The referenced data element must
contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
404
Data Element 23
(Victim Segment) When a Group A Incident Report is submitted,
the individual segments comprising the incident cannot contain
duplicates. In this case, two victim segments were submitted
having the same entry in Data Element 23 (Victim Sequence
Number).
451
Data Element
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:
Format:
Position:
A
3-Character Alphanumeric
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:
06/15/2020
2019.2.1 NIBRS Technical Specification
79
Table 3-37 Victim Connected to UCR Offense Code Edit Description
Victim Connected to UCR Code(s) Element Edits
Edit Description
Associated
Error Code
Data Element 24
(Victim Connected to UCR Offense Code) The referenced data
element in an incident must contain data when the referenced
data element is mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory field.
401
Data Element 24
(Victim Connected to UCR Offense Code) The referenced data
element must contain a valid data value when it is entered; blank
is permissible on nonmandatory fields.
404
Data Element 24
(Victim Connected to UCR Offense Code) 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.
406
Data Element 24
(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
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.
466
Data Element
06/15/2020
2019.2.1 NIBRS Technical Specification
80
Victim Connected to UCR Code(s) Element Edits
Data Element
Edit Description
Associated
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.
Data Element 24
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).
478
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
81
Victim Connected to UCR Code(s) Element Edits
Data Element
Edit Description
Associated
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.
Data Element 24
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.
478
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
06/15/2020
2019.2.1 NIBRS Technical Specification
82
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
71
Once per Victim Segment
Yes
Table 3-38 Type of Victim Edit Description
Type of Victim Element Edits
Data Element
Edit Description
Associated
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.
Data Element 25
06/15/2020
Exception - Type of Victim must be G = Government for offenses:
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
2019.2.1 NIBRS Technical Specification
080
83
Type of Victim Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 25
(Type of Victim) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
when the conditions are met for data that must be entered into a
conditionally mandatory field.
401
Data Element 25
(Type of Victim) The referenced data element must contain a valid
data value when it is entered; blank is permissible on nonmandatory
fields.
404
(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:
Data Element 25
Data Element 25
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
(Type of Victim) Must have a value of I = Individual or L = Law
Enforcement Officer when Data Element 24 (Victim Connected to
UCR Offense Code) contains a Crime Against Person.
461
464
(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.
Data Element 25
Data Element 25
Exception - Type of Victim must be G = Government for offenses
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
(Type of Victim) Cannot have a value of S = Society/Public when
Data Element 24 (Victim Connected to UCR Offense Code) contains
a Crime Against Property.
465
467
(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
06/15/2020
09A = Murder & Nonnegligent Manslaughter
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
2019.2.1 NIBRS Technical Specification
482
84
Type of Victim Element Edits
Data Element
Edit Description
Associated
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:
Data Element 25
09A = Murder & Nonnegligent Manslaughter
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
490
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
2-Character Numeric
130–131
Once per Victim Segment
Optional
Table 3-39 Type of Officer Activity/Circumstance Edit Description
Type of Officer Activity/Circumstance Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 25A
(Type of Officer Activity/Circumstance) The referenced data
element must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
404
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 Victim), and Data Element 28 (Race of Victim) must be
entered when Data Element 25 (Type of Victim) is L = Law
Enforcement Officer.
454
Data Element 25A
(Type of Officer Activity/Circumstance) Data Element 25B (Officer
Assignment Type), Data Element 25C (Officer–ORI Other
483
06/15/2020
2019.2.1 NIBRS Technical Specification
85
Type of Officer Activity/Circumstance Element Edits
Data Element
Edit Description
Jurisdiction), may only be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
Associated
Error Code
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
132
Once per Victim Segment
Optional
Table 3-40 Officer Assignment Type Edit Description
Officer Assignment Type Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 25B
(Officer Assignment Type) The referenced data element must
contain a valid data value when it is entered; blank is permissible
on nonmandatory fields.
404
Data Element 25B
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 Victim), and Data Element 28
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
454
Data Element 25B
Data Element 25A (Type of Officer Activity/Circumstance), Data
Element 25B (Officer Assignment Type), Data Element 25C
(Officer–ORI Other Jurisdiction), may only be entered when Data
Element 25 (Type of Victim) is L = Law Enforcement Officer.
483
Data Values: For Uniformed Law Enforcement Officers:
F = Two-Officer Vehicle
06/15/2020
2019.2.1 NIBRS Technical Specification
86
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
9-Character Alphanumeric
133–141
Once per Victim Segment
Optional
Table 3-41 Jurisdiction Edit Description
Officer ORI Jurisdiction Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 25C
(Officer–ORI Other Jurisdiction) Must be a valid nine-character
NCIC ORI.
952
Data Element 25C
(Officer–ORI Other Jurisdiction) Data Element 25A (Type of
Officer Activity/Circumstance), Data Element 25B (Officer
Assignment Type), Data Element 25C (Officer–ORI Other
Jurisdiction), may only be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
483
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
87
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:
Format:
Position:
Occurrence:
Mandatory:
A
4-Character Alphanumeric
72–75
Once per Victim Segment
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
Data Element
Edit Description
Associated
Error Code
Data Element 26
(Age of Victim) The referenced data element must contain a valid
data value when it is entered; blank is permissible on nonmandatory
fields.
404
Data Element 26
(Age of Victim) contains data, but is not left-justified. A single twocharacter age must be in positions 1 and 2 of the field.
408
Data Element 26
(Age of Victim) contains more than two characters indicating a
possible age-range was being attempted. If so, the field must
contain numeric entry of four digits.
409
Data Element 26
(Age of Victim) was entered as an age-range. Accordingly, the first
age component must be less than the second age.
410
Data Element 26
(Age of Victim) was entered as an age-range. Therefore, the first
age component cannot be 00 = Unknown.
422
Data Element 26
(Age of Victim) cannot be less than 13 years old when Data Element
35 (Relationship of Victim to Offender) contains a relationship of
SE = Spouse.
450
Data Element 26
(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
Enforcement Officer. (Data Element 26 must be >=17 & <=98 or
Data Element 26 = 00)
452
Data Element 26
(Age of Victim) The data element associated with this error must be
present when Data Element 25 (Type of Victim) is I = Individual.
453
Data Element 26
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 Victim), and Data Element 28
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
454
Data Element 26
The Data Element associated with this error cannot be entered
when Data Element 25 (Type of Victim) is not I = Individual or
L = Law Enforcement Officer.
458
Data Element 26
Data Element 26 (Age of Victim) should be under 18 when Data
Element 24 (Victim Connected to UCR Offense Code) is
36B = Statutory Rape.
481
06/15/2020
2019.2.1 NIBRS Technical Specification
88
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:
Format:
Position:
A
1-Character Alphabetic
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
Data Element
Edit Description
Associated
Error Code
Data Element 27
(Sex of Victim) The referenced data element must contain a valid
data value when it is entered; blank is permissible on nonmandatory
fields.
404
Data Element 27
(Sex of Victim) The data element associated with this error must be
present when Data Element 25 (Type of Victim) is I = Individual.
453
Data Element 27
(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
Victim), and Data Element 28 (Race of Victim) must be entered
when Data Element 25 (Type of Victim) is L = Law Enforcement
Officer.
454
Data Element 27
(Sex of Victim) The data element associated with this error cannot
be entered when Data Element 25 (Type of Victim) is not
I = Individual or L = Law Enforcement Officer.
458
Data Element 27
(Sex of Victim) Data Element 27 (Sex of Victim) must be M = Male
or F = Female to be connected to offense codes of 11A = Rape and
36B = Statutory Rape.
469
Data Values: F = Female
M = Male
U = Unknown
06/15/2020
2019.2.1 NIBRS Technical Specification
89
Data Element 28-Race of Victim
Race of Victim is used to indicate the race of an individual victim.
Group:
Format:
Position:
Occurrence:
Mandatory:
A
1-Character Alphabetic
77
Once per Victim Segment
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
Data Element
Edit Description
Associated
Error Code
Data Element 28
(Race of Victim) The referenced data element must contain a valid
data value when it is entered; blank is permissible on nonmandatory
fields.
404
Data Element 28
(Race of Victim) The data element associated with this error must be
present when Data Element 25 (Type of Victim) is I = Individual.
453
Data Element 28
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 Victim), and Data Element 28
(Race of Victim) must be entered when Data Element 25 (Type of
Victim) is L = Law Enforcement Officer.
454
Data Element 28
(Race of Victim) The data element associated with this error cannot
be entered when Data Element 25 (Type of Victim) is not I =
Individual or L = Law Enforcement Officer.
458
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:
Format:
Position:
Occurrence:
Mandatory:
06/15/2020
A
1-Character Alphabetic
78
Once per Victim Segment
Optional
2019.2.1 NIBRS Technical Specification
90
Edits:
Table 3-45 Ethnicity of Victim Edit Description
Ethnicity of Victim Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 29
(Ethnicity of Victim) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
404
Data Element 29
(Ethnicity of Victim) The data element associated with this error
cannot be entered when Data Element 25 (Type of Victim) is not
I = Individual or L = Law Enforcement Officer
458
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
79
Once per Victim Segment
Optional
Table 3-46 Resident Status of Victim Edit Description
Resident Status of Victim Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 30
(Resident Status of Victim) The referenced data element must
contain a valid data value when it is entered; blank is permissible
on nonmandatory fields.
404
Data Element 30
(Resident Status of Victim) The Data Element associated with this
error cannot be entered when Data Element 25 (Type of Victim) is
not I = Individual or L = Law Enforcement Officer.
458
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:
Format:
Position:
06/15/2020
A
2-Character Numeric
80–81 Circumstance 1
2019.2.1 NIBRS Technical Specification
91
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
Data Element
Edit Description
Associated
Error Code
Data Element 31
(Aggravated Assault/Homicide Circumstances) The referenced data
element in an incident must contain data when the referenced data
element is mandatory or when the conditions are met for data that
must be entered into a conditionally mandatory field.
401
Data Element 31
Must contain numeric entry with zero left-fill.
402
Data Element 31
(Aggravated Assault/Homicide Circumstances) The referenced data
element must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
404
Data Element 31
(Aggravated Assault/Homicide Circumstances) 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.
406
(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
09B = Negligent Manslaughter
09C = Justifiable Homicide
13A = Aggravated Assault
419
(Aggravated Assault/Homicide Circumstances) was entered with
two entries, but was rejected for one of the following reasons:
Data Element 31
1) 10 = Unknown Circumstances is mutually exclusive with any
other value.
2) Multiple values from more than one category were entered.
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.
456
Data Element 31
(Aggravated Assault/Homicide Circumstances) may only have
codes of 01 through 06 and 08 through 10 when Data Element 24
(Victim Connected To UCR Offense) is 13A = Aggravated Assault.
All other codes, including 07 = Mercy Killing, are not valid because
they do not relate to an Aggravated Assault.
462
Data Element 31
(Aggravated Assault/Homicide Circumstances) When a Justifiable
Homicide is reported, Data Element 31 (Aggravated Assault/
Homicide Circumstances) may only have codes of 20 = Criminal
Killed by Private Citizen or 21 = Criminal Killed by Police Officer. In
this case, a code other than the two mentioned was entered.
463
06/15/2020
2019.2.1 NIBRS Technical Specification
92
Aggravated Assault/Homicide Circumstances Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 31
(Aggravated Assault/Homicide Circumstances) A victim segment
was submitted with Data Element 24 (Victim Connected to UCR
Offense Code) having an offense that does not have a permitted
code for Data Element 31 (Aggravated Assault/Homicide
Circumstances).
477
Data Element 31
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 Data Element 6 (UCR Offense Code)
should have been submitted, or multiple individual victims should
have been submitted for the incident report.
480
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:
Format:
Position:
06/15/2020
A
1-Character Alphabetic
84
2019.2.1 NIBRS Technical Specification
93
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
Data Element
Edit Description
Associated
Error Code
Data Element 32
(Additional Justifiable Homicide Circumstances) The referenced
data element must contain a valid data value when it is entered;
blank is permissible on nonmandatory fields.
404
Data Element 32
Data Element 31 (Aggravated Assault/Homicide Circumstances)
contains: 20 = Criminal Killed by Private Citizen or 21 = Criminal
Killed by Police Officer, but Data Element 32 (Additional Justifiable
Homicide Circumstances) was not entered.
455
Data Element 32
(Additional Justifiable Homicide Circumstances) was entered, but
Data Element 31 (Aggravated Assault/Homicide Circumstances)
does not reflect a justifiable homicide circumstance.
457
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:
Format:
Position:
A
1-Character Alphabetic
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
06/15/2020
2019.2.1 NIBRS Technical Specification
94
•
•
•
•
•
•
•
•
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
Data Element
Edit Description
Associated
Error Code
Data Element 33
(Type Injury) The referenced data element in an Incident must
contain data when the referenced data element is mandatory or
when the conditions are met for data that must be entered into a
conditionally mandatory field.
401
Data Element 33
(Type Injury) The referenced data element must contain a valid
data value when it is entered; blank is permissible on
nonmandatory fields.
404
Data Element 33
(Type Injury) 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.
406
Data Element 33
(Type Injury) Can have multiple data values and was entered with
multiple values. However, the entry shown between the brackets in
[value] above cannot be entered with any other data value.
407
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:
Data Element 33
Data Element 33
06/15/2020
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
(Type Injury) The data element associated with this error cannot be
entered when Data Element 25 (Type of Victim) is not
I = Individual or L = Law Enforcement Officer.
2019.2.1 NIBRS Technical Specification
419
458
95
Type of Injury Element Edits
Data Element
Data Element 33
Edit Description
Associated
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).
Either the offense should have been classified as an
13A =
Aggravated Assault or the victim’s injury should not have been
entered as major.
479
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:
Format:
Position:
A
2-Character Numeric
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
This data element will remain optional for all other Crimes Against Property until further notice.
Edits:
06/15/2020
2019.2.1 NIBRS Technical Specification
96
Table 3-50 Offender Number to be Related Edit Description
Offender Number(s) to be Related Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 34
Data Element 34 (Offender Number to be Related) has a value that
does not have a corresponding Offender Segment. For example, if
the field value 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).
070
Data Element 34
(Offender Number to be Related) The referenced data element in an
Incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
401
Data Element 34
Must contain numeric entry with zero left-fill.
402
Data Element 34
(Offender Number to be Related) 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.
406
Data Element 34
(Offender Number to be Related) The data element associated with
this error cannot be entered when Data Element 25 (Type of Victim)
is not I = Individual or L = Law Enforcement Officer.
458
Data Element 34
(Offender Number to be Related) has relationships of VO = Victim
Was Offender that point to multiple offenders, which is an
impossible situation. A single victim cannot be two offenders.
471
Data Element 34
Data Element 34
(Offender Number to be Related) A victim may only have one
spousal relationship. In this instance, the victim has a relationship of
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 =
Failure to Register as a Sex Offender*.
*Denotes offenses for federal and tribal LEA reporting only
475
485
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:
Format:
Position:
06/15/2020
A
2-Character Alphabetic
92–93
Relationship 1
96–97
Relationship 2
2019.2.1 NIBRS Technical Specification
97
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 will remain optional for all other Crimes Against Property until further notice.
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.
Data Value XR = Victim was Ex-Relationship (ex-boyfriend/ex-girlfriend)
Edits:
Table 3-51 Relationship of Victim to Offender Edit Description
Relationship(s) of Victim to Offender(s) Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 35
(Relationship of Victim to Offender) The referenced data element
must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
404
Data Element 35
(Relationship of Victim to Offender) Corresponding Data Element 35
(Relationship of Victim to Offender) data must be entered when
Data Element 34 (Offender Number to be Related) is entered with a
value greater than 00.
460
Data Element 35
(Relationship of Victim to Offender) cannot be entered when Data
Element 34 (Offender Number to be Related) is zero. Zero means
that the number of offenders is unknown; therefore, the relationship
cannot be entered.
468
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
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. However, there may be some situations where
only one of the victims is also the offender, but where the other
victim(s) is not also the offender(s).
470
Data Element 35
(Relationship of Victim to Offender) has relationships of VO = Victim
Was Offender that point to multiple offenders, which is an
impossible situation. A single victim cannot be two offenders.
471
06/15/2020
2019.2.1 NIBRS Technical Specification
98
Relationship(s) of Victim to Offender(s) Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 35
(Relationship of Victim to Offender) If Data Element 37 (Age of
Offender) is 00 = Unknown, Data Element 38 (Sex of Offender) is
U = Unknown, and Data Element 39 (Race of Offender) is
U = Unknown, then Data Element 35 (Relationship of Victim to
Offender) must be RU = Relationship Unknown.
472
Data Element 35
(Relationship of Victim to Offender) Segment Level 4 (Victim
Segment) cannot be submitted multiple times with VO = Victim Was
Offender in Data Element 35 (Relationship of Victim to Offender)
when Data Element 34 (Offender Number to be Related) contains
the same data value (indicating the same offender).
474
Data Element 35
(Relationship of Victim to Offender) A victim can only have one
spousal relationship. In this instance, the victim has a relationship of
SE = Spouse to two or more offenders.
475
Data Element 35
(Relationship of Victim to Offender) An offender can only have one
spousal relationship. In this instance, two or more victims have a
relationship of SE = Spouse to the same offender.
476
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
06/15/2020
2019.2.1 NIBRS Technical Specification
99
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.
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
2-Character Numeric
38–39
Once per Offender Segment
Yes
Table 3-52 Offender Sequence Number Edit Description
Offender Sequence Number Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 36
(Offender Sequence Number) The referenced data element in an
incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
501
Data Element 36
Data Element 36 (Offender Sequence Number) must contain
numeric entry (00 through 99) with zero left-fill.
502
Data Element 36
(Offender Sequence Number) When multiple Offender Segments
are submitted, none can contain a 00 = Unknown value because the
presence of 00 indicates that the number of offenders is unknown.
In this case, multiple offenders were submitted, but one of the
segments contains the 00 = Unknown value.
555
Data Element 36
Data Element 36
06/15/2020
(Offender Sequence Number) contains 00 indicating that nothing is
known about the offender(s) regarding number and any identifying
information. To exceptionally clear the incident, the value cannot be
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
2019.2.1 NIBRS Technical Specification
557
559
100
Offender Sequence Number Element Edits
Data Element
Edit Description
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 for age, sex, and race.
*Denotes offenses for federal and tribal LEA reporting only
Associated
Error Code
Data Values: 00 = Unknown Offender
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
4-Character Numeric
40–43
Once per Offender Segment
Conditional
Table 3-53 Age of Offender Edit Description
Age of Offender Element Edits
Edit Description
Associated
Error Code
Data Element 37
(Age of Offender) The referenced data element in an Incident must
contain data when the referenced data element is mandatory or
when the conditions are met for data that must be entered into a
conditionally mandatory field.
501
Data Element 37
(Age of Offender) contains data but is not left-justified. A single
two-character age must be in positions 1 through 2 of the field.
508
Data Element 37
(Age of Offender) contains more than two characters indicating a
possible age-range is being attempted. If so, the field must contain
a numeric entry of four digits.
509
Data Element 37
(Age of Offender) was entered as an age-range. Accordingly, the
first age component must be less than the second age.
510
Data Element 37
(Age of Offender) was entered as an age-range. Therefore, the first
age component cannot be 00 = Unknown.
522
Data Element 37
(Age of Offender) cannot be less than 13 years old when Data
Element 35 (Relationship of Victim to Offender) contains a
relationship of SE = Spouse.
550
Data Element
06/15/2020
2019.2.1 NIBRS Technical Specification
101
Age of Offender Element Edits
Data Element
Data Element 37
Data Element 37
Edit Description
(Age of Offender) Data Element 38 (Sex of Offender), and Data
Element 39 (Race of Offender) cannot be entered when Data
Element 36 (Offender Sequence Number) is 00 = Unknown.
(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
be consistent with the victim’s age in relation to the offender’s age:
Associated
Error Code
552
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
Data Element 37
(Offender Segment) None of the Offender Segments contain all
known values for age, sex, and race. When an incident is cleared
exceptionally (Data Element 4 contains an A through E), one
offender must have all known values.
558
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
44
Once per Offender Segment
Conditional
Table 3-54 Sex of Offender Edit Description
Sex of Offender Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 38
(Sex of Offender) The referenced data element in an incident must
contain data when the referenced data element is mandatory or when
the conditions are met for data that must be entered into a
conditionally mandatory field.
501
06/15/2020
2019.2.1 NIBRS Technical Specification
102
Sex of Offender Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 38
(Sex of Offender) The referenced data element must contain a valid
data value when it is entered; blank is permissible on nonmandatory
fields.
504
Data Element 38
(Sex of Offender) Data Element 38 and Data Element 39 (Race of
Offender) cannot be entered when Data Element 36 (Offender
Sequence Number) is 00 = Unknown.
552
Data Element 38
(Offender Segment) None of the Offender Segments contain all known
values for age, sex, and race. When an incident is cleared
exceptionally (Data Element 4 contains an A through E) one offender
must have all known values.
558
Data Element 38
Segment Level 5 (Offender Segment) must contain a data value for at
least one offender in Data Element 38 (Sex of Offender) that is not the
same sex that is entered in Data Element 27 (Sex of Victim) when
Data Element 6 (UCR Offense Code) is 11A = Rape. The offender
must be connected to the victim in Data Element 34 (Offender Number
to be Related) unless offender number in Data Element 34 (Offender
Number to be Related) is 00 = Unknown
560
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
45
Once per Offender Segment
Conditional
Table 3-55 Race of Offender Edit Description
Race of Offender Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 39
(Race of Offender) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
when the conditions are met for data that must be entered into a
conditionally mandatory field.
501
Data Element 39
(Race of Offender) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
504
Data Element 39
Data Element 38 (Sex of Offender), and Data Element 39 (Race of
Offender) cannot be entered when Data Element 36 (Offender
Sequence Number) is 00 = Unknown.
552
06/15/2020
2019.2.1 NIBRS Technical Specification
103
Race of Offender Element Edits
Data Element
Edit Description
(Offender Segment) None of the Offender Segments contain all
known values for age, sex, and race. When an Incident is cleared
exceptionally (Data Element 4 contains an A through E) one
offender must have all known values.
Data Element 39
Data Values:
Associated
Error Code
558
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 39A-Ethnicity of Offender
Ethnicity of Offender is used to identify the ethnicity of the offender.
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A
1-Character Alphabetic
46
Once per Offender Segment
Optional
Table 3-56 Ethnicity of Offender Edit Description
Ethnicity of Offender Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 39A
(Ethnicity of Offender) The referenced data element must contain
a valid data value when it is entered; blank is permissible on
nonmandatory fields.
504
Data Element 39A
(Ethnicity of Offender) Data Element 38 (Sex of Offender) and
Data Element 39 (Race of Offender) cannot be entered when
Data Element 36 (Offender Sequence Number) is 00 = Unknown.
552
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).
06/15/2020
2019.2.1 NIBRS Technical Specification
104
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
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
A, B
2-Character Numeric
38–39 (both Arrestee Segment/Group B Arrest Report Segment)
Once per Arrestee Segment/Group B Arrest Report Segment
Yes
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
Data Element
Data Element 40
06/15/2020
Edit Description
(Arrestee Sequence Number) The referenced data element in an
incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
2019.2.1 NIBRS Technical Specification
Associated
Error Code
601, 701
105
Arrestee Sequence Number Element Edits
Data Element
Data Element 40
Edit Description
Data Element 40 (Arrestee Sequence Number) must be numeric
entry of 01 to 99 with zero left-fill.
Associated
Error Code
602,702
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:
Format:
Position:
A, B
12-Character Alphanumeric
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
Data Element
Data Element 41
Data Element 41
Data Element 41
Data Element 41
Edit Description
(Arrest Transaction Number) The referenced data element in an
incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
(Arrest Transaction Number) Must be blank right-fill if under 12
characters in length. Cannot have embedded blanks between the
first and last characters entered.
(Arrest Transaction Number) Must be left-justified with blank rightfill if under 12 characters in length.
(Arrest Transaction Number) Must contain a valid character
combination of the following:
• A–Z (capital letters only)
• 0–9
• Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not valid.
Associated
Error Code
601, 701
615, 715
616, 716
617, 717
Data Values: 12-character alphanumeric value consisting of:
A–Z
0–9
Hyphen
06/15/2020
2019.2.1 NIBRS Technical Specification
106
Data Element 42-Arrest Date
Arrest Date is used to enter the year, month, and day of the arrest.
Group:
Format:
Position:
A, B
8-Character Numeric (YYYY/MM/DD)
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.
Table 3-59 Arrest Date Edit Description
Arrestee Date Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 42
(Arrest Date) The referenced data element in an incident must
contain data when the referenced data element is mandatory or when
the conditions are met for data that must be entered into a
conditionally mandatory field.
601, 701
Data Element 42
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.
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
longer be submitting data to the FBI as of an inactive date. The FBI
will not accept arrest data this ORI after this date.
605, 705
618, 718
(Arrest Date) cannot be earlier than Data Element 3 (Incident
Date/Hour). A person cannot be arrested before the incident
occurred.
Data Element 42
The exception to this rule is when an additional arrest is reported for
a pre-NIBRS incident. In this case, Segment Level 6 (Arrestee
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.
665
Data Element 42
Group B Arrest Report (Level 7) submitted with a Segment Action
Type of A = Add cannot have Data Element 42 (Arrest Date) earlier
than the Base Date.
720
Data Element 42
(Arrest Date) is missing for a Group B Arrest Report with a Segment
Action Type of D = Delete; must be populated with a valid data value
and cannot be blank.
797
06/15/2020
2019.2.1 NIBRS Technical Specification
107
Arrestee Date Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 42
(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
file that matches Data Element 41 (Arrest Transaction Number) with
an Arrest Date outside the two year window.
798
Data Element 42
(Arrest Date) is missing for a Group B Arrest Report with a Segment
Action Type of D = Delete; multiple Group B Arrest Reports are on file
that match Data Element 41 (Arrest Transaction Number).
799
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
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:
Format:
Position:
A, B
1-Character Alphabetic
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
Data Element
Data Element 43
06/15/2020
Edit Description
(Type of Arrest) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
2019.2.1 NIBRS Technical Specification
Associated
Error Code
601, 701
108
Type of Arrest Element Edits
Data Element
Edit Description
when the conditions are met for data that must be entered into a
conditionally mandatory field.
Data Element 43
(Type of Arrest) The referenced data element must contain a valid
data value when it is entered; blank is permissible on
nonmandatory fields.
Associated
Error Code
604, 704
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.
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:
Format:
Position:
Occurrence:
Mandatory:
Edits:
Note:
A
1-Character Alphabetic
61 Arrestee Segment
Once per Arrestee Segment
Yes
Table 3-61 Multiple Arrestee Segments Indicator Edit Description
Multiple Arrestee Segments Indicator Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 44
(Multiple Arrestee Segments Indicator) The referenced data element
in an Incident must contain data when the referenced data element
is mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
601
Data Element 44
(Multiple Arrestee Segments Indicator) The referenced data element
must contain a valid data value when it is entered; blank is
permissible on nonmandatory fields.
604
Data Values: C = Count Arrestee
M = Multiple
N = Not Applicable
06/15/2020
2019.2.1 NIBRS Technical Specification
109
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:
Format:
Position:
A, B
3-Character Alphanumeric
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.
Table 3-62 UCR Arrest Offense Code Edit Description
UCR Arrest Offense Code Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 45
(UCR Arrest Offense Code) The referenced data element in an
Incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
601, 701
Data Element 45
(UCR Arrest Offense Code) The referenced data element must
contain a valid data value when it is entered; blank is permissible
on nonmandatory fields.
604, 704
06/15/2020
2019.2.1 NIBRS Technical Specification
110
UCR Arrest Offense Code Element Edits
Data Element
Edit Description
Data Element 45
(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
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
Associated
Error Code
650, 750
Data Element 45
(UCR Arrest Offense Code) was entered with 09C = Justifiable
Homicide. This is not a valid arrest offense.
670
Data Element 45
(UCR Arrest Offense Code) must contain a Group B Offense Code
in Data Element 45 (UCR Arrest Offense). The offense code
submitted is not a Group B offense code.
760
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:
Format:
Position:
A, B
2-Character Numeric
65–66
Weapon 1
Arrestee Segment
68–69
Weapon 2
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
111
Table 3-63 Arrestee Was Armed With Edit Description
Arrestee Was Armed With Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 46
(Arrestee Was Armed With) The referenced data element in an
Incident must contain data when the referenced data element is
mandatory or when the conditions are met for data that must be
entered into a conditionally mandatory field.
601, 701
Data Element 46
(Arrestee Was Armed With) The referenced data element must
contain a valid data value when it is entered; blank is permissible on
nonmandatory fields.
604, 704
Data Element 46
(Arrestee Was Armed With) 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.
606, 706
Data Element 46
(Arrestee Was Armed With) can have multiple data values and was
entered with multiple values. However, 01 = Unarmed cannot be
entered with any other data value.
607, 707
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:
Format:
Position:
A, B
1-Character Alphabetic
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
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
112
Table 3-64 Automatic Weapon Indicator Edit Description
Automatic Weapon Indicator Element Edits
Data Element
Edit Description
Associated
Error Code
Data Element 46
(Automatic Weapon Indicator) The referenced data element must
contain a valid data value when it is entered; blank is permissible on
nonmandatory fields.
604, 704
Data Element 46
Data Element 46
(Automatic Weapon Indicator) does not have A = Automatic or a
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
13 = Rifle
14 = Shotgun
15 = Other Firearm
654, 754
655, 755
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:
Format:
Position:
A, B
2-Character Numeric
71–74 Arrestee Segment
58–61 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.
06/15/2020
2019.2.1 NIBRS Technical Specification
113
Table 3-65 Age of Arrestee Edit Description
Age of Arrestee Element Edits
Edit Description
Associated
Error Code
Data Element 47
(Age of Arrestee) The referenced data element in an Incident
must contain data when the referenced data element is mandatory
or when the conditions are met for data that must be entered into
a conditionally mandatory field.
601, 701
Data Element 47
(Age of Arrestee) contains data, but is not left-justified. A single
two-character age must be in positions 1 through 2 of the field.
608, 708
Data Element 47
(Age of Arrestee) contains more than two characters indicating a
possible age-range is being attempted. If so, the field must
contain a numeric entry of four digits.
609, 709
Data Element 47
(Age of Arrestee) was entered as an age-range. Accordingly, the
first age component must be less than the second age.
610, 710
Data Element 47
(Age of Arrestee) was entered as an age-range. Therefore, the
first age component cannot be 00 = Unknown.
622, 722
Data Element 47
(Disposition of Arrestee Under 18) was not entered, but Data
Element 47 (Age of Arrestee) is under 18. Whenever an arrestee’s
age indicates a juvenile, the agency must enter the disposition.
652, 752
Data Element
Data Element 47
Data Element 47 (Age of Arrestee) does not contain a numeric
entry of 00 through 99 for an exact age.
664
Data Element 47
Data Element 47 (Age of Arrestee) does not contain a numeric
entry of 00 through 99 for an exact age.
757
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:
Format:
Position:
A, B
1-Character Alphabetic
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
114
Table 3-66 Sex of Arrestee Edit Description
Sex of Arrestee Element Edits
Data Element
Data Element 48
Data Element 48
Edit Description
(Sex of Arrestee) The referenced data element in an incident must
contain data when the referenced data element is mandatory or
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
F = Female.
Associated
Error Code
601, 701
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:
Format:
Position:
A, B
1-Character Alphabetic
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
Data Element
Edit Description
Associated
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
when the conditions are met for data that must be entered into a
conditionally mandatory field.
601, 701
(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
fields.
604, 704
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
115
Group:
Format:
Position:
A, B
1-Character Alphabetic
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
Data Element
Data Element 50
Edit Description
(Ethnicity of Arrestee) The referenced data element must contain a
valid data value when it is entered; blank is permissible on
nonmandatory fields.
Associated
Error Code
604, 704
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:
Format:
Position:
A, B
1-Character Alphabetic
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
Data Element
Data Element 51
Edit Description
(Resident Status of Arrestee) The referenced data element must
contain a valid data value when it is entered; blank is permissible on
nonmandatory fields.
Associated
Error Code
604, 704
Data Values: R = Resident
N = Nonresident
U = Unknown
06/15/2020
2019.2.1 NIBRS Technical Specification
116
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:
Format:
Position:
A, B
1-Character Alphabetic
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
Data Element
Edit Description
Associated
Error Code
Data Element 52
(Disposition of Arrestee Under 18) The referenced data element must
contain a valid data value when it is entered; blank is permissible on
nonmandatory fields.
604, 704
Data Element 52
(Disposition of Arrestee Under 18) was not entered, but Data Element
47 (Age of Arrestee) is under 18. Whenever an arrestee’s age
indicates a juvenile, the agency must enter the disposition.
652, 752
Data Element 52
(Disposition of Arrestee Under 18) was entered, but Data Element 47
(Age of Arrestee) is 18 or greater. Whenever an arrestee’s age
indicates an adult, the agency cannot enter the juvenile disposition
because it does not apply.
653, 753
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
117
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:
Format:
Positions:
Occurrence:
Mandatory:
Edits:
N/A
2-Character Numeric (MM)
38–39
Once per Zero Report Segment
Yes
Table 3-71 Zero Report Month Edit Description
Zero Report Month Element Edits
Data Element
Edit Description
Associated
Error Code
Zero Report Element (Month)
Mandatory Data Elements (Mandatory = Yes) must be
populated with a valid data value and cannot be blank.
001
Zero Report Element (Month)
Zero Report Month must be a valid month, data values 01
through 12.
090
Zero Report Element (Month)
Zero Report Month and Zero Report Year cannot precede
the month and year in the date the LEA converted to the
NIBRS.
093
Zero Report Element (Month)
A Segment Level 0 was submitted with a month and year
entered into positions 38 through 43 that was later than
the Month of Electronic submission and Year of Electronic
submission entered into positions 7 through 12.
094
Zero Report Element (Month)
The combined Zero Report Month and Zero Report Year
cannot be on or after the date LEA is placed in Coveredby Status. When Zero Report data are received for a LEA
in Covered-by Status, the FBI will remove the agency from
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.
096
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
06/15/2020
2019.2.1 NIBRS Technical Specification
118
Data Element (unnumbered)-Zero Report Year
Zero Report Year is used to identify the year in which Zero Report Month occurred.
Group:
Format:
Position:
Occurrence:
Mandatory:
Edits:
N/A
4-Character Numeric (YYYY)
40–43
Once per Zero Report Segment
Yes
Table 3-72 Zero Report Year Edit Description
Zero Report Year Element Edits
Data Element
Zero Report Element (Year)
Zero Report Element (Year)
Zero Report Element (Year)
Edit Description
Mandatory Data Elements (Mandatory = Yes) must be
populated with a valid data value and cannot be blank.
Zero Report Month and Zero Report Year cannot
precede the month and year in the date the LEA
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
the Month of Electronic submission and Year of
Electronic submission entered into positions 7 through
12.
Associated
Error Code
001
093
094
Data Values: 1991–Current Year
06/15/2020
2019.2.1 NIBRS Technical Specification
119
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: [email protected]
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
120
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
121
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
06/15/2020
2019.2.1 NIBRS Technical Specification
122
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
123
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
Position
Field Name
Description
1–4
Year
This value identifies the data value in Header Data Element “Year of
Submission”.
5–6
Month
This value identifies the data value in Header Data Element “Month of
Submission”.
7–13
Submission
Record
Number
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
will contain “0000600”.
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.
14
Segment
Action Type
This value identifies the data value in Header Data Element “Segment
Action Type”.
06/15/2020
2019.2.1 NIBRS Technical Specification
124
EDS Record Layout
Record
Position
Field Name
Description
15–23
ORI
This value identifies the data value in Data Element 1 (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.
24–35
Incident
Number
This value identifies the data value in Data Element 2 (Incident Number).
36
Segment
Level
This value identifies the data value in Header Data Element “Segment
Level”.
37–39
UCR
Offense
Code
This value identifies the data value in Data Element 6 (UCR Offense
Code) on the Offense Segment (Level 2) in error.
40–42
Person
Sequence
Number
This value identifies the data value in Data Element 23 (Victim Sequence
Number) on the Victim Segment (Level 4), Data Element 36 (Offender
Sequence Number) on the Offender Segment (Level 5), or Data Element
40 (Arrestee Sequence Number) on the Arrestee Segment (Level 6) for
the segment in error.
43
Type
Property
Loss/Etc.
This value identifies the data value in Data Element 14 (Type Property
Loss/Etc.) on the Property Segment (Level 3) in error.
44–46
Data
Element
Number
This value identifies the Data Element that is in error.
47–49
Error
Number
This value identifies the error number that can be used to refer to
additional information about the error condition.
50–61
Data Value
In Error
This value identifies the data value that is in error.
62–140
Error
Message
This is the error message associated with the error number identified in
record positions 47–49.
Note: When ORI is “99999999”, this value will contain “FBI Processed
Submission on MM/DD/YYYY”.
141–146
Unused
Field (blank)
The FBI no longer uses this field.
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
125
5.2.1 Structure Check Errors
Table 5-2 Structure Check Errors
Structure Check Errors
Error
Number
Error Message
Error Description
050
SEGMENT LEVELS ARE OUT OF
NUMERICAL ORDER FOR THIS
INCIDENT
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, 4, 5 must
be written in that order, not as 1, 2, 2, 5, 3, 4, 4, 4.
051
INVALID RECORD LEVEL ON
SUBMISSION
Segment Level must contain a valid data value
0–7.
055
CANNOT HAVE A GROUP A
INCIDENT REPORT WITHOUT
LEVEL 1 SEGMENT
Segment Level 1 (Administrative Segment) with
Segment Action Type I = Incident Report must be
the first segment submitted for each Group A
Incident Report.
056
DUPLICATE INCIDENTPREVIOUSLY ADDED
Data Element 2 (Incident Number) must be a
unique number for each incident submitted. No two
incidents can have the same incident number.
058
ALL SEGMENTS IN A
SUBMISSION MUST HAVE SAME
MONTH AND YEAR OF
SUBMISSION
Month of Submission and Year of Submission must
contain the same data values for each segment in
a NIBRS submission. The first segment processed
will be compared with all other segments to check
for this condition.
059
ALL SEGMENTS IN SUBMISSION
MUST BE FROM SAME STATE
Data Element 1 (ORI) must contain the same state
abbreviation code (e.g., SC, MD, etc.) in the first
two positions (record positions 17 & 18). For nonfederal LEAs, every segment in a submission must
have the same state code in the first two positions
of the ORI.
060
PROCESSING DATE PRECEDES
MONTH AND YEAR OF
SUBMISSION
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 submitted for a future month/year.
EACH OFFENSE MUST HAVE AT
LEAST ONE VICTIM
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 Data Element 6 (UCR Offense Code)
in Data Element 24 (Victim Connected to UCR
Offense Code).
THE CORRESPONDING
OFFENDER SEGMENT MUST
EXIST
Data Element 34 (Offender Number to be Related)
has a value that does not have a corresponding
Offender Segment. For example, if the field value
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).
065
070
06/15/2020
2019.2.1 NIBRS Technical Specification
126
Structure Check Errors
Error
Number
071
Error Message
Error Description
CANNOT HAVE ARRESTS WHEN
CLEARED EXCEPTIONALLY
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 (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 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:
072
RECOVERED PROPERTY MUST
ALSO BE SUBMITTED AS
STOLEN
1) When Data Element 6 (UCR Offense Code)
contains an offense that allows property to be
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
NUMBER OF RECOVERED
VEHICLES CANNOT BE
GREATER THAN THE NUMBER
STOLEN
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 Element 19
(Number of Recovered Motor Vehicles) within the
same incident.
074
PROPERTY SEGMENT MUST
EXIST WITH THIS OFFENSE
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
Kidnapping/Abduction, Crimes Against Property,
Drug/Narcotic Offenses, or Gambling Offenses.
075
MISSING A MANDATORY
SEGMENT LEVEL FOR A
COMPLETE INCIDENT
Segment Levels 1, 2, 4, and 5 (Administrative
Segment, Offense Segment, Victim Segment, and
Offender Segment) with Segment Action Type
I = Incident Report must be submitted for each
Group A Incident Report; they are mandatory.
073
06/15/2020
2019.2.1 NIBRS Technical Specification
127
Structure Check Errors
Error
Number
076
077
078
06/15/2020
Error Message
Error Description
PROPERTY SEGMENT CANNOT
EXIST WITH OFFENSE
SUBMITTED
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 =
Kidnapping/Abduction, Drug/Narcotic Offenses,
521 = Violation of National Firearm Act of 1934*,
522 = Weapons of Mass Destruction*, 526 =
Explosives*, 26H = Money Laundering*,
Commerce Violations*, or Gambling Offenses.
*Denotes offenses for federal and tribal LEA
reporting only
NEED A PROPERTY LOSS CODE
OF 1 OR 8 WHEN THIS OFFENSE
IS ATTEMPTED
(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*,
522 = Weapons of Mass Destruction*, 526 =
Explosives*, 26H = Money Laundering*,
Commerce Violations*, or Gambling Offenses and
Data Element 7 (Offense Attempted/Completed) is
Attempted.
*Denotes offenses for federal and tribal LEA
reporting only
A VALID PROPERTY LOSS CODE
DOES NOT EXIST FOR THIS
COMPLETED OFFENSE
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.
Data Element 14 (Type Property Loss/Etc.) must
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.
2019.2.1 NIBRS Technical Specification
128
Structure Check Errors
Error
Number
Error Message
Error Description
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
129
Structure Check Errors
Error
Number
Error Message
Error Description
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
06/15/2020
2019.2.1 NIBRS Technical Specification
130
Structure Check Errors
Error
Number
080
06/15/2020
Error Message
CRIMES AGAINST SOCIETY CAN
HAVE ONLY ONE
SOCIETY/PUBLIC VICTIM
Error Description
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:
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
2019.2.1 NIBRS Technical Specification
131
Structure Check Errors
Error
Number
Error Message
Error Description
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:
081
TYPE PROPERTY LOSS CODE IS
NOT VALID WITH THE
OFFENSES SUBMITTED
Arson-Attempted
Bribery-Attempted/Completed
Burglary/Breaking & Entering-Attempted/
Completed
Counterfeiting/Forgery-Attempted
Destruction/Damage/Vandalism of PropertyAttempted
Drug/Narcotic Violations-Attempted/Completed
Drug Equipment Violations-Attempted/Completed
Embezzlement-Attempted
Extortion/Blackmail-Attempted
False Pretenses/Swindle/Confidence GameAttempted
Credit Card/Automated Teller Machine FraudAttempted
Impersonation-Attempted
Welfare Fraud-Attempted
Wire Fraud-Attempted
Identity Theft-Attempted
Hacking/Computer Invasion-Attempted
Betting/Wagering-Attempted
Operating/Promoting/Assisting GamblingAttempted
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 DeviceAttempted
Theft From Motor Vehicle-Attempted
Theft of Motor Vehicle Parts or AccessoriesAttempted
Motor Vehicle Theft-Attempted
Robbery-Attempted
Stolen Property Offenses-Attempted/Completed
06/15/2020
2019.2.1 NIBRS Technical Specification
132
Structure Check Errors
Error
Number
Error Message
Error Description
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
06/15/2020
2019.2.1 NIBRS Technical Specification
133
Structure Check Errors
Error
Number
Error Message
Error Description
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
134
Structure Check Errors
Error
Number
Error Message
Error Description
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
06/15/2020
2019.2.1 NIBRS Technical Specification
135
Structure Check Errors
Error
Number
Error Message
Error Description
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
06/15/2020
2019.2.1 NIBRS Technical Specification
136
Structure Check Errors
Error
Number
Error Message
Error Description
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
06/15/2020
2019.2.1 NIBRS Technical Specification
137
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 & EnteringAttempted/Completed
250 = Counterfeiting/Forgery-Attempted
290 = Destruction/Damage/Vandalism of PropertyAttempted
35A = Drug/Narcotic Violations-Attempted
35B = Drug Equipment Violations-Attempted
270 = Embezzlement-Attempted
210 = Extortion/Blackmail-Attempted
26A = False Pretenses/Swindle/Confidence GameAttempted
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 GamblingAttempted
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 AccessoriesAttempted
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
06/15/2020
2019.2.1 NIBRS Technical Specification
138
Structure Check Errors
Error
Number
Error Message
Error Description
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.
084
RECOVERED PROPERTY VALUE
CANNOT BE GREATER THAN
THE VALUE WHEN STOLEN
Note: An exception occurs when Data Element 6
(UCR Offense Code) contains an offense that
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.
EACH VICTIM MUST BE
CONNECTED TO AT LEAST TWO
OFFENDERS
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
Segment Level 5 (Offender Segment) records
submitted for the incident, and Data Element 25
(Type of Victim) is I = Individual or L = Law
Enforcement.
088
GROUP A AND GROUP B
CANNOT HAVE SAME
IDENTIFIER
Segment Level 6 (Arrestee Segment) and Segment
Level 7 (Group B Arrest Report Segment) cannot
have the same data values entered in Data
Element 2 (Incident Number) and Data Element 41
(Arrest Transaction Number), respectively, for the
same ORI.
090
ZERO REPORTING MONTH IS
NOT 01-12
A Segment Level 0 was submitted that had an
invalid reporting month in positions 38 through 39.
The data entered must be a valid month of 01
through 12.
091
ZERO-REPORTING YEAR IS
INVALID
A Segment Level 0 was submitted that did not
have four numeric digits in positions 40 through 43.
085
06/15/2020
2019.2.1 NIBRS Technical Specification
139
Structure Check Errors
Error
Number
Error Message
Error Description
092
ZERO REPORTING INCIDENT
NUMBER MUST BE ALL ZEROS
(Incident Number) Zero-Reporting Segment (Level
0) must contain 12 zeros as the Incident Number.
093
ZERO REPORT MONTH/YEAR IS
PRIOR TO AGENCY
CONVERSION TO THE NIBRS
094
ZERO REPORT MONTH/YEAR
EXCEEDED MONTH/YEAR OF
SUBMISSION
Zero Report Month and Zero Report Year cannot
precede the month and year in the date the LEA
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 the Month of Electronic submission
and Year of Electronic submission entered into
positions 7 through 12.
095
PRE-NIBRS SEGMENTS CANNOT
BE DELETED IN THIS WAY
An instruction to delete data in NIBRS before the
agency transitioned to NIBRS, which is not
allowed.
096
ZERO REPORT MONTH & ZERO
REPORT YEAR CANNOT BE ON
OR AFTER DATE AGENCY IS
PLACED ON COVERED-BY
STATUS
The combined Zero Report Month and Zero Report
Year cannot be on or after the date an 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 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.
931
THE ORI INFORMATION IS
DUPLICATED IN THE
REFERENCE DATA
The ORI exists in the reference table for a different
agency. Verify that the ORI is accurate.
932
INVALID ORI FORMAT - THE ORI
WAS NOT FOUND IN THE
REFERENCE DATA
The ORI submitted was not found in the reference
data table. Verify that the submitting agency is
providing an accurate ORI for the data submission.
933
THE ORI IS COVERED BY
ANOTHER AGENCY
The ORI submitted is currently in a Covered-by
status. Verify that the information being provided is
accurate and/or to ensure that the submitting
agency is now providing its own information and is
no longer in Covered-by status.
934
THE ORI IS MARKED AS
DELETED IN THE REFERENCE
DATA
The ORI submitted has been marked for deletion.
Verification is needed to ensure this is accurate.
NIBRS CERTIFICATION DATE
DOES NOT EXIST
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
first pass a testing phase to achieve NIBRS
certification and then the FBI reference data
administrator can enter a certification date into the
system.
935
06/15/2020
2019.2.1 NIBRS Technical Specification
140
Structure Check Errors
Error
Number
Error Message
Error Description
937
PRE-NIBRS INCIDENT RECEIVED
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
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.
938
MULTIPLE INCIDENTS ON FILE
Action Type of “A” is used, and there are multiple
incidents on file for the same agency/incident
number.
939
CANNOT MODIFY PRE-NIBRS
GROUP B INCIDENT
Action Type of “M” is used for a Group B Arrest
and the Arrest Date is before the agency
transitioned to NIBRS.
940
EXCEPTIONAL CLEARANCE
ALREADY ON FILE
Agency is trying to add an exceptional clearance
and the incident has already been exceptionally
cleared either by circumstances or arrest.
941
WEB SERVICE SUBMISSION
ALREADY IN PROCESS
Agency is trying to perform any insert or replace
action for a Group A/Group B Incident while an
action is currently pending for the same
agency/incident number in web services.
952
INVALID ORI FORMAT - NOT A
VALID ORI - NOT IN UCR ORI
FILE
Data Element 1 (ORI) and Data Element 25C
(Officer–ORI Other Jurisdiction) must be a valid
nine-character NCIC ORI.
5.2.2 Administrative Segment Errors
Table 5-3 Administrative Segment Errors
Administrative Segment Errors
Error
Number
Error Message
Error Description
101
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element is
mandatory or when the conditions are met for
data that must be entered into a conditionally
mandatory field.
104
INVALID DATA VALUE-NOT ON
FBI VALIDATION TABLE
The referenced data element must contain a valid
data value when it is entered; blank is permissible
on nonmandatorynonmandatory fields.
06/15/2020
2019.2.1 NIBRS Technical Specification
141
Administrative Segment Errors
Error
Number
Error Message
Error Description
INVALID DATA VALUE FOR 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 31days). Also, the date cannot
exceed the current date.
106
INVALID DATA VALUE FOR HOUR
(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
Element 3 (Incident Date/Hour) must be populated
with a valid hour (00-23). Incident Hour Unknown
(Blank) is not a valid entry.
115
CANNOT HAVE EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON-BLANK CHARACTERS
(Incident Number) Must be blank right-fill if under
12 characters in length. Cannot have embedded
blanks between the first and last characters
entered.
116
MUST BE LEFT JUSTIFIED
BLANK DETECTED IN FIRST
POSITION
(Incident Number) must be left-justified with blank
right-fill. Since the number is less than 12
characters, it must begin in position 1.
105
Must contain a valid character combination of the
following:
117
CANNOT HAVE CHARACTERS
OTHER THAN A–Z, 0–9, AND/OR
HYPHEN, AND/OR BLANKS
•
•
•
A–Z (capital letters only)
0–9
Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
118
06/15/2020
DATE CANNOT BE ON OR AFTER
THE INACTIVE DATE OF THE ORI
The UCR Program has determined that an ORI
will no longer be submitting data to the FBI as of
an inactive date. The UCR Program will not
accept data from the ORI after this date.
2019.2.1 NIBRS Technical Specification
142
Administrative Segment Errors
Error
Number
Error Message
Error Description
Data Element 2A (Cargo Theft) must be blank,
unless Data Element 6 (UCR Offense Code)
includes at least one of the following:
119
122
151
06/15/2020
CARGO THEFT DATA CAN ONLY
BE SUBMITTED FOR SPECIFIC
OFFENSES
CARGO THEFT VALUE
REQUIRED WITH SPECIFIC
OFFENSES
REPORT INDICATOR MUST BE
BLANK OR “R”
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
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
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
This field must be blank if the Incident Date is
known. If the Incident Date is unknown, then the
Report Date would be entered instead and must
be indicated with an “R” in the Report Indicator
field within the Administrative Segment.
2019.2.1 NIBRS Technical Specification
143
Administrative Segment Errors
Error
Number
Error Message
Error Description
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
153
VALUE ENTERED CONFLICTS
WITH PRESENCE OF AN ENTRY
IN EXCEPTIONAL CLEARANCE
DATE
Data Element 4 (Cleared Exceptionally) cannot be
N = Not Applicable if Data Element 5 (Exceptional
Clearance Date) is entered.
155
CLEARANCE DATE PREDATES
INCIDENT DATE
Data Element 5 (Exceptional Clearance Date) is
earlier than Data Element 3 (Incident Date/Hour).
156
AN ENTRY MUST BE MADE
WHEN CLEARED
EXCEPTIONALLY HAS ENTRIES
OF A-E
Data Element 5 (Exceptional Clearance Date)
must be present if the case was cleared
exceptionally. Data Element 4 (Cleared
Exceptionally) has an entry of A through E;
therefore, the date must also be entered.
170
INCIDENT DATE CANNOT BE
AFTER MONTH AND YEAR OF
ELECTRONIC SUBMISSION
Data Element 3 (Incident Date/Hour) The date
cannot be later than the year and month the
electronic submission represents. For example,
the May 1999 electronic submission cannot
contain incidents happening after this date.
172
INCIDENT DATE/HOUR FOR I
RECORDS CANNOT PREDATE
01/01/1991
Data Element 3 (Incident Date) cannot be earlier
than 01/01/1991. This edit will preclude dates that
are obviously incorrect since the FBI began
accepting NIBRS data on this date.
06/15/2020
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.
2019.2.1 NIBRS Technical Specification
144
Administrative Segment Errors
Error
Number
Error Message
Error Description
173
INCIDENT DATE CANNOT BE
BEFORE DATE ORI WENT IBR
A Group A Incident Report was submitted with
Data Element 3 (Incident Date/Hour) containing a
date that occurred before the agency converted
over to NIBRS. Because of this, the record was
rejected. At some point, the participant will convert
its local agencies from SRS reporting to IncidentBased Reporting. Once the participant starts to
send NIBRS data for a converted agency to the
FBI, any data received from this agency that could
possibly be interpreted as duplicate reporting
within both the SRS and NIBRS for the same
month will be rejected by the FBI. In other words,
if the participant sends IBR data for an agency for
the first time on September 1999, monthly
submittal, dates for incidents, recovered property,
and arrests must be within September. The
exception is when exceptional clearances occur
for a pre-IBR incident. In this case, Data Element
3 (Incident Date/Hour) may be earlier than
September 1999, but Data Element 5 (Exceptional
Clearance Date) must be within September 1999.
The FBI will reject data submitted for prior
months. Thereafter, all data coming from this
agency must have dates subsequent to the initial
start date of September 1999, except as
mentioned previously. The SRS already contains
aggregate data for the months prior to NIBRS
conversion. If the FBI were to accept IBR data for
months previously reported with Summary data,
the result would be duplicate reporting for those
months.
175
CANNOT CALCULATE BASE
DATE FROM INCIDENT DATE
The electronic submission control date (positions
7 through 12, month and year) and Data Element
3 (Incident Date/Hour) must both be valid dates
for calculating timeframes.
178
THIS ADMINISTRATIVE
SEGMENT HAS A CONFLICTING
LENGTH
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
RDW, then all future 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.
197
06/15/2020
MISSING INCIDENT DATE FOR
DELETE
Data Element 3 (Incident Date) is missing for a
Group A Incident Report with a Segment Action
Type of D = Delete; must be populated with a
valid data value and cannot be blank.
2019.2.1 NIBRS Technical Specification
145
Administrative Segment Errors
Error
Number
Error Message
Error Description
198
MISSING INCIDENT DATE FOR
DELETE - INCIDENT NUMBER
MATCHES GROUP A INCIDENT
REPORTS WITH INCIDENT DATE
OUTSIDE TWO YEAR WINDOW
Data Element 3 (Incident Date) is missing for a
Group A Incident Report with a Segment Action
Type of D = Delete; at least one Group A Incident
Report is on file that matches Data Element 2
(Incident Number) with an Incident Date outside
the two year window.
199
MISSING INCIDENT DATE FOR
DELETE - INCIDENT NUMBER
MATCHES MULTIPLE GROUP A
INCIDENT REPORTS
Data Element 3 (Incident Date) is missing for a
Group A Incident Report with a Segment Action
Type of D = Delete; must be populated with a
valid data value and cannot be blank. Incident
Number matches multiple Group A Incident
Reports.
5.2.3 Offense Segment Errors
Table 5-4 Offense Segment Errors
Offense Segment Errors
Error
Number
Error Message
Error Description
201
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element is
mandatory or when the conditions are met for
data that must be entered into a conditionally
mandatory field.
202
CONTAINS NONNUMERIC ENTRY
Data Element 10 (Number of Premises Entered) is
not a numeric entry of 01 through 99.
204
INVALID DATA VALUE
The referenced data element must contain a valid
data value when it is entered; blank is permissible
on nonmandatory fields.
06/15/2020
2019.2.1 NIBRS Technical Specification
146
Offense Segment Errors
Error
Number
Error Message
Error Description
205
ERROR - INVALID OFFENSE
CODE FOR LOCATION TYPE
CYBERSPACE
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
26H = Money Laundering*
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
206
ERROR - DUPLICATE VALUE =
[value]
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
147
Offense Segment Errors
Error
Number
Error Message
Error Description
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.
207
ERROR - MUTUALLY EXCLUSIVE
VALUE = [value]
•
•
•
•
207A ERROR MUTUALLY EXCLUSIVE
VALUE - SUSPECTED OF USING
207B ERROR MUTUALLY EXCLUSIVE
VALUE - BIAS MOTIVATION
207C ERROR MUTUALLY EXCLUSIVE
VALUE - CRIMINAL ACTIVITY / GANG
INFORMATION
207D ERROR MUTUALLY EXCLUSIVE
VALUE - WEAPON CODE
215
CANNOT CONTAIN EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON BLANK CHARACTERS
Must be blank right-fill if under 12 characters in
length. Cannot have embedded blanks between
the first and last characters entered.
216
MUST BE LEFT-JUSTIFIED–
BLANK DETECTED IN FIRST
POSITION
Must be left-justified with blank right-fill if under 12
characters in length.
Must contain a valid character combination of the
following:
217
CANNOT HAVE CHARACTERS
OTHER THAN A–Z, 0–9, AND/OR
HYPHEN, AND/OR BLANKS
•
•
•
A–Z (capital letters only)
0–9
Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
06/15/2020
2019.2.1 NIBRS Technical Specification
148
Offense Segment Errors
Error
Number
Error Message
Error Description
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:
219
DATA CAN ONLY BE ENTERED
FOR SPECIFIC OFFENSES
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*
620 = Wildlife Trafficking*
*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
06/15/2020
2019.2.1 NIBRS Technical Specification
149
Offense Segment Errors
Error
Number
Error Message
Error Description
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:
220
DATA MUST BE ENTERED FOR
SPECIFIC OFFENSES
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*
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:
221
06/15/2020
DATA MUST BE ENTERED FOR
SPECIFIC OFFENSES
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/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
2019.2.1 NIBRS Technical Specification
150
Offense Segment Errors
Error
Number
Error Message
Error Description
Data Element 13 (Type of Weapon/Force
Involved) Type of Weapon/Force Involved can
only be entered when the UCR Offense Code is:
222
DATA CAN ONLY BE ENTERED
FOR SPECIFIC OFFENSES
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/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:
250
OFFENSE CODE CAN ONLY BE
USED BY FEDERAL 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
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*
*Denotes offenses for federal and tribal LEA
reporting only
06/15/2020
2019.2.1 NIBRS Technical Specification
151
Offense Segment Errors
Error
Number
Error Message
Error Description
251
INVALID CODE
(Offense Attempted/Completed) Must be a valid
code of A = Attempted or C = Completed.
252
OFFENSE CODE MUST BE 220
WITH A LOCATION TYPE OF 14
OR 19 FOR DATA TO BE
ENTERED
When Data Element 10 (Number of Premises
Entered) is entered, Data Element 9 (Location
Type) must be 14 = Hotel/Motel/Etc. or
19 = Rental Storage Facility, and Data Element 6
(UCR Offense Code) must be
220 = Burglary/Breaking & Entering.
253
MUST BE PRESENT WHEN
OFFENSE CODE IS 220
Data Element 11 (Method of Entry) was not
entered; it must be entered when UCR Offense
Code of 220 = Burglary/Breaking & Entering has
been entered.
254
MUST BE BLANK WHEN
OFFENSE IS OTHER THAN 220
Data Element 11 (Method of Entry) only applies to
UCR Offense Code of 220 = Burglary/Breaking &
Entering. Since a burglary offense was not
entered, the Method of Entry should not have
been entered.
255
AUTOMATIC INDICATOR MUST
BE BLANK OR “A”
Must be A = Automatic or blank = Not Automatic
256
OFFENSE CODES OF 09A, 09B,
09C, 13A, 13B, 13C, AND 360
MUST HAVE ENTRY OF C
Code must be C = Completed if Data Element 6
(UCR Offense Code) is an Assault, Homicide, or
360 = Failure to Register as a Sex Offender*.
*Denotes offenses for federal and tribal LEA
reporting only
257
MUST BE PRESENT WITH AN
OFFENSE CODE OF 220 AND A
LOCATION TYPE OF 14 OR 19
Data Element 10 (Number of Premises Entered)
must be entered if offense code is
220 = Burglary/Breaking & Entering and if Data
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:
258
262
06/15/2020
WEAPON TYPE MUST = 11, 12,
13, 14, OR 15 FOR AN “A” IN THE
AUTO INDICATOR
DUPLICATE OFFENSE SEGMENT
11 = Firearm (Type Not Stated)
12 = Handgun
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.
When a Group A Incident Report is submitted, the
individual segments comprising the incident
cannot contain duplicates. In this case, two
Offense Segments were submitted having the
same offense in Data Element 6 (UCR Offense
Code).
2019.2.1 NIBRS Technical Specification
152
Offense Segment Errors
Error
Number
Error Message
Error Description
263
CANNOT HAVE MORE THAN 10
OFFENSES
Offenses may be submitted only 10 times for each
Group A Incident Report; 10 offense codes are
allowed for each incident.
264
GROUP A OFFENSE CANNOT
CONTAIN A GROUP B OFFENSE
Data Element 6 (UCR Offense Code) must be a
Group A UCR Offense Code, not a Group B
Offense Code.
265
INVALID WEAPON WITH AN
OFFENSE OF 13B
If an Offense Segment (Level 2) was submitted for
13B = Simple Assault, Data Element 13 (Type
Weapon/Force Involved) can only have codes of
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.
266
NO OTHER OFFENSE CAN BE
SUBMITTED WITH JUSTIFIABLE
HOMICIDE
When a Justifiable Homicide is reported, no other
offense may be reported in the Group A Incident
Report. These should be submitted on another
Group A Incident Report.
267
INVALID WEAPON TYPE FOR
HOMICIDE OFFENSES
If a homicide offense is submitted, Data Element
13 (Type Weapon/Force Involved) cannot have
99 = None. Some type of weapon/force must be
used in a homicide offense.
268
LARCENY OFFENSE CANNOT
HAVE A MOTOR VEHICLE
PROPERTY DESCRIPTION
ENTERED
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, 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).
269
POSSIBLE CLASSIFICATION
ERROR OF AGGRAVATED
ASSAULT 13A CODED AS
SIMPLE 13B
If Data Element 6 (UCR Offense Code) is
13B = Simple Assault and the weapon involved is
11 = Firearm, 12 = Handgun, 13 = Rifle,
14 = Shotgun, or 15 = Other Firearm, then the
offense should instead be classified as
13A = Aggravated Assault.
270
JUSTIFIABLE HOMICIDE MUST
BE CODED AS NON BIAS
MOTIVATED
Must be 88 = None when Data Element 6 (UCR
Offense Code) is 09C = Justifiable Homicide.
06/15/2020
2019.2.1 NIBRS Technical Specification
153
Offense Segment Errors
Error
Number
284
Error Message
THIS OFFENSE SEGMENT HAS A
CONFLICTING LENGTH
Error Description
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.
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
Number
Error Message
Error Description
301
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element is
mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory
field.
302
CONTAINS NONNUMERIC ENTRY
Must be numeric entry with zero left-fill. Refer to
individual data element for specific formatting
instructions.
304
INVALID DATA VALUE
The referenced data element must contain a valid
data value when it is entered; Blank is permissible
on nonmandatory fields
305
DATE RECOVERED IS INVALID
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
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).
306
ERROR-DUPLICATE DATA
VALUE
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.
Refer to individual data elements for exceptions.
06/15/2020
2019.2.1 NIBRS Technical Specification
154
Property Segment Errors
Error
Number
Error Message
315
CANNOT HAVE EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON-BLANK CHARACTERS
316
MUST BE LEFT-JUSTIFIED–
BLANK DETECTED IN FIRST
POSITION
317
CANNOT HAVE CHARACTERS
OTHER THAN A–Z, 0–9, AND/OR
HYPHEN, AND/OR BLANKS
Error Description
Data Element 2 (Incident Number) Must be blank
right-fill if under 12 characters in length. Cannot
have embedded blanks between the first and last
characters entered.
Data Element 2 (Incident Number) Must be leftjustified with blank right-fill if under 12 characters in
length.
Must contain a valid character combination of the
following:
•
•
•
A–Z (capital letters only)
0–9
Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not
valid.
351
06/15/2020
PROPERTY VALUE OF ZERO IS
NOT ALLOWED
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
48=Documents–Personal or Business
65=Identity Documents
66=Identity–Intangible
Optional zero
77=Other
99=(blank)–this data value is not currently
used by the FBI.
2019.2.1 NIBRS Technical Specification
155
Property Segment Errors
Error
Number
Error Message
Error Description
(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.
352
DATA ELEMENTS 15 - 22 MUST
BE BLANK WHEN PROPERTY
LOSS CODE=1 OR 8
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 Element 20
(Suspected Drug Type) must be entered.
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.
353
PENDING INVENTORY MUST
HAVE PROPERTY VALUE OF 1
Data Element 15 (Property Description) is 88 =
Pending Inventory, but Data Element 16 (Value of
Property) is not $1.
354
VALUE OF PROPERTY ENTERED
WITHOUT PROPERTY
DESCRIPTION
Data Element 16 (Value of Property) contains a
value, but Data Element 15 (Property Description)
was not entered.
355
PROPERTY LOSS CODE (14)
MUST=5 (RECOVERED) FOR
DATA TO BE ENTERED
Data Element 14 (Type Property Loss/Etc.) must
be 5 = Recovered for Data Element 17 (Date
Recovered) to be entered.
356
PROPERTY DESCRIPTION (15)
AND VALUE (16) MUST BOTH
EXIST IF DATA ARE PRESENT
Data Element 17 (Date Recovered) was entered,
but Data Elements 15 (Property Description)
and/or 16 (Value of Property) were not entered.
STOLEN VEHICLE NUMBER
CANNOT BE ENTERED WITHOUT
MOTOR VEHICLE OFFENSE
Data Element 18 (Number of Stolen Motor
Vehicles) was entered. However, Data Element 14
(Type Property Loss/Etc.) 7 = Stolen/Etc. 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.
DATA MUST EXIST WITH AN
OFFENSE CODE OF 240 AND A
PROPERTY LOSS OF 7
Entry must be made for Data Element 18 (Number
of Stolen Motor Vehicles) when Data Element 6
(UCR Offense Code) is 240 = Motor Vehicle Theft,
Data Element 7 (Offense Attempted/Completed) is
C = Completed, and Data Element 14 (Type
Property Loss/Etc.) is 7 = Stolen/Etc.
357
358
06/15/2020
2019.2.1 NIBRS Technical Specification
156
Property Segment Errors
Error
Number
359
Error Message
Error Description
Data Element 15 (Property Description) must be
one of the following:
ALL NONVEHICULAR PROPERTY
DESCRIPTIONS WERE ENTERED
03 = Automobiles
05 = Buses
24 = Other Motor Vehicles
28 = Recreational Vehicles
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.
360
PROPERTY LOSS (14) MUST BE
5 WITH AN OFFENSE CODE OF
240 FOR DATA TO BE ENTERED
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.
The exception to this rule is when recovered
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.
361
DATA MUST EXIST WITH AN
OFFENSE CODE OF 240 AND A
PROPERTYLOSS OF 5
Entry must be made for Data Element 19 (Number
of Recovered Motor Vehicles) When Data Element
6 (UCR Offense Code) is 240 = Motor Vehicle
Theft, Data Element 7 (Offense Attempted/
Completed) is C = Completed, Data Element 14
(Type Property Loss/Etc.) is 5 = Recovered, and
vehicle codes were recovered.
362
TWO OTHER CODES MUST BE
ENTERED WHEN AN X IS
PRESENT
Since X = Over 3 Drug Types was entered in Data
Element 20 (Suspected Drug Type), two other
codes must also be entered. Less than three codes
are present.
363
DRUG QUANTITY
MEASUREMENT MUST BE
BLANK WITH OVER 3 DRUG
TYPES
Since Data Element 20 (Suspected Drug Type)
contains X=Over 3 Drug Types, Data Element 21
(Estimated Quantity) and 22 (Type Measurement)
must be blank.
06/15/2020
2019.2.1 NIBRS Technical Specification
157
Property Segment Errors
Error
Number
Error Message
Error Description
WITH DATA ENTERED BOTH
QUANTITY (21) AND
MEASUREMENT (22) MUST BE
PRESENT
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 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.
365
OFFENSE=35A AND PROPERTY
LOSS=6 AND DESCRIPTION=10
MUST EXIST
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 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.
366
WITH DATA ENTERED BOTH
TYPE (20) AND MEASUREMENT
(22) MUST BE PRESENT
Data Element 21 (Estimated Quantity) was
entered, but Data Elements 20 (Suspected Drug
Type) and/or 22 (Type Measurement) were not
entered; both must be entered.
364
367
DRUG TYPE MUST BE E, G, OR K
FOR A VALUE OF NP
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
Plants to the following drugs:
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.
368
372
06/15/2020
WITH DATA ENTERED BOTH
TYPE (20) AND QUANTITY (21)
MUST BE PRESENT
Data Element 22 (Type Measurement) was
entered, but Data Elements 20 (Suspected Drug
Type) and/or 21 (Estimated Quantity) were not
entered; both must be entered.
DATA ELEMENTS 15-22 WERE
ALL BLANK WITH THIS
PROPERTY LOSS CODE
If 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., Data Elements 15
through 22 must have applicable entries in the
segment.
2019.2.1 NIBRS Technical Specification
158
Property Segment Errors
Error
Number
375
Error Message
MANDATORY FIELD WITH THE
PROPERTY LOSS CODE
ENTERED
Error 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
3=Counterfeited/Forged
4=Destroyed/Damaged/Vandalized
5=Recovered
6=Seized
7=Stolen/Etc.
DUPLICATE TYPE PROPERTY
LOSS SEGMENTS ARE NOT
ALLOWED
When a Group A Incident Report is submitted, the
individual segments comprising the Incident cannot
contain duplicates. Example, two property
segments cannot be submitted having the same
entry in Data Element 14 (Type Property
Loss/Etc.).
382
DRUG/NARCOTIC VIOLATIONS
OFFENSE MUST BE SUBMITTED
FOR SEIZED DRUGS
Segment Level 3 (Property Segment) cannot be
submitted with 10=Drugs/Narcotics in Data
Element 15 (Property Description) and blanks in
Data Element 16 (Value of Property) unless Data
Element 6 (UCR Offense Code) is
35A=Drug/Narcotic Violations.
383
PROPERTY VALUE MUST BE
BLANK FOR 35A (SINGLE
OFFENSE)
Data Element 16 (Value of Property) must be blank
when Data Element 15 (Property Description) code
is 10=Drugs/Narcotics and the only offense
submitted is a 35A=Drug/Narcotic Violations.
376
384
387
06/15/2020
DRUG QUANTITY MUST BE
NONE WHEN DRUG
MEASUREMENT IS NOT
REPORTED
WITH A PROPERTY LOSS=6 AND
ONLY OFFENSE 35A CANNOT
HAVE DESCRIPTION 11 or WITH
A PROPERTY LOSS=6 AND ONLY
OFFENSE 35B CANNOT HAVE
DESCRIPTION 10
Data Element 21 (Estimated Drug Quantity) must
be 000000001000=None (i.e., 1) when Data
Element 22 (Type Drug Measurement) is XX=Not
Reported indicating the drugs were 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 values.
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 and no other
crimes requiring a Property Segment exist.
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 and no other
crimes requiring a Property Segment exist.
2019.2.1 NIBRS Technical Specification
159
Property Segment Errors
Error
Number
388
Error Message
NUMBER STOLEN IS LESS THAN
NUMBER OF VEHICLE CODES
Error Description
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 03 = Automobiles and 05 = Buses
were entered as being stolen, 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.
389
NUMBER RECOVERED IS LESS
THAN NUMBER OF VEHICLE
CODES
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 codes of
03 = Automobiles and 05 = Buses were entered as
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
160
Property Segment Errors
Error
Number
Error Message
Error Description
(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
390
ILLOGICAL PROPERTY
DESCRIPTION FOR THE
OFFENSE SUBMITTED
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
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
391
PROPERTY VALUE MUST BE
ZERO FOR DESCRIPTION
SUBMITTED
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.)
Data Element 16 (Value of Property) must be zero
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
06/15/2020
2019.2.1 NIBRS Technical Specification
161
Property Segment Errors
Error
Number
392
Error Message
Error Description
35A OFFENSE ENTERED AND
1=NONE ENTERED MISSING
SUSPECTED DRUG TYPE (20)
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 suspected drug
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
Number
Error Message
Error Description
401
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element is
mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory
field.
402
CONTAINS NONNUMERIC ENTRY
Must contain numeric entry with zero left-fill.
404
INVALID DATA VALUE
The referenced data element must contain a valid
data value when it is entered; blank is permissible
on nonmandatory fields.
406
ERROR - DUPLICATE VALUE =
[value]
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.
407
ERROR - MUTUALLY EXCLUSIVE
VALUE = [value]
Data Element 33 (Type Injury) Can have multiple
data values and was entered with multiple values.
However, the entry shown between the brackets in
[value] above cannot be entered with any other
data value.
408
EXACT AGE MUST BE IN FIRST
TWO POSITIONS
Data Element 26 (Age of Victim) contains data, but
is not left-justified. A single two-character age must
be in positions 1 and 2 of the field.
409
CONTAINS NONNUMERIC ENTRY
Data Element 26 (Age of Victim) contains more
than two characters indicating a possible agerange was being attempted. If so, the field must
contain a numeric entry of four digits.
410
FIRST AGE MUST BE LESS THAN
SECOND FOR AGE RANGE
Data Element 26 (Age of Victim) was entered as an
age-range. Accordingly, the first age component
must be less than the second age.
06/15/2020
2019.2.1 NIBRS Technical Specification
162
Victim Segment Errors
Error
Number
Error Message
415
CANNOT CONTAIN EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON BLANK CHARACTERS
Data Element 2 (Incident Number) must be blank
right-fill if under 12 characters in length. Cannot
have embedded blanks between the first and last
characters entered.
416
MUST BE LEFT-JUSTIFIED–
BLANK DETECTED IN FIRST
POSITION
Data Element 2 (Incident Number) must be leftjustified with blank right-fill if under 12 characters in
length.
Error Description
Data Element 2 (Incident Number) must contain a
valid character combination of the following:
417
CANNOT HAVE CHARACTERS
OTHER THAN A–Z, 0–9, AND/OR
HYPHEN, AND/OR BLANKS
•
•
•
A–Z (capital letters only)
0–9
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
24 (Victim Connected to UCR Offense Code) are:
419
DATA CAN ONLY BE ENTERED
FOR SPECIFIC OFFENSES
422
AGE RANGE CANNOT HAVE “00”
IN FIRST TWO POSITIONS
Data Element 26 (Age of Victim) was entered as an
age-range. Therefore, the first age component
cannot be 00 = Unknown.
450
VICTIM IS SPOUSE BUT AGE IS
LESS THAN 13
Data Element 26 (Age of Victim) cannot be less
than 13 years old when Data Element 35
(Relationship of Victim to Offender) contains a
relationship of SE = Spouse.
06/15/2020
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
2019.2.1 NIBRS Technical Specification
163
Victim Segment Errors
Error
Number
Error Message
Error Description
451
VICTIM NUMBER ALREADY
EXISTS
When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot
contain duplicates. In this case, two victim
segments were submitted having the same entry in
Data Element 23 (Victim Sequence Number).
452
AGE OF VICTIM MUST BE
GREATER THAN OR EQUAL TO
17 AND LESS THAN OR EQUAL
TO 98 WHEN VICTIM TYPE (25) =
L
(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
Enforcement Officer. (Data Element 26 must be
>=17 & <=98 or Data Element 26 = 00)
453
MUST BE PRESENT WHEN
VICTIM TYPE (25) = I
The data element associated with this error must
be present when Data Element 25 (Type of Victim)
is I = Individual.
454
MUST BE ENTERED WHEN
VICTIM TYPE IS LAW
ENFORCEMENT OFFICER
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 Victim), and Data
Element 28 (Race of Victim) must be entered when
Data Element 25 (Type of Victim) is L = Law
Enforcement Officer.
455
ADDITIONAL JUSTIFIABLE
HOMICIDE IS MANDATORY WITH
A 20 OR 21 ENTERED
Data Element 31 (Aggravated Assault/Homicide
Circumstances) contains: 20 = Criminal Killed by
Private Citizen or 21 = Criminal Killed by Police
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.
456
MULTIPLE VALUES ENTERED
FOR DATA ELEMENT ARE NOT
COMPATIBLE - VALUES ARE
MUTUALLY EXCLUSIVE
2) Multiple values from more than one category
were entered.
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.
457
WHEN DATA ELEMENT 32 IS
ENTERED, DATA ELEMENT 31
MUST EQUAL 20 OR 21
Data Element 32 (Additional Justifiable Homicide
Circumstances) was entered, but Data Element 31
(Aggravated Assault/Homicide Circumstances)
does not reflect a justifiable homicide
circumstance.
458
VICTIM TYPE (25) MUST BE I OR
L FOR DATA TO BE ENTERED
The Data Element associated with this error cannot
be entered when Data Element 25 (Type of Victim)
is not I = Individual or L = Law Enforcement Officer.
06/15/2020
2019.2.1 NIBRS Technical Specification
164
Victim Segment Errors
Error
Number
Error Message
460
RELATIONSHIP MUST BE
ENTERED WHEN AN OFFENDER
NUMBER (34) EXISTS
461
ENTRY FOR TYPE OF VICTIM
MUST BE "G" WHEN THIS
OFFENSE CODE IS ENTERED
Error Description
Corresponding Data Element 35 (Relationship of
Victim to Offender) data must be entered when
Data Element 34 (Offender Numbers to be
Related) is entered with a value greater than 00.
(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*
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
INVALID AGGRAVATED
ASSAULT/HOMICIDE FOR 13A
OFFENSE
Data Element 31 (Aggravated Assault/Homicide
Circumstances) can only have codes of 01 through
06 and 08 through 10 when Data Element 24
(Victim Connected to UCR Offense) is 13A =
Aggravated Assault. All other codes, including 07 =
Mercy Killing, are not valid because they do not
relate to an aggravated assault.
463
INVALID AGGRAVATED
ASSAULT/HOMICIDE FOR 09C
OFFENSE
When a Justifiable Homicide is reported, Data
Element 31 (Aggravated Assault/Homicide
Circumstances) can only have codes of
20 = Criminal Killed by Private Citizen or
21 = Criminal Killed by Police Officer. In this case,
a code other than the two mentioned was entered.
464
ENTRY FOR TYPE OF VICTIM
MUST BE “I” WHEN THIS
OFFENSE CODE IS ENTERED
(Type of Victim) Must have a value of I = Individual
or L = Law Enforcement Officer when Data
Element 24 (Victim Connected to UCR Offense
Code) contains a Crime Against Person.
462
06/15/2020
2019.2.1 NIBRS Technical Specification
165
Victim Segment Errors
Error
Number
Error Message
Error Description
ENTRY FOR TYPE OF VICTIM
MUST BE “S” WHEN THIS
OFFENSE CODE IS ENTERED
(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*
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
466
OFFENSE MUST BE SUBMITTED
AS LEVEL 2 RECORD IF VICTIM
IS CONNECTED
Each UCR Offense Code entered into Data
Element 24 (Victim Connected to UCR Offense
Code) must have the Offense Segment for the
value. In 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.
467
ENTRY FOR TYPE OF VICTIM
CANNOT BE S WHEN THIS
OFFENSE CODE IS ENTERED
(Type of Victim) cannot have a value of S =
Society/Public when Data Element 24 (Victim
Connected to UCR Offense Code) contains a
Crime Against Property.
468
RELATIONSHIP CANNOT BE
ENTERED WHEN RELATED TO
OFFENDER NUMBER 00
Data Element 35 (Relationship of Victim to
Offender) cannot be entered when Data Element
34 (Offender Number to be Related) is zero. Zero
means that the number of offenders is unknown;
therefore, the relationship cannot be entered.
469
VICTIM SEX MUST BE M OR F
FOR AN 11A OR 36B OFFENSE
Data Element 27 (Sex of Victim) must be M = Male
or F = Female to be connected to offense codes of
11A = Rape and 36B = Statutory Rape.
WHEN VO RELATIONSHIP IS
PRESENT, MUST HAVE TWO OR
MORE VICTIMS AND
OFFENDERS
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 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. However, there may be some situations
where only one of the victims is also the offender,
but where the other victim(s) is not also the
offender(s).
465
470
06/15/2020
2019.2.1 NIBRS Technical Specification
166
Victim Segment Errors
Error
Number
Error Message
Error Description
471
ONLY ONE VO RELATIONSHIP
PER VICTIM
Data Element 35 (Relationship of Victim to
Offenders) has relationships of VO = Victim Was
Offender that point to multiple offenders, which is
an impossible situation. A single victim cannot be
two offenders.
472
WHEN OFFENDER
AGE/SEX/RACE ARE UNKNOWN,
RELATIONSHIP MUST BE
RU=UNKNOWN
If Data Element 37 (Age of Offender) is
00 = Unknown, Data Element 38 (Sex of Offender)
is U = Unknown, and Data Element 39 (Race of
Offender) is U = Unknown, then Data Element 35
(Relationship of Victim to Offender) must be
RU = Relationship Unknown.
474
ONLY ONE VO RELATIONSHIP
CAN BE ASSIGNED TO A
SPECIFIC OFFENDER
Segment Level 4 (Victim Segment) cannot be
submitted multiple times with VO = Victim Was
Offender in Data Element 35 (Relationship of
Victim to Offender) when Data Element 34
(Offender Number to be Related) contains the
same data value (indicating the same offender).
475
ONLY ONE SE RELATIONSHIP
PER VICTIM
A victim can only have one spousal relationship. In
this instance, the victim has a relationship of
SE = Spouse to two or more offenders.
476
ONLY ONE SE RELATIONSHIP
CAN BE ASSIGNED TO A
SPECIFIC OFFENDER
An offender can only have one spousal
relationship. In this instance, two or more victims
have a relationship of SE = Spouse to the same
offender.
477
INVALID AGGRAVATED
ASSAULT/HOMICIDE
CIRCUMSTANCES FOR
CONNECTED OFFENSE
A victim segment was submitted with Data Element
24 (Victim Connected to UCR Offense Code)
having an offense that does not have a permitted
code for Data Element 31 (Aggravated
Assault/Homicide Circumstances).
06/15/2020
2019.2.1 NIBRS Technical Specification
167
Victim Segment Errors
Error
Number
Error Message
Error Description
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 mxclusive
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.
478
VICTIM CONNECTED TO AN
INVALID COMBINATION OF
OFFENSES
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, 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.
06/15/2020
2019.2.1 NIBRS Technical Specification
168
Victim Segment Errors
Error
Number
Error Message
Error Description
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.
479
06/15/2020
SIMPLE ASSAULT(13B) CANNOT
HAVE MAJOR INJURIES
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). Either
the offense should have been classified as an
13A = Aggravated Assault or the victim’s injury
should not have been entered as major.
2019.2.1 NIBRS Technical Specification
169
Victim Segment Errors
Error
Number
Error Message
Error Description
480
WHEN ASSAULT/HOMICIDE (31)
IS 08, INCIDENT MUST HAVE
TWO OR MORE OFFENSES
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 Data Element 6 (UCR Offense
Code) should have been submitted, or multiple
individual victims should have been submitted for
the incident report.
481
VICTIM'S AGE IS 18 OR OVER
FOR STATUTORY RAPE
OFFENSE
Data Element 26 (Age of Victim) should be under
18 when Data Element 24 (Victim Connected to
UCR Offense Code) is 36B = Statutory Rape.
482
483
484
LEOKA VICTIM MUST BE
CONNECTED TO MURDER OR
ASSAULT OFFENSE
VICTIM MUST BE LAW
ENFORCEMENT OFFICER TO
ENTER LEOKA DATA
THIS VICTIM SEGMENT HAS A
CONFLICTING LENGTH
Data Element 25 (Type of Victim) cannot be
L = Law Enforcement Officer unless Data Element
24 (Victim Connected to UCR Offense Code) is
one of the following:
09A = Murder & Nonnegligent Manslaughter
13A = Aggravated Assault
13B = Simple Assault
13C = Intimidation
Data Element 25A (Type of Officer Activity/
Circumstance), Data Element 25B (Officer
Assignment Type), Data Element 25C (Officer–ORI
Other Jurisdiction), may be entered only when
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
Segments within that ORI must be formatted using
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
06/15/2020
OFFENDER NUMBER TO BE
RELATED CANNOT BE “00” FOR
THIS OFFENSE
(Offender Number to be Related) cannot be 00 =
Unknown when Data Element 24 (Victim
Connected to UCR Offense Code) is 360 = Failure
to Register as a Sex Offender*.
*Denotes offenses for federal and tribal LEA
reporting only
2019.2.1 NIBRS Technical Specification
170
Victim Segment Errors
Error
Number
490
Error Message
INCIDENT DATE/HOUR MUST
CONTAIN A VALID ENTRY WHEN
VICTIM IS L = LAW
ENFORCEMENT OFFICER
Error Description
(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
13A = Aggravated Assault
13B = Simple Assault
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
171
13B Simple Assault
X
X
X
X
X
13C - Intimidation
X
X
X
X
X
240 - Motor Vehicle Theft
23H - All Other Larceny
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
23A - Pocket-picking
X
23B - Purse-snatching
X
23C - Shoplifting
X
23D - Theft From Building
X
23E - Theft From Coin Machine
X
23F - Theft From Motor Vehicle
X
23G - Theft of Motor Vehicle Part
X
23H - All Other Larceny
X
240 - Motor Vehicle Theft
X
36A - Incest
X
X
X
X
36B - Statutory Rape
X
X
X
X
06/15/2020
23G - Theft of Motor Vehicle Part
X
120 - Robbery
X
23F - Theft From Motor Vehicle
X
X
X
23E - Theft From Coin Machine
X
X
X
23D - Theft From Building
X
23C - Shoplifting
X
X
X
23B - Purse-snatching
X
X
23A - Pocket-picking
X
X
X
X
13C - Intimidation
X
X
13A - Aggravated Assault
X
X
X
11C - Sexual Assault w/Object
11D - Fondling
X
36B - Statutory Rape
X
11B - Sodomy
X
36A - Incest
X
13B - Simple Assault
X
13A - Aggravated Assault
X
11A - Rape
120 - Robbery
09B - Negligent Manslaughter
11D - Fondling
X
11C - Sexual Assault w/Object
X
11B - Sodomy
09B - Negligent Manslaughter
09A - Murder
11A - Rape
09A - Murder
09C Justifiable Homicide cannot
occur with any other offense
Table 5-7 Mutually Exclusive Offenses for Error Code 478 Chart
2019.2.1 NIBRS Technical Specification
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
172
5.2.6 Offender Segment Errors
Table 5-8 Offender Segment Errors
Offender Segment Errors
Error
Number
Error Message
Error Description
501
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element is
mandatory or when the conditions are met for data
that must be entered into a conditionally mandatory
field.
502
CONTAINS NONNUMERIC ENTRY
Data Element 36 (Offender Sequence Number)
must contain numeric entry (00 through 99) with
zero left-fill.
504
INVALID DATA VALUE
The referenced data element must contain a valid
data value when it is entered; blank is permissible
on nonmandatory fields.
508
EXACT AGE MUST BE IN FIRST
TWO POSITIONS
Data Element 37 (Age of Offender) contains data
but is not left-justified. A single two-character age
must be in positions 1 through 2 of the field.
509
CONTAINS NONNUMERIC ENTRY
Data Element 37 (Age of Offender) contains more
than two characters indicating a possible agerange is being attempted. If so, the field must
contain a numeric entry of four digits.
510
FIRST AGE MUST BE LESS THAN
SECOND FOR AGE RANGE
Data Element 37 (Age of Offender) was entered as
an age-range. Accordingly, the first age component
must be less than the second age.
515
CANNOT HAVE EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON-BLANK CHARACTERS
Must be blank right-fill if under 12 characters in
length. Cannot have embedded blanks between
the first and last characters entered.
516
MUST BE LEFT-JUSTIFIED–
BLANK DETECTED IN FIRST
POSITION
Must be left-justified with blank right-fill if under 12
characters in length.
Must contain a valid character combination of the
following:
517
CANNOT HAVE CHARACTERS
OTHER THAN A–Z, 0–9, AND/OR
HYPHEN, AND/OR BLANKS
522
AGE RANGE CANNOT HAVE “00”
IN FIRST TWO POSITIONS
Data Element 37 (Age of Offender) was entered as
an age-range. Therefore, the first age component
cannot be 00 = Unknown.
550
OFFENDER IS SPOUSE, BUT
AGE IS LESS THAN 13
Data Element 37 (age of Offender) cannot be less
than 13 years old when Data Element 35
(Relationship of Victim to Offender) contains a
relationship of SE = Spouse.
06/15/2020
• A–Z (capital letters only)
• 0–9
• Hyphen
Example: 11-123-SC is valid, but 11+123*SC is not
valid.
2019.2.1 NIBRS Technical Specification
173
Offender Segment Errors
Error
Number
Error Message
Error Description
551
DUPLICATE OFFENDER
SEGMENT
When a Group A Incident Report is submitted, the
individual segments comprising the incident cannot
contain duplicates. In this case, two Offender
Segments were submitted having the same entry in
Data Element 36 (Offender Sequence Number).
552
CANNOT BE PRESENT WHEN
OFFENDER NUMBER IS “00”
UNKNOWN
Data Element 37 (Age of Offender) cannot be
entered when Data Element 36 (Offender
Sequence Number) is 00 = Unknown.
AGE OF VICTIM AND OFFENDER
DOES NOT REFLECT THE
RELATIONSHIP
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 must be greater than the offender’s age. The
following relationships must 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)
555
OFFENDER “00” EXISTS-CANNOT
SUBMIT MORE OFFENDERS
When multiple Offender Segments are submitted,
none can contain a 00 = Unknown value because
the presence of 00 indicates that the number of
offenders is unknown. In this case, multiple
offenders were submitted, but one of the segments
contains the 00 = Unknown value.
556
OFFENDER AGE MUST BE
NUMERIC DIGITS
Data Element 37 (Age of Offender) must contain
numeric entry of 00 through 99.
OFFENDER SEQUENCE NUMBER
CANNOT BE UNKNOWN IF
INCIDENT CLEARED
EXCEPTIONALLY
Data Element 36 (Offender Sequence Number)
contains 00 indicating that nothing is known about
the offender(s) regarding number and any
identifying information. To exceptionally clear the
incident, the value cannot be 00. The incident was
submitted with Data Element 4 (Cleared
Exceptionally) having a value of A through E.
AT LEAST ONE OFFENDER
MUST HAVE KNOWN VALUES
None of the Offender Segments contain all known
values for age, sex, and race. When an incident is
cleared exceptionally (Data Element 4 contains an
A through E), one offender must have all known
values.
557
558
06/15/2020
2019.2.1 NIBRS Technical Specification
174
Offender Segment Errors
Error
Number
559
560
584
Error Message
Error Description
OFFENDER DATA MUST BE
PRESENT IF OFFENSE CODE IS
09C = JUSTIFIABLE HOMICIDE
OR 360 = FAILURE TO REGISTER
AS A SEX OFFENDER*
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 for age, sex, and
race.
*Denotes offenses for federal and tribal LEA
reporting only
VICTIM’S SEX CANNOT BE SAME
FOR ALL OFFENDERS FOR
OFFENSES OF RAPE
Segment Level 5 (Offender Segment) must contain
a data value for at least one offender in Data
Element 38 (Sex of Offender) that is not the same
sex that is entered in Data Element 27 (Sex of
Victim) when Data Element 6 (UCR Offense Code)
is 11A = Rape. The offender must be connected to
the victim in Data Element 34 (Offender Number to
be Related) unless offender number in Data
Element 34 (Offender Number to be Related) is
00 = Unknown
THIS OFFENDER SEGMENT HAS
A CONFLICTING LENGTH
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
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
Number
Error Message
Error Description
601
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an Incident must
contain data when the referenced data element is
mandatory or when the conditions are met for
data that must be entered into a conditionally
mandatory field.
602
CONTAINS NONNUMERIC ENTRY
(Arrestee Sequence Number) must be numeric
entry of 01 to 99 with zero left-fill.
604
INVALID DATA VALUE
The referenced data element must contain a valid
data value when it is entered; blank is permissible
on nonmandatory fields.
06/15/2020
2019.2.1 NIBRS Technical Specification
175
Arrestee Segment Errors
Error
Number
605
Error Message
INVALID ARREST DATE
Error Description
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.
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.
606
ERROR-DUPLICATE VALUE =
[value]
Data Element 46 (Arrestee Was Armed With) 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.
607
ERROR-MUTUALLY EXCLUSIVE
VALUE = [value]
Data Element 46 (Arrestee Was Armed With) can
have multiple data values and was entered with
multiple values. However, 01 = Unarmed cannot
be entered with any other data value.
608
EXACT AGE MUST BE IN FIRST
TWO POSITIONS
Data Element 47 (Age of Arrestee) contains data,
but is not left-justified. A single two-character age
must be in positions 1 through 2 of the field.
609
CONTAINS NONNUMERIC ENTRY
Data Element 47 (Age of Arrestee) contains more
than two characters indicating a possible agerange is being attempted. If so, the field must
contain a numeric entry of four digits.
610
FIRST AGE MUST BE LESS THAN
SECOND FOR AGE RANGE
Data Element 47 (Age of Arrestee) was entered
as an age-range. Accordingly, the first age
component must be less than the second age.
615
CANNOT HAVE EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON-BLANK CHARACTERS
Must be blank right-fill if under 12 characters in
length. Cannot have embedded blanks between
the first and last characters entered.
616
MUST BE LEFT-JUSTIFIEDBLANK DETECTED IN FIRST
POSITION
Data Element 2 (Incident Number) and Data
Element 41 (Arrest Transaction Number) must be
left justified with blank right-fill when less than 12
characters in length.
Data Element 2 (Incident Number) Must contain a
valid character combination of the following:
617
CANNOT HAVE CHARACTERS
OTHER THAN A-Z, 0-9,
HYPHENS, AND/OR BLANKS
•
•
•
A–Z (capital letters only)
0–9
Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
06/15/2020
2019.2.1 NIBRS Technical Specification
176
Arrestee Segment Errors
Error
Number
Error Message
Error Description
618
ARREST DATE CANNOT BE ON
OR AFTER THE INACTIVE DATE
OF THE ORI
Data Element 42 (Arrest Date) The UCR Program
has determined that an ORI will no longer be
submitting data to the FBI as of an inactive date.
The FBI will not accept arrest data from this ORI
after this date.
622
AGE RANGE CANNOT HAVE “00”
IN FIRST TWO POSITIONS
Data Element 47 (Age of Arrestee) was entered
as an age-range. Therefore, the first age
component cannot be 00 = Unknown.
650
ARREST OFFENSE CODE CAN
ONLY BE USED BY FEDERAL
AND TRIBALAGENCIES
(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*
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*
*Denotes offenses for federal and tribal LEA
reporting only
652
DISPOSITION MUST BE
ENTERED WHEN AGE IS LESS
THAN 18
Data Element 52 (Disposition of Arrestee Under
18) was not entered, but Data Element 47 (Age of
Arrestee) is under 18. Whenever an arrestee’s
age indicates a juvenile, the agency must enter
the disposition..
653
FOR AGE GREATER THAN 17
DISPOSITION SHOULD NOT BE
ENTERED
Data Element 52 (Disposition of Arrestee Under
18) was entered, but Data Element 47 (Age of
Arrestee) is 18 or greater. Whenever an arrestee’s
age indicates an adult, the agency cannot enter
the juvenile disposition because it does not apply.
654
AUTOMATIC INDICATOR MUST
BE BLANK OR “A”
Data Element 46 (Arrestee Was Armed With)
does not have A = Automatic or a blank in the
third position of field.
06/15/2020
2019.2.1 NIBRS Technical Specification
177
Arrestee Segment Errors
Error
Number
Error Message
Error Description
In Data Element 46 (Arrestee Was Armed With), A
= Automatic is the third character of code. It is
valid only with codes:
655
656
WEAPON TYPE MUST = 11, 12,
13, 14, OR 15 FOR AN “A” IN THE
AUTO INDICATOR
THIS ARRESTEE EXCEEDED THE
NUMBER OF OFFENDERS ON
THE GROUP A INCIDENT
11 = Firearm (Type Not Stated)
12 = Handgun
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.
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.
The exception to this rule is when an additional
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.
661
ARRESTEE SEQUENCE NUMBER
ALREADY EXISTS
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
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
(Arrest Transaction) is unique for each arrestee
submitted to ensure that duplication does not
occur.
664
ARRESTEE AGE MUST BE
NUMERIC DIGITS
Data Element 47 (Age of Arrestee) does not
contain a numeric entry of 00 through 99 for an
exact age.
06/15/2020
2019.2.1 NIBRS Technical Specification
178
Arrestee Segment Errors
Error
Number
Error Message
Error Description
Data Element 42 (Arrest Date) cannot be earlier
than Data Element 3 (Incident Date/Hour). A
person cannot be arrested before the incident
occurred.
665
ARREST DATE CANNOT BE
BEFORE THE INCIDENT START
DATE
The exception to this rule is when an additional
arrest is reported for a pre-NIBRS incident. In this
case, Segment Level 6 (Arrestee 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.
INVALID ARRESTEE SEX VALUE
Data Element 48 (Sex of Arrestee) does not
contain a valid code of M = Male or F = Female.
Note: U = Unknown (if entered) is not a valid sex
for an arrestee.
669
NO ARRESTEE RECORDS
ALLOWED FOR A JUSTIFIABLE
HOMICIDE
Group A Incident Reports cannot have arrests
when Data Element 6 (UCR Offense Code) is
09C = Justifiable Homicide. By definition a
justifiable homicide never involves an arrest of the
offender (the person who committed the justifiable
homicide).
670
JUSTIFIABLE HOMICIDE CANNOT
BE AN ARREST OFFENSE CODE
Data Element 45 (UCR Arrest Offense Code) was
entered with 09C = Justifiable Homicide. This is
not a valid arrest offense.
667
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
Number
Error Message
Error Description
701
MUST BE PRESENT—
MANDATORY FIELD
The referenced data element in an incident must
contain data when the referenced data element
is mandatory or when the conditions are met for
data that must be entered into a conditionally
mandatory field.
702
CONTAINS NONNUMERIC ENTRY
Data Element 40 (Arrestee Sequence Number)
must be numeric entry of 01 to 99 with zero leftfill.
704
INVALID DATA VALUE
The referenced data element must contain a
valid data value when it is entered; blank is
permissible on nonmandatory fields.
INVALID ARREST DATE
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).
705
06/15/2020
2019.2.1 NIBRS Technical Specification
179
Group B Arrest Report Segment Errors
Error
Number
Error Message
Error Description
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.
706
ERROR-DUPLICATE VALUE =
[value]
Data Element 46 (Arrestee Was Armed With)
cannot contain duplicate data values although
more than one data value is allowed.
707
ERROR-MUTUALLY EXCLUSIVE
VALUE = [value]
Data Element 46 (Arrestee Was Armed With) can
have multiple data values and was entered with
multiple values. However, 01 = Unarmed cannot
be entered with any other data value.
708
EXACT AGE MUST BE IN FIRST
TWO POSITIONS
Data Element 47 (Age of Arrestee) contains data,
but is not left-justified. A single two-character age
must be in positions 1 through 2 of the field.
709
CONTAINS NONNUMERIC ENTRY
Data Element 47 (Age of Arrestee) contains
more than two characters indicating a possible
age-range is being attempted. If so, the field
must contain numeric entry of four digits.
710
FIRST AGE MUST BE LESS THAN
SECOND FOR AGE RANGE
Data Element 47 (Age of Arrestee) was entered
as an age-range. Accordingly, the first age
component must be less than the second age.
715
CANNOT HAVE EMBEDDED
BLANKS BETWEEN FIRST AND
LAST NON-BLANK CHARACTERS
Must be blank right-fill if under 12 characters in
length. Cannot have embedded blanks between
the first and last characters entered.
716
MUST BE LEFT-JUSTIFIED–
BLANK DETECTED IN FIRST
POSITION
Must be left-justified with blank right-fill if under
12 characters in length.
Must contain a valid character combination of the
following:
717
CANNOT HAVE CHARACTERS
OTHER THAN A-Z, 0-9, AND/OR
HYPHENS, AND/OR BLANKS
•
•
•
A–Z (capital letters only)
0–9
Hyphen
Example: 11-123-SC is valid, but 11+123*SC is
not valid.
718
ARREST DATE CANNOT BE ON
OR AFTER THE INACTIVE DATE
OF THE ORI
Data Element 42 (Arrest Date) The UCR
Program has determined that an ORI will no
longer be submitting data to the FBI as of an
inactive date. The FBI will not accept arrest data
from this ORI after this date.
720
GROUP B ADD CANNOT
PREDATE NIBRS START DATE
Group B Arrest Report (Level 7) submitted with a
Segment Action Type of A = Add cannot have
06/15/2020
2019.2.1 NIBRS Technical Specification
180
Group B Arrest Report Segment Errors
Error
Number
Error Message
722
AGE RANGE CANNOT HAVE “00”
IN FIRST TWO POSITIONS
Data Element 47 (Age of Arrestee) was entered
as an age-range. Therefore, the first age
component cannot be 00 = Unknown.
ARREST OFFENSE CODE CAN
ONLY BE USED BY FEDERAL
AND TRIBAL AGENCIES
(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
49A = Harboring Escapee/Concealing from
Arrest
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
750
751
06/15/2020
Error Description
Data Element 42 (Arrest Date) earlier than the
Base Date.
ARRESTEE SEQUENCE NUMBER
ALREADY EXISTS
(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 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.
2019.2.1 NIBRS Technical Specification
181
Group B Arrest Report Segment Errors
Error
Number
Error Message
Error Description
752
DISPOSITION MUST BE
ENTERED WHEN AGE IS LESS
THAN 18
Data Element 52 (Disposition of Juvenile) was
not entered, but Data Element 47 (Age of
Arrestee) is under 18. Whenever an arrestee’s
age indicates a juvenile, the agency must enter a
disposition.
753
FOR AGE GREATER THAN 17
DISPOSITION SHOULD NOT BE
ENTERED
Data Element 52 (Disposition of Juvenile) was
entered, but Data Element 47 (Age of Arrestee)
is 18 or greater. Whenever an arrestee’s age
indicates an adult, the agency cannot enter the
juvenile disposition because it does not apply.
754
AUTOMATIC INDICATOR MUST
BE BLANK OR “A”
Data Element 46 (Arrestee Was Armed With)
does not have A = Automatic or a blank in the
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)
12 = Handgun
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.
755
WEAPON TYPE MUST = 11, 12,
13, 14, OR 15 FOR AN “A” IN THE
AUTO INDICATOR
757
ARRESTEE AGE MUST BE
NUMERIC DIGITS
Data Element 47 (Age of Arrestee) does not
contain a numeric entry of 00 through 99 for an
exact age.
INVALID ARRESTEE SEX VALUE
Data Element 48 (Sex of Arrestee) does not
contain a valid code of M = Male or F = Female.
Note: that U = Unknown (if entered) is not a valid
sex for an arrestee.
759
DUPLICATE GROUP B ARREST
REPORT SEGMENT ON FILE
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
Data Element 40 (Arrestee Sequence Number) is
unique for each Arrestee Segment submitted so
that duplication does not occur.
760
LEVEL 7 ARRESTS MUST HAVE A
GROUP B OFFENSE
Group B Arrest Reports (Level 7) must contain a
Group B Offense Code in Data Element 45 (UCR
Arrest Offense). The offense code submitted is
not a Group B offense code.
797
MISSING ARREST DATE FOR
DELETE OF GROUP B ARREST
Data Element 42 (Arrest Date) is missing for a
Group B Arrest Report with a Segment Action
Type of D = Delete; must be populated with a
valid data value and cannot be blank.
798
MISSING ARREST DATE FOR
DELETE - ARREST
Data Element 42 (Arrest Date) is missing for a
Group B Arrest Report with a Segment Action
758
06/15/2020
2019.2.1 NIBRS Technical Specification
182
Group B Arrest Report Segment Errors
Error
Number
799
Error Message
Error Description
TRANSACTION NUMBER
MATCHES GROUP B ARREST
REPORT WITH ARREST DATE
OUTSIDE TWO YEAR WINDOW
Type of D = Delete; at least one Group B Arrest
Report is on file that matches Data Element 41
(Arrest Transaction Number) with an Arrest Date
outside the two year window.
MISSING ARREST DATE FOR
DELETE-ARREST TRANSACTION
NUMBER MATCHES MULTIPLE
GROUP B ARREST REPORTS
Data Element 42 (Arrest Date) is missing for a
Group B Arrest Report with a Segment Action
Type of D = Delete; multiple Group B Arrest
Reports are on file that match Data Element 41
(Arrest Transaction Number).
5.2.9 Zero Report Segment Errors
Error
Number
Table 5-11 Zero Report Segment Errors
Error Message
Error Description
001
MUST BE POPULATED WITH A
VALID DATA VALUEMANDATORY FIELD
Mandatory Data Elements (Mandatory = Yes)
must be populated with a valid data value and
cannot be blank.
028
CANNOT ADD ZERO REPORT GROUP A INCIDENT ON FILE
FOR THIS MONTH
An agency cannot submit a Zero Report segment
when a Group A Incident Report is already on file
for the month/year.
029
CANNOT ADD ZERO REPORTGROUP B ARREST REPORT ON
FILE FOR THIS MONTH
An agency cannot submit a Zero Report segment
when a Group B Arrest Report is already on file for
the month/year.
030
CANNOT DELETE ZERO REPORT
- GROUP A INCIDENT ON FILE
FOR THIS MONTH
An agency cannot delete a Zero Report when a
Group A Incident was already on file for the
month.
031
CANNOT DELETE ZERO REPORT
- GROUP B INCIDENT ON FILE
FOR THIS MONTH
An agency cannot delete a Zero Report when a
Group B Incident was already on file for the
month.
090
ZERO REPORT MONTH IS NOT
01–12
Zero Report Month must be a valid month, data
values 01 through 12.
091
ZERO-REPORTING YEAR IS
INVALID
A Segment Level 0 was submitted that did not
have four numeric digits in positions 40 through
43.
092
ZERO REPORT INCIDENT
NUMBER MUST BE ALL ZEROS
Data Element 2 (Incident Number) in the Zero
Report Segment (Level 0) must contain 12 zeros.
093
ZERO REPORT MONTH/YEAR IS
PRIOR TO AGENCY
CONVERSION TO THE NIBRS
Zero Report Month and Zero Report Year cannot
precede the month and year in the date the LEA
converted to NIBRS.
094
ZERO REPORT MONTH/YEAR
EXCEEDED MONTH/YEAR OF
SUBMISSION
A Segment Level 0 was submitted with a month
and year entered into positions 38 through 43 that
was later than the Month of Electronic submission
and Year of Electronic submission entered into
positions 7 through 12.
06/15/2020
2019.2.1 NIBRS Technical Specification
183
Error
Number
096
Error Message
ZERO REPORT MONTH & ZERO
REPORT YEAR CANNOT BE ON
OR AFTER DATE AGENCY IS
PLACED ON COVERED-BY
STATUS
Error Description
The combined Zero Report Month and Zero
Report Year cannot be on or after the date a 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 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.
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.
06/15/2020
2019.2.1 NIBRS Technical Specification
184
Warning
Number
Warning Message
Description
1197
DELETED MULTIPLE
INCIDENTS
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
replacement incident was submitted on the current
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.
1198
INCIDENT DATE IN DELETE
DOES NOT MATCH INCIDENT
DATE ON FILE
Delete record was submitted with an incident date
that does not match the incident date on the
previously submitted incident that resides in our
database.
1201
WARNING - BURGLARY
INCIDENTS WITH LOCATION
14/19 AND 14/19/99
PREMISES ENTERED
The burglary incident referenced has a Data
Element 9 (Location Type) of 14 = Hotel/Motel Etc.
or 19 = Rental Storage Facility and 99 in Data
Element 10 (Number of Premises Entered). Please
verify the location and/or number of premises
entered is correct.
WARNING - HOMICIDE OR
MANSLAUGHTER INCIDENTS
WITH “VEHICLE” WEAPON
TYPE
Homicides and Negligent Manslaughters are being
reported which occurred with a motor vehicle in
Data Element 13 (Type Weapon/Force Involved).
The offenses of Homicide and Negligent
Manslaughter does not include accidental traffic
fatalities. Negligent Homicide offenses using a
vehicle/vessel are valid in fatalities involving
driving under the influence, cell/smart phone use,
or reckless driving incidents.
WARNING - WEAPONS LAW
OFFENSES WITH PERSONAL
WEAPONS
Data Value 40 = Personal Weapons and/or
99 = None are being reported in Data Element 13
(Type Weapon/Force Involved). These weapon
types do not meet the criteria for this offense.
Weapon Law Violations are defined as the
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.
1204
WARNING - ROBBERY
INCIDENTS WITH NO
INDIVIDUAL VICTIM
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
those persons and other entities (businesses,
financial institutions, etc.) from whom property was
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.
1209
WARNING - OFFENSE
CONTAINS AUTOMATIC
WEAPONS
The offense has Data Element 13 (Type
Weapon/Force Involved) with a weapon indicator
of A = Automatic, e.g., 13A = Automatic Rifle. An
automatic firearm is defined as any firearm which
shoots, or is designed to shoot, more than one
1202
1203
06/15/2020
2019.2.1 NIBRS Technical Specification
185
shot at a time by a single pull of the trigger without
manual reloading. Please verify the weapon was
an automatic firearm.
1220
WARNING - INCIDENT
REPORTED WITH BIAS CODE
99 OR UNKNOWN
Data Element 8A (Bias Motivation) indicates a
Bias code 99 = Unknown and indicates a
suspected Hate Crime bias and should be
resubmitted after investigation, either as
88 = None (no bias), or the appropriate bias code.
1221
WARNING - INCIDENT
REPORTED WITH MULTIPLE
BIAS CODES
Data Element 8A (Bias Motivation) was entered
with multiple bias codes (up to 5). Please verify
that the multiple bias codes are correct as
reported.
1222
WARNING - INCIDENT
CONTAINS AN OFFENSE OF
MURDER AND
NONNEGLIGENT
MANSLAUGHTER
ASSOCIATED WITH HATE
CRIME
1223
WARNING - INCIDENT
REPORTED WITH OFFENSE
RAPE ASSOCIATED WITH
HATE CRIME
Data Element 6 (UCR Offense Code)
11A = Rape with a valid bias code(s) in Data
Element 8A (Bias Motivation) other than 88 =
None (no bias). Please verify that the incident is
correct as reported.
1224
WARNING - INCIDENT
REPORTED WITH OFFENSE
SODOMY ASSOCIATED WITH
HATE CRIME
Data Element 6 (UCR Offense Code)
11B = Sodomy with a valid bias code(s) in Data
Element 8A (Bias Motivation) other than
88 = None (no bias). Please verify that the incident
is correct as reported.
1225
WARNING - INCIDENT
REPORTED WITH OFFENSE
SEXUAL ASSAULT WITH AN
OBJECT ASSOCIATED WITH
HATE CRIME
Data Element 6 (UCR Offense Code)
11C = Sexual Assault With An Object with a valid
bias code(s) in Data Element 8A (Bias Motivation)
other than 88 = None (no bias). Please verify that
the incident is correct as reported.
1226
WARNING - INCIDENT
REPORTED WITH MULTIPLE
OFFENSE SEGMENTS
ASSOCIATED WITH A HATE
CRIME
Data Element 6 (UCR Offense Code) has multiple
offense segments associated with Data Element
8A (Bias Motivation) other than 88 = None (no
bias). Please verify that the incident is correct as
reported.
WARNING - ARSON
PROPERTY TYPE 77 “OTHER”
WITH HIGH DOLLAR VALUES
- 10,000
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
incidents contained large dollar values. When
utilizing property description 77 = Other up to ten
property descriptions can be entered for each
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
1302
06/15/2020
Data Element 6 (UCR Offense Code)
09A = Murder and Nonnegligent Manslaughter
with a valid bias code(s) in Data Element 8A (Bias
Motivation) other than 88 = None (no bias).
Please verify that the incident is correct as
reported.
2019.2.1 NIBRS Technical Specification
186
property should be combined and entered as
77 = Other.
1303
1304
1305
06/15/2020
WARNING - LARCENY WITH
BURGLARY
The incidents of Burglary also contain a larcenytheft. Offenses locally known as burglary (any
degree); unlawful entry with intent to commit a
larceny or felony; breaking and entering with intent
to commit a larceny; housebreaking; and
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.
WARNING - LARCENY THEFT
- AIRCRAFT
In Data Element 15 (Property Description) the
stolen property being reported is 01 = Aircraft. It is
uncommon in an offense of larceny-theft to contain
an aircraft as the stolen property in the property
description.
WARNING - LARCENY THEFT
- COIN OPERATED MACHINE
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
33 = Structures-public/community
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
2019.2.1 NIBRS Technical Specification
187
WARNING - LARCENY THEFT
- STOLEN STRUCTURES
Incidents of larceny-theft with Commercial/
Business, Single Occupancy Dwellings, Other
Dwellings, Industrial/Manufacturing, and
Public/Community are reported as stolen property
in Data Element 15 (Property Description). It is
uncommon for an offense of larceny-theft to
contain a structure as the stolen property.
1307
WARNING - SPECIAL
PROPERTY CODE - 99
Stolen property 99 = Blank is being reported in
Data Element 15 (Property Description);
99 = Blank is a special data value which will
capture statistics on certain theft fads, i.e., pet
rocks, if necessary. The FBI does not currently use
this code.
1308
WARNING - MOTOR VEHICLE
THEFT INCIDENTS WITH
GREATER THAN 5 VEHICLES
STOLEN
1310
WARNING - CREDIT
CARD/AUTOMATIC TELLER
MACHINE FRAUD
Data Element 15 (Property Description)
09 = Credit/Debit Cards are being reported stolen.
The fraudulent use of the credit/debit card should
be reported, and not the theft of the card.
WARNING - LARCENY-THEFT
23F AND 23G RADIOS/TVs/VCRs
There are a number of entries for Property
Description (Data Element 15) 26 = Radios/TVs/
VCRs being reported. The 23F = Theft From Motor
Vehicle is the theft of articles from a motor vehicle
and the 23G = Theft of Motor Vehicle Parts and
Accessories is the theft of any part or accessory
affixed to the interior or exterior of a motor vehicle
necessary for its operation.
WARNING - DRUG
EQUIPMENT VIOLATIONS
Data Element 12 (Type Criminal Activity) is
reported as P = Possessing/Concealing with Data
Element 14 (Type Property Loss) 1 = None.
Typically with this Type of Criminal Activity, the
Type of Property Loss is 5 = Recovered or
6 = Seized.
WARNING - DRUG QUANTITY
MEASUREMENTS OF
DOSAGE UNIT
Data Element 22 (Type Drug Measurement)
DU = Dosage Unit is being used for crack,
cocaine, and marijuana. Usually a weight
measurement like GM = Gram, KG = Kilogram,
OZ = Ounce, or LB = Pound is used. The
NP = Number of Plants is sometimes used for
marijuana.
WARNING - PROPERTY DESC
(15) HAD VALUE (16) THAT
EXCEEDED THRESHOLD OF
$1,000,000
When Data Element 15 (Property Description)
contains a value that exceeds an FBI-assigned
threshold amount, a warning message will be
created. The participant is asked to check to see if
the value entered was a data entry error, or if it
was intended to be entered. A warning message is
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,
1306
1312
1314
1316
1342
06/15/2020
Data Element 18 (Number of Motor Vehicles
Stolen) is greater than five. Please verify the
number of vehicles stolen.
2019.2.1 NIBRS Technical Specification
188
the FBI will generate a warning message. In this
case, the cents were entered as whole dollars.
1343
WARNING - 280 OFFENSE
HAS RECOVERED VEHICLE
BUT 240 DOESNT SHOW
STOLEN
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
Element 15 (Property Description) is a vehicle.
Data Element 15 (Property Description) for
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.
1350
WARNING - CONTAINS NONNUMERIC ENTRY - MUST BE
ZERO LEFT FILL
Contains nonnumeric entry; must be zero left fill.
1401
WARNING - INCEST
WITHOUT FAMILY
RELATIONSHIP
Data Element 35 (Relationship of Victim to
Offender) is nonfamily. Incest is the sexual
intercourse between persons who are related to
each other within the degrees wherein marriage is
prohibited by law. Because the relationship is
nonfamily, the agency should classify the offense
as a Statutory Rape and/or Rape.
1402
WARNING - STATUTORY
RAPE WITH VICTIMS UNDER
AGE 13
Statutory rape is the sexual intercourse with a
person who is under the statutory age of consent.
Based upon Data Element 26 (Age of Victim), the
FBI is questioning if the child is capable of giving
consent.
1403
WARNING - STATUTORY
RAPE WITH VICTIM AS
FAMILY MEMBER
1404
WARNING - AGGRAVATED
ASSAULT WITH MINOR OR
NO INJURY AND PERSONAL
OR NO WEAPONS
06/15/2020
The Relationship of Data Element 35 (Victim to
Offender) is a family member. Statutory Rape is
the sexual intercourse with a person who is under
the statutory age of consent. Based upon the
definition of Statutory Rape, the agency should
classify these incidents as Incest or Rape.
Incidents are being reported in Data Element 33
(Type Injury) where the victim sustained minor or
no injuries and either personal or no weapons
were involved.
2019.2.1 NIBRS Technical Specification
189
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.
1405
WARNING - SIMPLE ASSAULT
WITH INJURY AND NO
WEAPON
Based on the definition, the agency should classify
these as Simple Assaults.
The victims sustained minor injuries, but there
were no weapons used when the assaults were
committed. At the very least, the weapon reported
should be 40 = Personal Weapons.
1407
WARNING - UKNOWN VICTIM
INFORMATION
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
information should be known. If the agency cannot
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.
1408
WARNING - PROPERTY
CRIME WITH THE ONLY
VICTIM UNDER AGE 7
Please verify Data Element 26 (Age of Victim).
The only victim is under the age of 7 and listed as
the victim of a property crime.
1409
WARNING - VICTIM IS
OFFICER OF ASSAULT OR
HOMICIDE WITHOUT VICTIM
CIRCUMSTANCE BEING
ASSAULT ON LAW
ENFORCEMENT OFFICER
If Data Element 25 (Type Victim) is L = Law
Enforcement Officer, then one of the two possible
Data Element 31 (Aggravated Assault/Homicide
Circumstances) should be 02 = Assault on Law
Enforcement Officer.
1413
WARNING - CHILD/PARENT
RELATIONSHIPS WITH
POSSIBLE AGE PROBLEMS
Data Element 35 (Relationship of Victim to
Offender) is:
CH = Child
PA = Parent
GP = Grandparent
GC = Grandchild
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.
1427
WARNING - INCIDENT
REPORTED WITH SOCIETY
AS VICTIM OF A HATE CRIME
Data Element 25 (Type of Victim) is S = Society
and Data Element 8A (Bias Motivation) is other
than 88 = None (no bias). Please verify that the
incident is correct as reported.
1441
WARNING – VICTIM HAD AGE
OVER 98
The agencies may have a reporting problem when
utilizing Data Element 26 (Age of Victim). The
06/15/2020
2019.2.1 NIBRS Technical Specification
190
agency may be misusing the age code of 99 when
the age is 00 = Unknown.
1449
WARNING - VICTIM IS
SPOUSE BUT AGE IS LESS
THAN 18
Data Element 26 (Age of Victim) cannot be 13, 14,
15, 16, or 17 when Data Element 35 (Relationship
of Victim to Offender) contains a relationship of
SE = Spouse.
1451
WARNING - VICTIM AGE
RANGE OF 01-98 AND 01-99
Data Element 26 (Age of Victim) was submitted
with an unreasonable range span from the
youngest age of 01 to the oldest age of 98 or 99.
1501
WARNING - AGE OF
OFFENDER LESS THAN 3
The agencies may have a reporting problem when
using Data Element 37 (Age of Offender). The
agency may be confusing the age code of 01 and
02 as the Victim/Offender Sequence Number.
1508
WARNING - FONDLING WITH
OFFENDERS UNDER AGE 13
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
of another person for the purpose of sexual
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.
1509
WARNING - VIOLENT CRIME
WITH OFFENDER UNDER 11
Please verify Data Element 37 (Age of Offender).
The offender is listed as under age 11 and the
offense is homicide, rape, or robbery.
1541
WARNING – OFFENDER HAD
AGE OVER 98
The agency may have a reporting problem when
using Data Element 37 (Age of Offender). The
agency may be misusing the age code of 99 when
the age is 00 = Unknown.
1549
WARNING–OFFENDER IS
SPOUSE, BUT AGE IS LESS
THAN 18
Data Element 37 (Age of Offender) cannot be 13,
14, 15, 16, or 17 when Data Element 35
(Relationship of Victim to Offender) contains a
relationship of SE = Spouse.
1551
WARNING - OFFENDER AGE
RANGE OF 01-98 AND 01-99
Data Element 37 (Age of Offender) was submitted
with an unreasonable range span from the
youngest age of 01 to the oldest age of 98 or 99.
1601
WARNING - AGE OF
ARRESTEE LESS THAN 3
The agency may have a reporting problem when
using Data Element 47 (Age of Arrestee). The
agency may be confusing the age code of 01, 02,
and 03 as the Victim/Offender Sequence Number.
1607
WARNING - OFFENDER
SEQUENCE NUMBER WITH
ALL UNKNOWN
INFORMATION
Data Element 36 (Offender Sequence Number)
are being reported as 01, 02, etc. with Data
Element 37 (Unknown Offender Age), Data
Element 38 (Sex of Offender), and Data Element
39 (Race of Offender). If nothing is known about
the offender(s), the agency should enter 00 =
Unknown in Data Element 36 (Offender Sequence
Number), and Data Elements 37 through 39
should be blank.
1608
WARNING - DUI WITH
ARRESTEE UNDER 13
Please verify Data Element 47 (Age of Arrestee).
The arrestee is listed as under age 13 and the
offense is driving under the influence.
06/15/2020
2019.2.1 NIBRS Technical Specification
191
1609
1640
WARNING - VIOLENT CRIME
WITH ARRESTEE UNDER 11
WARNING - NO DISPOSITION
FOR POSSIBLE JUVENILE
ARRESTEE
Please verify Data Element 47 (Age of Arrestee).
The arrestee is listed as under age 11 and the
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
adult, but the average age is a juvenile.
Note: When an age range is not entered and the
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.
1641
WARNING - ARRESTEE HAD
AN AGE OF 99 OR OLDER
Data Element 47 (Age of Arrestee) was entered
with a value of 99 which means the arrestee was
over 98 years old. Verify that the submitter of data
is not confusing the 99 = Over 98 Years Old with
00 = Unknown.
1651
WARNING - ARRESTEE AGE
RANGE OF 01-98 AND 01-99
Data Element 47 (Age of Arrestee) in a Group A
Incident Report was submitted with an
unreasonable range span from the youngest age
of 01 to the oldest age of 98 or 99.
1701
WARNING - AGE OF
ARRESTEE LESS THAN 3
The agency may have a reporting problem when
using Data Element 47 (Age of Arrestee).
1708
WARNING - DUI WITH
ARRESTEE UNDER 13
Please verify Data Element 47 (Age of Arrestee).
The arrestee is listed as under age 13, and the
offense is driving under the influence.
1740
WARNING - NO DISPOSITION
FOR POSSIBLE JUVENILE
ARRESTEE
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
adult, but the average age is a juvenile.
Note: When an age range is not entered and the
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.
1741
WARNING - ARRESTEE IS
OVER AGE 98
Data Element 47 (Age of Arrestee) was entered
with a value of 99, which means the arrestee is
over 98 years old. The submitter should verify that
99 = Over 98 Years Old is not being confused with
00 = Unknown.
1751
WARNING - ARRESTEE AGE
RANGE OF 01-98 AND 01-99
Data Element 47 (Age of Arrestee) in a Group B
arrest was submitted with an unreasonable range
span from the youngest age of 01 to the oldest
age of 98 or 99.
06/15/2020
2019.2.1 NIBRS Technical Specification
192
6 RECORD LAYOUTS
6.1 Administrative Segment Layout (Level 1)
Segment Length:
SEGMENT
LENGTH
1-4
0087 (without Cargo Theft)
0088 (with Cargo Theft)
SEGMENT
LEVEL
5
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
DATA ELEMENT 3 INCLUDES 3 ELEMENTS
REPORT
INCIDENT
DATE
INCIDENT
DATE
INDICATOR
HOUR
(3)
(3)
(3)
38-45
46
47-48
EXCEPTIONAL CLEARANCE OFFENSE CODE
OCCURS 10 TIMES
EXCEPTIONAL
EXCEPTIONAL
CLEARNCE
CLEARANCE
OFFENSE CODE
OFFENSE CODE
THROUGH
#1
#10
58-60
85-87
CLEARED
EXCEPTIONALLY
(4)
49
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
EXCEPTIONAL
CLEARANCE
DATE
(5)
50-57
OPTIONAL
CARGO
THEFT
(2A)
88
Figure 6-1 Administrative Segment Layout (Level 1)
06/15/2020
2019.2.1 NIBRS Technical Specification
193
6.2 Offense Segment Layout (Level 2)
Segment Length:
SEGMENT
LENGTH
1-4
0063 (1 Bias Motivation)
0071 (5 Bias Motivations)
SEGMENT
LEVEL
5
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
DATA ELEMENT 8 OCCURS 3 TIMES
OFFENDER
OFFENDER
SUSPECTED
SUSPECTED
OF USING #1 THROUGH OF USING #3
(8)
(8)
42
44
YEAR OF
SUBMISSIO
N
9-12
LOCATION
TYPE
(9)
45-46
NUMBER
OF
PREMISES
ENTERED
(10)
47-48
CITY
INDICATOR
13-16
METHOD
OF ENTRY
(11)
49
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
UCR
OFFENSE
CODE
(6)
38-40
OFFENSE
ATTEMPTED/
COMPLETED
(7)
41
DATA ELEMENT 12 OCCURS 3 TIMES
TYPE
TYPE
CRIMINAL
CRIMINAL
ACTIVITY #1 THROUGH
ACTIVITY #3
(12)
(12)
50
52
DATA ELEMENT 13 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 3 TIMES
TYPE
AUTOMATIC
AUTOMATIC
WEAPON
TYPE WEAPON
FORCE
WEAPON
WEAPON
FORCE
THROUGH
INVOLVED #1 INDICATOR #1
INDICATOR #3
INVOLVED #3
(13)
(13)
(13)
(13)
53-54
55
59-60
61
BIAS MOTIVATION #2 - #5 ARE OPTIONAL
DATA ELEMENT 8A OCCURS 4 TIMES
BIAS
MOTIVATION #1
(8A)
62-63
BIAS
MOTIVATION #2
(8A)
64-65
THROUGH
BIAS
MOTIVATION #5
(8A)
70-71
Figure 6-2 Offense Segment Layout (Level 2)
06/15/2020
2019.2.1 NIBRS Technical Specification
194
6.3 Property Segment Layout (Level 3)
Segment Length:
SEGMENT
LENGTH
1-4
0307
SEGMENT
LEVEL
5
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
INCIDENT
NUMBER
(2)
26-37
ORI
(1)
17-25
TYPE
PROPERTY
LOSS/ETC
(14)
38
DATA ELEMENTS 15, 16, & 17 AS A GROUP OCCUR 10 TIMES
PROPERTY
DESCRIPTION #1
(15)
39-40
NUMBER OR
STOLEN
MOTOR
VEHICLES
(18)
229-230
VALUE OF
PROPERTY #1
(16)
41-49
NUMBER OF
RECOVERED
MOTOR
VEHICLES
(19)
231-232
DATE
RECOVERED #1
(17)
50-57
THROUGH
PROPERTY
DESCRIPTION #10
(15)
210-211
VALUE OF
PROPERTY #10
(16)
212-220
DATE
RECOVERED
#10 (17)
221-228
DATA ELEMENTS 20, 21, & 22 AS A GROUP OCCUR 3 TIMES
ESTIMATED
SUSPECTED
DRUG
TYPE DRUG
DRUG TYPE #1
QUANTITY #1
MEASUREMENT #1
THROUGH
(22)
(20)
(21)
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)
06/15/2020
2019.2.1 NIBRS Technical Specification
195
6.4 Victim Segment Layout (Level 4)
Segment Length:
SEGMENT
LENGTH
1-4
0129 (without LEOKA)
0141 (with LEOKA)
SEGMENT
LEVEL
5
SEGMENT
ACTION
TYPE
6
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
VICTIM
SEQUENCE
NUMBER
(23)
38-40
RACE OF
VICTIM
(28)
77
ETHNICITY
OF VICTIM
(29)
78
DATA ELEMENT 24 OCCURS 10 TIMES
VICTIM CONNECTED
TO UCR OFFENSE #1
(24)
41-43
RESIDENT
STATUS
OF
VICTIM
(30)
79
THROUGH
VICTIM CONNECTED TO
UCR OFFENSE #10
(24)
68-70
DATA ELEMENT 31 OCCURS 2 TIMES
AGGRAVATED
AGGRAVATED
ASSAULT/HOMICIDE
ASSAULT/HOMICIDE
CIRCUMSTANCES #1
CIRCUMSTANCES #2
(31)
(31)
80-81
82-83
OFFENDER
NUMBER TO BE
RELATED #1
(34)
90-91
TYPE OF
VICTIM
(25)
71
AGE OF
VICTIM
(26)
72-75
ADDITIONAL
JUSTIFIABLE
HOMICIDE
CIRCUMSTANCES
(32)
84
SEX OF
VICTIM
(27)
76
DATA ELEMENT 33 OCCURS 5 TIMES
TYPE
INJURY #1
(33)
85
DATA ELEMENTS 34 & 35 AS A GROUP OCCUR 10 TIMES
RELATIONSHIP
OFFENDER
RELATIONSHIP
OF VICTIM TO
NUMBER TO BE
OF VICTIM TO
OFFENDER #1
RELATED #10
OFFENDER #10
THROUGH
(35)
(34)
(35)
92-93
126-127
128-129
THROUGH
TYPE
INJURY #5
(33)
89
LEOKA DATA ELEMENTS ARE OPTIONAL
OFFICER –
TYPE OF OFFICER
OFFICER
ACTIVITY/
ASSIGNMENT
ORI OTHER
CIRCUMSTANCE
TYPE
JURISDICTION
(25C)
(25A)
(25B)
130-131
132
133-141
Figure 6-4 Victim Segment Layout (Level 4)
06/15/2020
2019.2.1 NIBRS Technical Specification
196
6.5 Offender Segment Layout (Level 5)
Segment Length:
SEGMENT
LENGTH
1-4
OFFENDER
SEQUENCE
NUMBER
(36)
38-39
0045 (without Offender Ethnicity)
0046 (with Offender Ethnicity)
SEGMENT
LEVEL
5
AGE OF
OFFENDER
(37)
40-43
SEGMENT
ACTION TYPE
6
SEX OF
OFFENDER
(38)
44
MONTH OF
SUBMISSION
7-8
RACE OF
OFFENDER
(39)
45
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
OPTIONAL
ETHNICITY OF
OFFENDER
(39A)
46
Figure 6-5 Offender Segment Layout (Level 5)
06/15/2020
2019.2.1 NIBRS Technical Specification
197
6.6 Arrestee Segment Layout (Level 6)
Segment Length:
SEGMENT
LENGTH
1-4
ARREST
DATE
(42)
52-59
0110
SEGMENT
LEVEL
5
TYPE OF
ARREST
(43)
60
AGE OF
ARRESTEE
(47)
71-74
SEGMENT
ACTION
TYPE
6
MULTIPLE
ARRESTEE
SEGMENTS
INDICATOR
(44)
61
SEX OF
ARRESTEE
(48)
75
MONTH OF
SUBMISSION
7-8
UCR
ARREST
OFFENSE
CODE
(45)
62-64
RACE OF
ARRESTEE
(49)
76
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
INCIDENT
NUMBER
(2)
26-37
ARRESTEE
SEQUENCE
NUMBER
(40)
38-39
ARREST
TRANSACTION
NUMBER
(41)
40-51
DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE
AUTOMATIC
ARRESTEE
AUTOMATIC
WAS ARMED
WEAPON
WAS ARMED
WEAPON
WITH #1
INDICATOR #1
WITH #2
INDICATOR #2
(46)
(46)
(46)
(46)
65-66
67
68-69
70
ETHNICITY OF
ARRESTEE
(50)
77
RESIDENT
STATUS OF
ARRESTEE
(51)
78
DISPOSITION
OF ARRESTEE
UNDER 18
(52)
79
CLEARANCE
INDICATOR
80
CLEARANCE OFFENSE CODE OCCURS 10 TIMES
CLEARANCE
CLEARANCE
OFFENSE
OFFENSE
THROUGH
CODE #10
CODE #1
108-110
81-83
Figure 6-6 Arrestee Segment Layout (Level 6)
06/15/2020
2019.2.1 NIBRS Technical Specification
198
6.7 Group B Arrest Report Segment Layout (Level 7)
Segment Length:
SEGMENT
LENGTH
1-4
TYPE OF
ARREST
(43)
48
RACE OF
ARRESTEE
(49)
63
0066
SEGMENT
ACTION
TYPE
6
SEGMENT
LEVEL
5
UCR
ARREST
OFFENSE
CODE
(45)
49-51
MONTH OF
SUBMISSION
7-8
YEAR OF
SUBMISSION
9-12
CITY
INDICATOR
13-16
ORI
(1)
17-25
ARREST
TRANSACTION
NUMBER
(41)
26-37
DATA ELEMENT 46 INCLUDES 2 ELEMENTS AND AS A GROUP OCCURS 2 TIMES
ARRESTEE
AUTOMATIC
ARRESTEE
AUTOMATIC
WAS ARMED
WEAPON
WAS ARMED
WEAPON
WITH #1
INDICATOR #1
WITH #2
INDICATOR #2
(46)
(46)
(46)
(46)
52-53
54
55-56
57
ETHNICITY OF
ARRESTEE
(50)
64
RESIDENT
STATUS OF
ARRESTEE
(51)
65
ARRESTEE
SEQUENCE
NUMBER
(40)
38-39
AGE OF
ARRESTEE
(47)
58-61
SEX OF
ARRESTEE
(48)
62
DISPOSITION
OF ARRESTEE
UNDER 18
(52)
66
Figure 6-7 Group B Arrest Report Segment Layout (Level 7)
06/15/2020
2019.2.1 NIBRS Technical Specification
ARREST
DATE
(42)
40-47
199
6.8 Zero Report Segment Layout (Level 0)
Segment Length:
0043
SEGMENT
LENGTH
SEGMENT
LEVEL
SEGMENT
ACTION
TYPE
MONTH OF
SUBMISSION
YEAR OF
SUBMISSION
CITY
INDICATOR
ORI
(1)
INCIDENT
NUMBER
(2)
ZERO
REPORT
MONTH
ZERO
REPORT
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
YEAR
MONT
H
SUBMISSIO
N RECORD
NUMBER
SEGMENT
ACTION
TYPE
1-4
5-6
7-13
14
DATA
ELEMENT
NUMBER
44-46
ERROR
NUMBER
47-49
DATA VALUE
IN ERROR
50-61
ORI
INCIDENT
NUMBER
SEGMENT
LEVEL
UCR
OFFENSE
CODE
PERSON
SEQUENCE
NUMBER
TYPE
PROPERTY
LOSS/ETC.
15-23
24-35
36
37-39
40-42
43
ERROR
MESSAGE
62-140
UNUSED
FIELD
141-146
Figure 6-9 EDS Layout
06/15/2020
2019.2.1 NIBRS Technical Specification
200
6.10 WDS Layout
Segment Length:
0149
SEGMENT
ACTION
TYPE
7-13
14
DATA ELEMENT NUMBER
VIOLATION
NUMBER
DATA VALUE IN VIOLATION
VIOLATION
MESSAGE
45-47
48-59
60-71
72-149
REPORT
YEAR
REPORT
MONTH
1-4
5-6
SUBMISSION
RECORD
NUMBER
ORI
INCIDENT
NUMBER
PUBLICATION
EFFECT
UCR
OFFENSE
CODE
1523
24-35
36
37-39
SEGMENT
LEVEL
PERSON
SEQUENCE
NUMBER
40
41-43
TYPE
PROPERTY
LOSS/ETC.
44
Figure 6-10 WDS Layout
06/15/2020
2019.2.1 NIBRS Technical Specification
201
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
290
of Property
Destruction/Damage/Vandalism
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
06/15/2020
2019.2.1 NIBRS Technical Specification
A-1
Group A Offenses
Offense
Code
Offense Description
Crime Against
Fraud Offenses
26A
False
Pretenses/Swindle/Confidence
Game
Property
Fraud Offenses
26B
Credit Card/Automated Teller
Machine Fraud
Property
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*
Property
Gambling Offenses
39A
Betting/Wagering
Society
Gambling Offenses
39B
Operating/Promoting/Assisting
Gambling
Society
Gambling Offenses
39C
Gambling Equipment
Violations
Society
Gambling Offenses
39D
Sports Tampering
Society
Homicide Offenses
09A
Murder & Nonnegligent
Manslaughter
Person
Homicide Offenses
09B
Negligent Manslaughter
Person
Homicide Offenses
09C
Justifiable Homicide
Not a Crime
Immigration Violations
30A
Illegal Entry into the United
States*
Society
Immigration Violations
30B
False Citizenship*
Society
Immigration Violations
30C
Smuggling Aliens*
Society
06/15/2020
2019.2.1 NIBRS Technical Specification
A-2
Group A Offenses
Offense
Code
Offense Description
Crime Against
Immigration Violations
30D
Re-entry after Deportation*
Society
Human Trafficking
64A
Human Trafficking,
Commercial Sex Acts
Person
Human Trafficking
64B
Human Trafficking,
Involuntary Servitude
Person
Kidnapping/Abduction
100
Kidnapping/Abduction
Person
Fugitive Offenses
49A
Harboring Escapee/ Concealing
from Arrest*
Society
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
Larceny/Theft Offenses
23E
Theft From Coin-Operated
Machine or Device
Property
Larceny/Theft Offenses
23F
Theft From Motor Vehicle
Property
Larceny/Theft Offenses
23G
Theft of Motor Vehicle Parts or
Accessories
Property
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
Prostitution Offenses
40B
Assisting or Promoting
Prostitution
Society
06/15/2020
2019.2.1 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
Offender*
Society
Stolen Property Offenses
280
Stolen Property Offenses
Property
Treason
101
Treason*
Society
Weapon Law Violations
520
Weapon Law Violations
Society
Weapon Law Violations
521
Violation of National Firearm
Act of 1934*
Society
Weapon Law Violations
522
Weapons of Mass Destruction*
Society
Weapon Law Violations
526
Explosives*
Society
06/15/2020
2019.2.1 NIBRS Technical Specification
A-4
A.2 Group B Offenses
Group B Offenses
Offense
Code
Offense Description
Crime Against
Bad Checks
90A
Bad Checks
Property
Curfew/Loitering/
Vagrancy Violations
90B
Curfew/Loitering/Vagrancy
Violations
Society
Disorderly Conduct
90C
Disorderly Conduct
Society
Driving Under the
Influence
90D
Driving Under the Influence
Society
Drunkenness
90E
Drunkenness
Society
Family Offenses,
Nonviolent
90F
Family Offenses, Nonviolent
Society
Liquor Law Violations
90G
Liquor Law Violations
Society
Peeping Tom
90H
Peeping Tom
Society
Trespass of Real Property
90J
Trespass of Real Property
Society
Bond Default
90K
Failure to Appear*
Society
Federal Resource
Violations
90L
Federal Resource Violations*
Society
Perjury
90M
Perjury*
Society
All Other Offenses
90Z
All Other Offenses
Person, Property,
or Society
*Denotes offenses for federal and tribal LEA reporting only
06/15/2020
2019.2.1 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 2019.2 NIBRS
XML Developer’s Guide, details of the XML structure of a NIBRS submission are visually
shown in figures.
06/15/2020
2019.2.1 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:
•
•
•
•
06/15/2020
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.
2019.2.1 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.
06/15/2020
2019.2.1 NIBRS Technical Specification
D-1
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
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)
06/15/2020
2019.2.1 NIBRS Technical Specification
E-1
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.
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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-2
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).
•
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:
•
•
•
•
•
•
•
•
•
06/15/2020
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
2019.2.1 NIBRS Technical Specification
E-3
•
•
•
•
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
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:
•
•
06/15/2020
ORI Number
Judicial District* (For federal reporting only)
2019.2.1 NIBRS Technical Specification
E-4
•
•
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)
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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-5
Mandatory Elements/Values:
1. Offense Attempted/completed = Attempted
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 Offender Sequence Number = Unknown
a. Offender Number to be Related = Unknown
5. If Offense Code = Aggravated Assault or Simple Assault
a. Type Weapon/Force Involved
b. Type Injury
6. Location Type cannot = Cyberspace
7. If Offense Code = Aggravated Assault
a. Aggravated Assault/Homicide Circumstances = Argument, Assault on LEO,
Drug Dealing, Gangland, Juvenile Gang, Domestic Violence, Mercy Killing,
Other Felony, Other Circumstances, or Unknown
8. 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
9. If Criminal Activity/Gang Information provided
a. Criminal Activity/Gang Information = Juvenile, Other Gang, or
None/Unknown
10. 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 = False
a. Type Property Loss = None, Recovered, Stolen, or Unknown
06/15/2020
2019.2.1 NIBRS Technical Specification
E-6
4. If Type Property Loss = Recovered or Stolen
a. Property Description
b. Value of Property
5. If Type Property Loss = Recovered
a. 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
5. If Offense Attempted/Completed = Completed
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 cannot = Structure Single Occupancy Dwelling,
Structure Other Dwellings, Structure Other Commercial, Structure Industrial,
Structure Public, Structure Storage, Structure Other
b. Value of Property
8. If Type Property Loss = Recovered
a. 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 of Victim = Government
2. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
3. For Import Violations - If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized or None
b. Property Description
c. Value of Property
06/15/2020
2019.2.1 NIBRS Technical Specification
E-7
4. For Export Violations - If Offense Attempted/Completed = Attempted
a. Type Property Loss = Counterfeited/Forged, Recovered, or Seized
b. Property Description
c. Value of Property
5. 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:
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. Property Description
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
i. If Seized
1. Property Description
2. 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-8
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
4. If Type Property Loss = Recovered
a. 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. If Offense Attempted/Completed Indicator = Attempted
a. Type Property Loss = None or Unknown
3. If Offense Attempted/Completed Indicator = Completed
a. Type Property Loss = None or Seized
4. If Property Description does not equal Drugs/Narcotic Violations
a. Value of Property
b. Type of Victim = Society
5. 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-9
i. Suspected Drug Type
ii. Estimated Drug Quantity
iii. Type Drug Measurement
6. If Offense Code = Drug Equipment Violations
a. If Type Property Loss = Seized
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
4. If Type Property Loss = Recovered
a. 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 Indicator = Complete
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
5. If Type Property Loss = Recovered
a. Date Recovered
06/15/2020
2019.2.1 NIBRS Technical Specification
E-10
6. 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
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
4. If Type Property Loss = Recovered
a. Date Recovered
5. 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-11
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
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.
2.
3.
4.
Offense Attempted/Completed = Completed
Type Weapon/Force Involved/Automatic Indicator
Type of Victim = Individual or Law Enforcement Officer
If Type of Victim = Law Enforcement Officer
a. Type of Activity (Officer)/Circumstance
b. Assignment Type (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, Other Circumstances, or Unknown
6. If Offense Code = Negligent Manslaughter
a. Aggravated Assault/Homicide Circumstances = Child Playing, Gun-Cleaning,
Hunting, Weapon Handling, or Negligent Killing
7. If Offense Code = Justifiable Homicide
a. Aggravated Assault/Homicide Circumstances = Killed by Private Citizen or
Killed by Police
b. Additional Justifiable Homicide Circumstances
8. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
9. If Offender Sequence Number = Unknown
a. Offender Number to be Related = Unknown
10. If Offense Code = Justifiable Homicide
a. Aggravated Assault/Homicide Circumstances = Killed by Private Citizen or
Killed by Police
06/15/2020
2019.2.1 NIBRS Technical Specification
E-12
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
11. If Type of Victim = Law Enforcement Officer
a. Type of Activity (Officer)/Circumstance
b. Assignment Type (Officer)
12. If Type of Victim = Law Enforcement Officer and Reporting Agency ORI Number
differs from officer’s regular jurisdiction:
a. ORI-Other Jurisdiction (Officer)
13. If Offense Code = Murder Nonnegligent or Negligent Manslaughter and Criminal
Activity/Gang Information is provided
a. Criminal Activity/Gang Information = Juvenile, Other Gang, or
None/Unknown
14. 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.
2.
3.
4.
5.
Offense Attempted/Completed = Attempted or Completed
Type Weapon/Force Involved/Automatic Indicator
Type of Victim = Individual
Type Injury
If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
6. If Offender Sequence Number = Unknown
a. Offender Number to be Related = Unknown
20. Immigration Violations* (For federal and tribal reporting only)
Offense Codes Illegal Entry (30A), False Citizenship (30B), Smuggling Aliens (30C), Reentry 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-13
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
5. If Type Property Loss = Recovered
a. Date Recovered
6. Type of Victim = Individual
7. Type Injury
8. If Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
9. If Offender Sequence Number = Unknown
a. Offender Number to be Related = Unknown
10. Location Type cannot = Cyberspace
11. If Criminal Activity/Gang Information is provided:
a. Criminal Activity/Gang Information = Juvenile, 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-14
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
4. If Type Property Loss = Recovered
a. Property Description = Automobiles, Buses, Other Motor Vehicles,
Recreational Vehicles, or Trucks
b. Date Recovered
5. If Property Description = Automobiles, Buses, Other Motor Vehicles, Recreational
Vehicles, or Trucks
a. Number of Recovered Motor Vehicles = 00 – 99
6. 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
7. 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
06/15/2020
2019.2.1 NIBRS Technical Specification
E-15
Mandatory Elements/Values:
1. Type of Victim = Society
26. Robbery
Offense Code 120 – Crime Against Property
Mandatory Elements/Values:
1.
2.
3.
4.
5.
6.
Cargo Theft = True or False
Type Weapon/Force Involved/Automatic Indicator
Type of Victim = Individual
Type Injury
Location Type cannot = Cyberspace
If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
7. If Offense Attempted/Completed = Completed
a. Type Property Loss = Recovered or Stolen
b. Property Description
c. Value of Property
8. If Type Property Loss = Recovered
a. Date Recovered
9. If Type of Victim = Individual and Offender Sequence Number does not = Unknown
a. Offender Number to be Related
b. Relationship of Victim to Offender
10. If Type of Victim = Individual and Offender Sequence Number = Unknown
a. Offender Number to be Related = Unknown
11. If Criminal Activity/Gang Information is present:
a. Criminal Activity/Gang Information = Juvenile, 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 Criminal Activity/Gang Information is present:
a. Criminal Activity/Gang Information = Juvenile, Other Gang, or
None/Unknown
4. Type of Victim = Individual
5. Type Injury
06/15/2020
2019.2.1 NIBRS Technical Specification
E-16
6. If Type of Victim = Individual and Offender Sequence Number does not = 00
(Unknown)
a. Offender Number to be Related
7. Relationship of Victim to Offender
8. If Type of Victim = Individual and Offender Sequence Number = 00 (Unknown)
a. Offender Number to be Related = Unknown
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 Type of Victim = Individual and Offender Sequence Number does not = 00
(Unknown)
a. Offender Number to be Related
b. Relationship of Victim to Offender
4. If Type of Victim = Individual and Offender Sequence Number = 00 (Unknown)
a. Offender Number to be Related = Unknown
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.
2.
3.
4.
Offense Attempted/Completed = Attempted
Type of Victim = Society
Offender Number to be Related cannot be Unknown
Location Type cannot = Cyberspace
30. Stolen Property Offenses
Offense Code 280 – 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 = None or Recovered
4. If Type Property Loss = Recovered
a. Property Description
b. Value of Property
06/15/2020
2019.2.1 NIBRS Technical Specification
E-17
c. 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
4. If Offense Attempted/Completed = Attempted
a. Type Property Loss = None or Unknown
5. If Offense Attempted/Completed = Completed
a. Type Property Loss = Seized or None
i. If Seized
1. Property Description
2. Value of Property
6. If Offense Code = Weapon Law Violations:
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.
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:
•
•
•
•
•
•
•
•
06/15/2020
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
2019.2.1 NIBRS Technical Specification
E-18
•
•
•
•
•
•
06/15/2020
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)
2019.2.1 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
06/15/2020
2019.2.1 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
06/15/2020
2019.2.1 NIBRS Technical Specification
F-2
| File Type | application/pdf |
| File Modified | 2020-07-01 |
| File Created | 2020-07-01 |