U.S. Department of Justice

Federal Bureau of Investigation

Criminal Justice Information Services Division

Uniform Crime Reporting

National Incident-Based

 Reporting System

Volume 4:

Error Message Manual

December 1999
NATIONAL INCIDENT-BASED

REPORTING SYSTEM

VOLUME 4: ERROR MESSAGE MANUAL

Prepared by

U.S. Department of Justice

Federal Bureau of Investigation

Criminal Justice Information Services Division

Uniform Crime Reporting Program

December 3, 1999

iii

FOREWORD

Information about the National Incident-Based Reporting System (NIBRS) is contained in

the four documents described below:

Volume 1: Data Collection Guidelines

This document is for the use of local, state, and federal Uniform Crime Reporting (UCR)

Program personnel (i.e., administrators, training instructors, report analysts, coders, data entry

clerks, etc.) who are responsible for collecting and recording NIBRS crime data for submission to

the FBI. It contains a system overview and descriptions of the offenses, offense codes, reports,

data elements, and data values used in the system.

Volume 2: Data Submission Specifications

This document is for the use of local, state, and federal systems personnel (i.e., computer

programmers, analysts, etc.) who are responsible for preparing magnetic media for submission to

the FBI. It contains the data submission instructions for magnetic media, record layouts, and

error-handling procedures that must be followed in submitting magnetic media to the FBI for

NIBRS reporting purposes.

Volume 3: Approaches to Implementing an Incident-Based Reporting (IBR) System

This document is for the use of local, state, and federal systems personnel (i.e., computer

programmers, analysts, etc.) who are responsible for developing an IBR system that will meet

NIBRS’s reporting requirements. It contains suggested approaches to developing an IBR system,

including a model incident report, standard data entry guide, data entry screens, and software

design suggestions. This manual is being phased out. Copies will be available until the supply is

depleted.

Volume 4: Error Message Manual

This document is for the use of local, state, and federal systems personnel (i.e., computer

programmers, analysts, etc.) who are responsible for preparing magnetic media for submission to

the FBI. It contains designations of mandatory and optional data elements, data element edits,

and error messages.

Copies of the above-listed documents can be obtained by writing to the:

Communications Unit

Criminal Justice Information Services Division

Federal Bureau of Investigation

Module D3

1000 Custer Hollow Road

Clarksburg, West Virginia 26306-0154

v

PURPOSE

These specifications have been prepared for the use of local, state, and federal systems

personnel (i.e., computer programmers and analysts) who are responsible for preparing magnetic

media for submission to the FBI. Included are designations of Mandatory and Optional data

elements, data element errors, and error messages that must be followed to meet NIBRS’s

reporting requirements.

Magnetic media submission instructions, record layouts, and error handling procedures are

discussed in Volume 2: Data Submission Specifications. Data entry approaches for NIBRS data

elements are discussed in Volume 3: Approaches to Implementing an Incident-Based Reporting

(IBR) System.

Whenever tape is specified within this document, it refers to the magnetic media that is

written upon by the participant when submitting data to the FBI. Volume 2, section I, “Magnetic

Data Submission Instructions,” explains the various types of magnetic media that the FBI 

accepts.

The functional data requirements, as discussed in this document, provide suggestions for

automating data element presence requirements relating to mandatory data elements, data element

edits, and error messages created as a result of errors.

Section I, “Mandatories,” explains all the UCR Offense Codes with the associated data

element numbers for Mandatory fields and those that are Optional. Each UCR Offense Code

requires that certain data elements be entered.

Section II, “Data Element Edits,” details all the software edits that the FBI performs on

data submitted by the participant. These are in addition to those specified in section I and are

listed in order by data element number.

Section III, “Error Numbers and Messages,” shows all messages produced as a result of

FBI error detection. These are listed in ascending sequence by error number.

vii

CONTENTS

I. Mandatories 1

A. Data Element Requirements 1

B. Mandatory Versus Optional Data Elements 1

C. Required Data Values 2

D. Group “A” Incident Report - Common Data Elements 4

E. Group “A” Incident Report - Additional Data Elements 6

F. Group “B” Arrest Report Data Elements 14

 II. Data Element Edits 17

A. General Information 17

B. Data Element Edits 18

(Numbers shown in parentheses are grouped in logical segments.)

Administrative Segment Edits (1-5) 18

Offense Segment Edits (6-13) 25

Property Segment Edits (14-22) 31

Victim Segment Edits (23-35) 40

Offender Segment Edits (36-39) 49

Arrestee Segment Edits (40-52) 53

Zero-Reporting Segment Edits 59

C. Global Edits 60

General Category 60

Administrative Segment Edits 64

Offense Segment Edits 66

Property Segment Edits 66

Victim Segment Edits 71

Arrestee Segment Edits 72

D. UCR Offense Code Edits 75

 III. Error Numbers and Messages 79

A. General Information 79

Information concerning error resolution and error number descriptions
viii

B. Error Numbers and Messages 81

Listed in numerical sequence by error number

Error Type (Range)

Structure/Control Program Errors (000-089) 81

Zero-Reporting Segment Errors (090-099) 87

Administrative Segment Errors (100-199) 88

Offense Segment Errors (200-299) 94

Property Segment Errors (300-399) 99

Victim Segment Errors (400-499) 109

Offender Segment Errors (500-599) 119

Arrestee Segment Errors (600-699) 123

Group “B” Arrest Report Errors (700-799) 129
1

I. 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: 

(a) Common Data Elements -- These are data elements which are applicable to

all Group “A” offenses. A list of Common data elements can be found on pages 4-6. 

(b) 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. A list of Additional data elements is

located on pages 6-14. 

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. A list of Group “B” Arrest Report data elements can be found on pages 14-15. 

B. Mandatory versus Optional Data Elements

Data elements designated as being 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 Number, Incident Number, and Incident

Date/Hour. If an incident report submitted on the magnetic media 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 any code but “N” in 4 (Cleared Exceptionally):

5 = Exceptional Clearance Date

This means that if any code but N = Not Applicable was entered into Data Element 4

(Cleared Exceptionally), the date of the clearance is to be entered into Data Element 5

(Exceptional Clearance Date). 
Mandatories

2

Data elements designated as being 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. There are four Optional data elements: 29

(Ethnicity of Victim); 30 (Resident Status of Victim); 50 (Ethnicity of Arrestee); and 51 (Resident

Status of Arrestee). 

Example: Optional: If “I” in 25 (Type of Victim):

 29 = Ethnicity (of Victim)

30 = Resident Status (of Victim) 

It is, therefore, left up to the submitting agency’s discretion whether Data Elements 29 and

30 will be reported. However, in order to be reported, the victim must be an I = Individual. 

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 segments (e.g., Property Segment, Victim Segment, etc.) submitted to the FBI for that

offense; and if other data values are entered, the report will be rejected by the FBI’s computer 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 (e.g., Assault Offenses, Homicide Offenses,

etc.), 25 = Type of Victim (I) means that the submitting agency must enter I = Individual into Data

Element 25 (Type of Victim) of the Victim Segments relating to those offenses. If any other type

of victim code is entered into the Victim Segment submitted for one of these offenses (e.g., B =

Business or S = Society/Public), the report will be rejected by the FBI’s computer as containing

an error.

Example (2): For all Crimes Against Society (e.g., Drug/Narcotic Offenses, Gambling

Offenses, etc.), 25 = Type of Victim (S) means that the submitting agency must enter S =

Society/Public into Data Element 25 (Type of Victim) of the Victim Segments relating to those

offenses. If any other type of victim code is entered into the Victim Segment submitted for one of

these offenses (e.g., I = Individual or B = Business), the report will be rejected by the FBI’s

computer 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 would be entered into the Victim Segment for the Crime

Against Person, while S = Society/Public would be entered into the Victim Segment for the Crime

Against Society. 
Mandatories

3

Again, If statements have been used to ensure correct reporting. The following If

statements are given as examples: 

Example (1): If “A” in 7 (Offense Attempted/Completed):

14 = Type of Property Loss/Etc. (1 or 8) 

This means that if the offense (e.g., Arson) was only A = Attempted (i.e., no fire 

resulted), then the type of property loss/etc. designated within the parentheses must be either 1 =

None or 8 = Unknown. 

Example (2): If “C” in 7 (Offense Attempted/Completed):

14 = Type of Property Loss/Etc. (2)

15 = Property Description

16 = Value of Property 

This means that if the offense (e.g., Arson) was C = Completed, then a Property Segment

must be submitted which has the type of property loss/etc. designated within the parentheses (2 =

Burned) entered into Data Element 14. If any other type of property loss/etc. was entered by the

submitting agency (e.g., 1 = None, 3 = Counterfeited, 4 = Destroyed/Damaged/Vandalized, 7 =

Stolen, etc.), the report will be rejected 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 Segment containing 

2 = Burned and another Property Segment containing 7 = Stolen could be

submitted for the incident. 

The above If statement also requires that a description of the burned property be entered

into Data Element 15 and its value be entered into Data Element 16. 

 Example (3): If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

This means that if an Offender Sequence Number was assigned (i.e., data were entered

describing an offender), then victim-to-offender relationship data must be entered into Data

Elements 34 (Offender Numbers to be Related) and 35 (Relationships of Victim to Offenders). 

Note: Example (3) applies only when a Crime Against Person (i.e., Homicide, Kidnaping,

Forcible Sex Offense, Assault Offense, or Nonforcible Sex Offense) or a Robbery

was committed against the victim. 
Mandatories

4

D. Group “A” Incident Report - Common Data Elements

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: (1) all initial Group “A” Incident

Reports; (2) initial Group “A” Incident Reports containing Arrestee Segments; (3) all updates

(e.g., Add Arrest, Modify, and Delete) to previously submitted Group “A” Incident Reports; and

(4) updates containing Arrestee Segments. 

Common Data Elements For All Initial Group “A” Incident Reports:

Mandatory: 1 = ORI Number 

 2 = Incident Number

 3 = Incident Date/Hour

 4 = Cleared Exceptionally 

If any code but “N” in 4 (Cleared Exceptionally):

 5 = Exceptional Clearance Date 

 6 = UCR Offense Code

 7 = Offense Attempted/Completed

 8 = Offender(s) Suspected of Using

 8A = Bias Motivation

 9 = Location Type

23 = Victim (Sequence) Number

24 = Victim Connected to UCR Offense Code(s)

25 = Type of Victim 

If “I” in 25 (Type of Victim):

26 = Age (of Victim)

27 = Sex (of Victim)

28 = Race (of Victim)

36 = Offender (Sequence) Number 

If any code but “00” in 36 (Offender Sequence Number):

37 = Age (of Offender)

38 = Sex (of Offender)

39 = Race (of Offender) 

Optional: If “I” in 25 (Type of Victim):

29 = Ethnicity (of Victim)

30 = Resident Status (of Victim) 
Mandatories

5

Supplemental Common Data Elements For Initial Group “A” Incident Reports 

Containing Arrestee Segments:

Mandatory: 40 = Arrestee (Sequence) Number

41 = Arrest (Transaction) Number

42 = Arrest Date

43 = Type of Arrest

44 = Multiple Arrestee Segments Indicator

45 = UCR Arrest Offense Code

46 = Arrestee Was Armed With

47 = Age (of Arrestee) 

If 47 (Age of Arrestee) is less than “18”:

52 = Disposition of Arrestee Under 18 

48 = Sex (of Arrestee)

49 = Race (of Arrestee)

Optional: 50 = Ethnicity (of Arrestee)

51 = Resident Status (of Arrestee) 

Common Data Elements For Updates (Add Arrest, Modify, and Delete) To Previously

Submitted Group “A” Incident Reports:

Mandatory: 1 = ORI Number

 2 = Incident Number 

Supplemental Common Data Elements For Updates Containing Arrestee Segments:

Mandatory: 40 = Arrestee (Sequence) Number

41 = Arrest (Transaction) Number

42 = Arrest Date

43 = Type of Arrest

44 = Multiple Arrestee Segments Indicator

45 = UCR Arrest Offense Code

46 = Arrestee Was Armed With

47 = Age (of Arrestee)

If 47 (Age of Arrestee) is less than “18”:

52 = Disposition of Arrestee Under 18 

48 = Sex (of Arrestee)

49 = Race (of Arrestee) 
Mandatories

6

Optional: 50 = Ethnicity (of Arrestee)

51 = Resident Status (of Arrestee) 

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 - Common Data Elements listed on pages 4-6. They complete

the data element reporting requirements for the individual offenses. These must be entered for the

specified offense. 

1. 200 Arson (Crime Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (2)

15 = Property Description

16 = Value of Property 

 2. 13A-13C Assault Offenses (Crimes Against Persons) 

Mandatory: 7 = Offense Attempted/Completed (C)

25 = Type of Victim (I) 

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

Only: 13A Aggravated Assault

13B Simple Assault 

Mandatory: 13 = Type Weapon/Force Involved

33 = Type Injury 

Only: 13A Aggravated Assault 

Mandatory: 31 = Aggravated Assault/Homicide Circumstances 
Mandatories

7

 3. 510 Bribery (Crime Against Property)

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1, 5, 7, or 8) 

If “5” or “7” in 14 (Type Property Loss/Etc.):

15 = Property Description

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

 4. 220 Burglary/Breaking and Entering (Crime Against Property)

Mandatory: If “14” or “19” in 9 (Location Type):

10 = Number of Premises Entered 

11 = Method of Entry 

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1, 5, 7, or 8) 

If “5” or “7” in 14 (Type Property Loss/Etc.):

15 = Property Description

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

 5. 250 Counterfeiting/Forgery (Crime Against Property) 

Mandatory: 12 = Type Criminal Activity 

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 
Mandatories

8

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (3, 5, or 6)

15 = Property Description

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

 6. 290 Destruction/Damage/Vandalism of Property 

 (Crime Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (4)

15 = Property Description

16 = Value of Property 

 7. 35A-35B Drug/Narcotic Offenses (Crimes Against Society) 

Mandatory: 12 = Type Criminal Activity 

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 6) 

If any code but “10” in 15 (Property Description):

16 = Value of Property 

25 = Type of Victim (S) 

 Only: 35A Drug/Narcotic Violations 

If “6” in 14 (Type Property Loss/Etc.):

15 = Property Description (any code but 11) 

If “1” in 14 (Type Property Loss/Etc.):

20 = Suspected Drug Type 
Mandatories

9

If “6” in 14 (Type Property Loss/Etc.) and

If “10” (Drugs) in 15 (Property Description):

20 = Suspected Drug Type

21 = Estimated Drug Quantity

22 = Type Drug Measurement 

Only: 35B Drug Equipment Violations 

If “6” in 14 (Type Property Loss/Etc.):

15 = Property Description (any code but 10) 

 8. 270 Embezzlement (Crime Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

15 = Property Description 

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

 9. 210 Extortion/Blackmail (Crime Against Property) 

Mandatory: 13 = Type Weapon/Force Involved

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8)

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

15 = Property Description

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.): 

17 = Date Recovered 

If “I” in 25 (Type of Victim):

33 = Type Injury 
Mandatories

10

10. 26A-26E Fraud Offenses (Crimes Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

15 = Property Description 

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

11. 39A-39D Gambling Offenses (Crimes Against Society) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (6)

15 = Property Description

16 = Value of Property 

25 = Type of Victim (S) 

Only: 39C Gambling Equipment Violations 

Mandatory: 12 = Type Criminal Activity 

12. 09A-09C Homicide Offenses (Crimes Against Persons) 

Mandatory: 7 = Offense Attempted/Completed (C)*

13 = Type Weapon/Force Involved

25 = Type of Victim (I)

31 = Aggravated Assault/Homicide Circumstances 

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

*Note: Attempted Murder is to be classified as Aggravated Assault.
Mandatories

11

Only: 09C Justifiable Homicide 

Mandatory: 31 = Aggravated Assault/Homicide Circumstances (20 or 21)

32 = Additional Justifiable Homicide Circumstances 

13. 100 Kidnaping/Abduction (Crime Against Person) 

Mandatory: 13 = Type Weapon/Force Involved 

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1, 5, 7, or 8) 

If “5” or “7” in 14 (Type Property Loss/Etc.):

15 = Property Description

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

25 = Type of Victim (I)

33 = Type Injury 

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

14. 23A-23H Larceny/Theft Offenses (Crimes Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

15 = Property Description

16 = Value of Property 
Mandatories

12

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

15. 240 Motor Vehicle Theft (Crime Against Property) 

Mandatory: If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

16 = Value of Property 

If “5” in 14 (Type Property Loss/Etc.):

15 = Property Description (any valid codes)

17 = Date Recovered 

If “03”, “05”, “24”, “28”, or “37” in 15 (Property Description):

19 = Number of Recovered Motor Vehicles 

If “7” in 14 (Type Property Loss/Etc.):

15 = Property Description (any valid codes, but one must be 

03, 05, 24, 28, or 37)

18 = Number of Stolen Motor Vehicles 

16. 370 Pornography/Obscene Material (Crime Against Society) 

Mandatory: 12 = Type Criminal Activity

25 = Type of Victim (S) 

17. 40A-40B Prostitution Offenses (Crimes Against Society) 

Mandatory: 25 = Type of Victim (S) 

18. 120 Robbery (Crime Against Property) 

Mandatory: 13 = Type Weapon/Force Involved 

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (5 or 7)

15 = Property Description

16 = Value of Property 
Mandatories

13

If “5” in 14 (Type Property Loss/Etc.):

17 = Date Recovered 

If “I” in 25 (Type of Victim):

33 = Type Injury 

If “I” in 25 (Type of Victim) and

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If “I” in 25 (Type of Victim) and

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

19. 11A-11D Sex Offenses, Forcible (Crimes Against Persons) 

Mandatory: 13 = Type Weapon/Force Involved

25 = Type of Victim (I)

33 = Type Injury 

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

20. 36A-36B Sex Offenses, Nonforcible (Crimes Against Persons) 

Mandatory: 25 = Type of Victim (I) 

If any code but “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related

35 = Relationship(s) of Victim to Offender(s) 

If code is “00” in 36 (Offender Sequence Number):

34 = Offender Number(s) to be Related (00)

21. 280 Stolen Property Offenses (Crimes Against Property) 

Mandatory: 12 = Type Criminal Activity 
Mandatories

14

If “A” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 8) 

If “C” in 7 (Offense Attempted/Completed):

14 = Type Property Loss/Etc. (1 or 5) 

If “5” in 14 (Type Property Loss/Etc.):

15 = Property Description

16 = Value of Property

17 = Date Recovered 

22. 520 Weapon Law Violations (Crimes Against Society) 

Mandatory: 12 = Type Criminal Activity

13 = Type Weapon/Force Involved

25 = Type of Victim (S) 

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 Segment of the Group “A” Incident Report, except for the Data Element 44 (Multiple

Arrestee Segments Indicator) which is not applicable. 

The data elements used in the Group “B” Arrest Report are as follows: 

Group “B” Arrest Report 

Mandatory: 1 = ORI Number

 *41 = Arrest (Transaction) Number

 *40 = Arrestee (Sequence) Number

42 = Arrest Date

43 = Type of Arrest

45 = UCR Arrest Offense Code

46 = Arrestee Was Armed With

47 = Age (of Arrestee)

48 = Sex (of Arrestee)

49 = Race (of Arrestee) 

*The order of these two data elements is reversed from that in the

Arrestee Segment. 
Mandatories

15

If 47 (Age of Arrestee) is less than “18”:

52 = Disposition of Arrestee Under 18 

Optional: 50 = Ethnicity (of Arrestee)

51 = Resident Status (of Arrestee) 

17

II. DATA ELEMENT EDITS

A. General Information

The personnel responsible for software development should be aware of the FBI editing

performed for each data element. Volume 1: Data Collection Guidelines details in section VI,

“Data Elements and Data Values,” all the valid code meanings applicable for each data element. 

This section should be referenced when establishing computer codes for data submitted to the FBI.

Some specific data element edits in subsection B of this section, pages 18-60, may also be

listed in subsection C (Global Edits), pages 60-75, and/or subsection D (UCR Offense Code

Edits), pages 75-78. This division was developed to provide a better understanding of certain

data relationships. The edit requirements in this section are in addition to those specified in

section I but may in some cases be duplicated. 

After each edit is a reference error number enclosed in parentheses, e.g., (056), (001), 

that is used when the error condition is detected by the FBI’s computer. These are defined in

section III. 

1. Computer Tables Will Assist With Presence Requirements

In order to provide a mechanism to determine what data elements belong with which

offenses as specified in section I of this manual, computer tables could be developed that contain

the data element numbers that belong with each offense. For example, the following table for

Data Element 7 (Offense Attempted/Completed) indicates which offense-dependent data elements

can be entered, i.e., the Additional Data Elements set forth in section I. The table can be

referenced by software when doing internal editing, checking, etc. (The method the FBI uses is

shown below.)

OFFENSE ATTEMPTED/COMPLETED DATA ELEMENTS

200 A 14

200 C 14, 15, 16

13A C 13, 31, 33, 34, 35

13B C 13, 33, 34, 35

13C C 34, 35

etc.

In a similar fashion, another table could contain the data elements of those fields that must

always be present for every Group “A” Incident Report submission, i.e., the Common 

Data Elements set forth in section I. This table would ensure the presence requirements for these

data elements.
Data Element Edits

18

In conjunction with these tables, software has to include specific edit requirements as

shown in section I. For example, offense 13A = Aggravated Assault requires that Data Element

25 (Type of Victim) be I = Individual.

If a data element is not applicable, the default value entered on the segment submitted on

magnetic media must be blanks, as specified in Volume 2: Data Submission Specifications,

section I.

2. References to Magnetic Media and Tape

Whenever magnetic media or tape is specified within the instructions, the terms refer to

the magnetic media that are written upon by the participant when submitting data to the FBI,

including diskettes. Volume 2, section I outlines the various types of magnetic media the FBI will

accept.

B. Data Element Edits

 

1. Data Element—Administrative Segment Edits

1 ORI Number

1) Must be present—cannot be blank.

(001, 101, 201, 301, 401, 501, 601, 701)

2) Must be a valid nine-character NCIC number, where the last two 

positions of the ORI must reflect 00 for nonfederal participants or a

UCR-assigned code for federal participants. 

(052, 086, 104, 204, 304, 404, 504, 604, 704)

3) First two positions must be the code of the state (e.g., SC, MD,

etc.) in which the incident occurred. For nonfederal participants,

every record must have the same code.

(059)

2 Incident Number

1) Must be present—cannot be blank.

(001, 101, 201, 301, 401, 501, 601, 701)
Data Element Edits

19

2) Zero-Reporting Segment (Level 0) must contain 12 zeros as the

incident number.

(092)

3) Must be left-justified with blank right-fill if under 12 characters

in length.

(016, 116, 216, 316, 416, 516, 616, 716)

4) Valid character combinations can include A through Z, 0 through 9,

hyphens, and/or blanks. For example, 89-123-SC is valid, but

89+123*SC is invalid.

(017, 117, 217, 317, 417, 517, 617, 717)

5) Must be blank right-fill if under 12 characters in length. Cannot

have embedded blanks between the first and last characters entered.

(015, 115, 215, 315, 415, 515, 615, 715)

6) For each submitting agency, as identified in “1 ORI NUMBER,”

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)

7) A Group “A” Incident Number and a Group “B” Arrest Report 

Arrest Transaction Number/Incident Number cannot have the same

number within the same ORI.

(088)

3 Incident Date/Hour

1) Must be present—cannot be blank.

(101)
Data Element Edits

20

2) 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.

(105)

3) When an ORI becomes inactive, no incident data may be submitted

to the FBI with an incident date on or after that date. However,

adjustments to previously submitted data may be made.

(118)

4) The date cannot be earlier than 01/01/1991 for I = Incident Report

submissions. This edit will preclude dates that are obviously

incorrect since the FBI began accepting data on this date.

(172)

5) At some point in time, the participant will convert its local agencies

from Summary reporting to Incident-Based 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 duplicated within both the Summary System 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 the September 1999, monthly magnetic media,

dates for incidents, recovered property, and arrests must be within

September. The exception occurs 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 can never have dates

prior to the initial start date of September 1999, except as 

mentioned previously. The Summary System 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. 
Data Element Edits

21

The state must maintain a table of start dates for each local agency

(ORI) within its state. As local agencies convert to IBR format, the

state would add the start date to its table. Any Incident Reports

submitted to the FBI must be rejected at the state level if the

incident date is earlier than this start date.

(171, 173)

6) The date cannot be later than the year and month the tape 

represents. For example, the May 1999 tape cannot contain 

incidents happening after this date.

(170)

7) The record control date in positions 7 through 12 (Month and

Year) and the incident date must be valid entries. The FBI software

uses these to determine if the complete incident should have been

reported to the FBI or if a subset of the segments should have been

submitted as Time-Window Submissions.

(175)

8) Administrative Segments (Level 1) submitted with a Segment

Action Type of W = Time-Window Submission cannot have a date

in Data Element 3 (Incident Date/Hour) which would be a valid

date for a Group “A” Incident. For any subsequent 

M = Modify of a previously submitted W = Time-Window 

Submission, this is also true.

(176)

9) Administrative Segments (Level 1) submitted with a segment 

Action Type of M = Modify cannot change the date in Data 

Element 3 (Incident Date/Hour) of segments which were 

previously submitted with a Segment Action Type of 

I = Incident Report. 

(161)

10) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify cannot change the Report Date 

Indicator (position 46 of the segment) of segments which were 
Data Element Edits

22

previously submitted with a Segment Action Type of 

I = Incident Report.

(162)

11) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify cannot change the hour in Data 

Element 3 (Incident Date/Hour) of segments which were 

previously submitted with a Segment Action Type of 

I = Incident Report.

(163)

12) If Hour is entered, it must be 00 through 23.

 Note: If the incident occurred at exactly midnight, the Incident

Date should be entered as if the time was 1 minute past

midnight. For example, if the crime occurred at exactly

midnight on Thursday, Friday’s date should be entered.

(152)

13) If the Incident Date is unknown, the report date should be used. 

Indicate a report date with an R in position 46 on the

Administrative Segment. If this is the Incident Date, then leave the

Report Indicator blank.

(151)

4 Cleared Exceptionally

1) Must be present—cannot be blank.

(101)

2) Must be a valid code.

(104)

3) Cannot be N = Not Applicable if Data Element 5 (Exceptional 

Clearance Date) is entered.

(153)
Data Element Edits

23

4) When a value other than N = Not Applicable is entered, there can

be no Arrestee Segments associated with the Group “A” Incident

Report. 

(071)

5) Administrative Segments (Level 1) submitted with a Segment 

Action Type of W = Time-Window Submission cannot contain an

N = Not Applicable in Data Element 4 (Cleared Exceptionally). 

(154)

6) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify must have an N = Not Applicable in

Data Element 4 (Exceptional Clearance Indicator) when arrestees

were already present for the Group “A” Incident Report.

(164)

7) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify cannot have an N = Not Applicable in

Data Element 4 (Exceptional Clearance Indicator) when the 

Incident was previously submitted as a W = Time-Window

Submission.

(165)

8) Administrative Segments (Level 1) submitted with a Segment 

Action Type of W = Time-Window Submission must contain Data

Elements 4 (Cleared Exceptionally) and 5 (Exceptional Clearance

Date). Both must be present to be a valid submission.

(157)

5 Exceptional Clearance Date

1) The clearance date cannot be earlier than the incident date.

(155)

2) Must be present if case was cleared exceptionally per data value 

code in Data Element 4 (Cleared Exceptionally).

(156)
Data Element Edits

24

3) 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 Tape

and Year of Tape fields on the data record. For example, if Month

of Tape and Year of Tape are 06/1999, the clearance date cannot

contain any date 07/01/1999 or later. 

(105)

4) Administrative Segments (Level 1) submitted with a Segment 

Action Type of W = Time-Window Submission must contain Data

Elements 4 (Cleared Exceptionally) and 5 (Exceptional Clearance

Date). Both must be present to be a valid submission.

(157)

5) Administrative Segments (Level 1) submitted with a Segment 

Action Type of W = Time-Window Submission cannot have an 

Exceptional Clearance Date (Data Element 5) earlier than the 

Time-Window Base Date. For any subsequent M = Modify of a

previously submitted W = Time-Window Submission, this is also

true. Volume 2, section I provides additional information on the

Base Date. 

(120)

6) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify with an N = Not Applicable in Data

Element 4 (Exceptional Clearance Indicator) cannot have an entry

in Data Element 5 (Exceptional Clearance Date).

(166)

7) Administrative Segments (Level 1) submitted with a Segment 

Action Type of M = Modify for a previously submitted W = 

Time-Window Submission must have a date in Data Element 5 

(Exceptional Clearance Date).

(167)
Data Element Edits

25

8) Administrative Segments (Level 1) submitted with a Segment 

Action Type of W = Time-Window Submission or M = Modify

cannot have a date earlier than the date the ORI went IBR.

(174)

2. Data Element—Offense Segment Edits

6 UCR Offense Code

1) Must be present—cannot be blank.

(201)

2) Must be a valid code.

(204)

3) Must be a Group “A” offense code.

(264)

7 Offense Attempted/Completed

1) Must be present—cannot be blank.

(201)

2) Must be a valid code of A = Attempted or C = Completed.

(251)

3) If A = Attempted is entered and Data Element 6 (UCR Offense 

Code) is a Crime Against Property, Gambling, Kidnaping, or 

Drug/Narcotic Offense, Data Element 14 (Type Property 

Loss/Etc.) must be 1 = None or 8 = Unknown. 

(077)

4) If Data Element 6 (UCR Offense Code) was a Crime Against 

Property, Kidnaping, Gambling, or Drug/Narcotic Offense, and

Data Element 7 (Offense Attempted/Completed) was C = Completed,
Data Element Edits

26

a Property Segment (Level 3) must be sent with a valid code in

Data Element 14 (Type Property Loss/Etc.).

(078)

5) If the UCR Offense Code is an Assault or Homicide Offense, the

offense must be C = Completed.

(256)

8 Offender(s) Suspected of Using

1) Must be present—cannot be blank.

(201)

2) Must be a valid code.

(204)

3) If more than one code entered, cannot be a duplicate.

(206)

4) Value N = Not Applicable is mutually exclusive with any other 

value entered, i.e., N is to be entered only if no other code applies.

(207)

8A Bias Motivation

1) Once a participant has added this data element into the Offense

Segment (Level 2), the field becomes mandatory and cannot be

blank. Conversely, if the participant has not yet adopted the data

element, then the FBI’s computer will not reject the submission. 

Rejection only occurs when the physical length of the Offense 

Segment includes the two-character field and it is blank.

(201)
Data Element Edits

27

2) Must be a valid code in conjunction with item 1 above.

(204)

9 Location Type

1) Must be present—cannot be blank.

(201)

2) Must be a valid code.

(204)

10 Number of Premises Entered

1) Must be entered if the UCR Offense Code is 220 (Burglary/B&E)

and Data Element 9 (Location Type) contains 14 =

Hotel/Motel/Etc. or 19 = Rental Storage Facility.

(257)

2) Must be numeric entry of 01-99 if entered.

(202)

3) When 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).

(252)

11 Method of Entry

1) Must be a valid code.

(204)

2) Must be entered when the UCR Offense Code is 220 Burglary.

(253)
Data Element Edits

28

3) Must not be entered when the UCR Offense Code is not 220 

Burglary.

(254)

12 Type Criminal Activity/Gang Information

1) Type criminal activity code of “B”, “C”, “D”, “E”, “O”, “P”, “T”,

or “U” must be present when the UCR Offense Code is:

250 = Counterfeiting/Forgery

280 = Stolen Property Offenses

35A = Drug/Narcotic Violations

35B = Drug Equipment Violations

39C = Gambling Equipment Violations

370 = Pornography/Obscene Material

520 = Weapon Law Violations

(201)

2) Must be a valid code.

(204)

3) If more than one code entered, cannot be a duplicate. This applies

to criminal activity codes and gang information codes.

(206)

4) Value N = None/Unknown is mutually exclusive with any other

gang information codes.

(207)

5) Type criminal activity codes of “B”, “C”, “D”, “E”, “O”, “P”, “T”,

or “U” can only be entered when the UCR Offense Code is:

250 = Counterfeiting/Forgery

280 = Stolen Property Offenses

35A = Drug/Narcotic Violations

35B = Drug Equipment Violations

39C = Gambling Equipment Violations

370 = Pornography/Obscene Material

520 = Weapon Law Violations

(219)
Data Element Edits

29

6) 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 = Kidnaping/Abduction

120 = Robbery

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

13A = Aggravated Assault

13B = Simple Assault

13C = Intimidation

(219)

13 Type Weapon/Force Involved

1) Must be present when the UCR Offense Code is:

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

09C = Justifiable Homicide

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion

520 = Weapon Law Violations

(201)

2) Must be a valid code.

(204)

3) If more than one code entered, cannot be a duplicate.

(206)
Data Element Edits

30

4) Value 99 = None is mutually exclusive with any other value, i.e., 99

is to be entered only if no other code applies.

(207)

5) Can only be entered when UCR Offense Code is:

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

09C = Justifiable Homicide

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion

520 = Weapon Law Violations

(219)

6) If the firearm is an Automatic, add A as the third character; valid

only with codes: 

11 = Firearm (Type Not Stated)

12 = Handgun

13 = Rifle

14 = Shotgun

15 = Other Firearm

(258)

7) The third character of the code must be A = Automatic or blank.

(255)

8) 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.

(265)
Data Element Edits

31

9) 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)

 10) 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)

3. Data Element—Property Segment Edits

14 Type Property Loss/Etc.

1) Must be present—cannot be blank.

(301)

2) Must be a valid code.

(304)

3) If 1 = None or 8 = Unknown, Data Elements 15 through 22 must 

be blank. The exception occurs when the offense is a 35A. In this

case, if 1 = None is entered, then Data Element 20 (Suspected Drug

Type) should be completed.

(352)

4) If 5 = Recovered, every property description code entered into 

Data Element 15 (Property Description) must also have been 

reported as 7 = Stolen/Etc. within that same incident. This applies

to both initial submissions and resubmissions for incident reports

with Segment Action Type of I = Incident Report. This does not

apply, of course, for offenses that allow recovered property without

being first stolen within that same incident, i.e. Counterfeiting/

Forgery and Stolen Property Offenses. Nor does it apply when

Property Description 38 = Vehicle Parts/Accessories are

subsequently reported as recovered when a vehicle was stolen. 

(072)
Data Element Edits

32

5) If code is 2 = Burned, 3 = Counterfeited/Forged, 4 = Destroyed/

Damaged/Vandalized, 5 = Recovered, 6 = Seized, or 7 = Stolen/

Etc., Data Elements 15-22 must have applicable entries in the 

segment. 

(372)

6) When submitting Segment Action Type of W = Time-Window

Submission or M = Modify, Data Element 14 (Type Property 

Loss/Etc.) must be 5 = Recovered. 

(378)

15 Property Description

1) Must be a valid code.

(304)

2) If more than one code entered, cannot be a duplicate.

(306)

3) If 88 = Pending Inventory is entered, then Data Element 16 (Value

of Property) must be 1 = Unknown ($1.00). One dollar is used as a

quality assurance edit check that instructs the FBI’s computer to

accept the 88 entry.

(353)

4) At least one 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. 

(375)
Data Element Edits

33

5) If 5 = Recovered, every property description code entered into 

Data Element 15 (Property Description) must also have been 

reported as 7 = Stolen/Etc. within that same incident. This applies

to both initial submissions and resubmissions for incident reports

with Segment Action Type I = Incident Report.

This does not apply, of course, to offenses that allow recovered

property without first being stolen within that same incident. Nor

does it apply when Property Description 38 = Vehicle Parts/

Accessories is subsequently reported as recovered when a vehicle

was stolen.

(072)

16 Value of Property

1) Must be numeric entry with zero left-fill if entered.

(302)

2) If value is unknown, must have value of 1 = Unknown ($1.00). A

value of zero is allowable only for property description codes of:

09 = Credit/Debit Cards

22 = Nonnegotiable Instruments

77 = Other

99 = (Special Category)

Note: Codes 09 and 22 require a zero value be submitted.

(351)

3) If Data Element 15 (Property Description) has a code of 09 = 

Credit/Debit Cards or 22 = Nonnegotiable Instruments, a zero 

value is required for Data Element 16 (Value of Property). 

(391)

4) If a value is entered, then Data Element 15 (Property Description)

must be entered.

(354)
Data Element Edits

34

5) If Data Element 15 (Property Description) code is 10 = 

Drugs/Narcotics and the only offense submitted is 35A = 

Drug/Narcotic Violations, the property value must be blank. 

However, if there are multiple property offenses submitted, do not

include the value of any 10 = Drugs/Narcotics pertaining to 35A in

this data element, but do include the value of these drugs that apply

to non-35A offenses. 

Note: If any offense other than 35A has a 10 = Drugs/Narcotics

entry, the value for this property must be entered in Data

Element 16 (Value of Property). 

(383)

6) 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. 

(084)

7) When Data Element 16 (Property Value) 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, a warning message will be generated. In this case, the

cents were entered as whole dollars. 

(342) 

17 Date Recovered

1) 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 Tape and
Data Element Edits

35

Year of Tape fields on the data record. For example, if Month of

Tape and Year of Tape are 06/1999, the recovered date cannot

contain any date 07/01/1999 or later. 

(305)

2) Cannot be earlier than Data Element 3 (Incident Date/Hour).

(305)

3) If entered, then both Data Elements 15 (Property Description) and

16 (Value of Property) must be entered.

(356)

4) If entered, Data Element 14 (Property Type Loss/Etc.) must be 

5 = Recovered.

(355)

5) Property Segments (Level 3) submitted with a Segment Action 

Type of W = Time-Window Submission cannot have a Date 

Recovered (Data Element 17) before the date which is calculated

using the base date technique (January 1 of the year prior to the

current year, or earlier than the date the agency went IBR). For

any subsequent M = Modify of a previously submitted W = 

Time-Window

Submission, this edit also applies.

(320)

18 Number of Stolen Motor Vehicles

1) Must be numeric entry with zero left-fill if entered.

(302)

2) Must be entered for and is only applicable to UCR Offense Code

240 = Motor Vehicle Theft. Data Element 14 (Type Property

Loss/Etc.) must be 7 = Stolen/Etc., and Data Element 7 (Offense

Attempted/Completed) must also be C = Completed. Motor

vehicles taken as the proceeds of other offenses; i.e., Burglary,

Fraud, Embezzlement, etc. should not be included. 
Data Element Edits

36

(357)

3) Entry must be made 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.

(358)

4) Data Element 15 (Property Description) must contain at least one

of the following vehicle codes for:

03 = Automobiles

05 = Buses

24 = Other Motor Vehicles

28 = Recreational Vehicles

37 = Trucks

(359)

5) If more than one vehicle code is entered in Data Element 15 

(Property Description), entry must be equal to or greater than this

number of different codes, unless the number of stolen vehicles is

unknown (00).

(388)

19 Number of Recovered Motor Vehicles

1) Must be numeric entry with zero left-fill if entered.

(302)

2) Must be entered for and is only applicable to UCR Offense Code

240 = Motor Vehicle Theft when Data Element 14 (Type Property

Loss/Etc.) is 5 = Recovered. Motor vehicles taken as the proceeds

of other offenses; i.e., Burglary, Fraud, Embezzlement, etc. should

not be included. 

(360)

3) When entry is 01 to 99, it must be equal to or less than the number

stolen. 
Data Element Edits

37

(073)

4) Entry must be made 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 15 (Property 

Description) contains a vehicle code.

(361)

5) When entry is 01 to 99, Data Element 15 (Property Description) 

must contain at least one of the following vehicle codes:

03 = Automobiles

05 = Buses

24 = Other Motor Vehicles

28 = Recreational Vehicles

37 = Trucks

(359)

6) If more than one vehicle code is entered in Data Element 15 

(Property Description), entry must be equal to or greater than this

number of different codes, unless the number of recovered vehicles

is unknown (00).

(389)

20 Suspected Drug Type

1) Must be entered when there is a UCR Offense Code of 35A =

Drug/Narcotic Violations, 6 = Seized was entered into Data

Element 14 (Type Property Loss/Etc.), and 10 = Drugs/Narcotics

was entered in Data Element 15 (Property Description).

(301)

If there are other offenses involved and 10 = Drugs/Narcotics was

split between offense 35A = Drug/Narcotic Violations and other

offenses, enter only the drug types applicable to 35A.

(365)

2) If more than one code is entered, the same code cannot be entered 
Data Element Edits

38

within the same Type Measurement category in Data Element 22.

In other words, cocaine cannot be reported in grams and pounds

(same weight category), but can be reported in grams and liters

(weight and capacity categories). For the drug type of U =

Unknown, this does not apply; U = Unknown can be entered only

once.

(306)

3) Must be a valid code. 

(304)

4) When Data Element 6 (UCR Offense Code) is 35A =

Drug/Narcotic Violations, 14 (Type Property Loss/Etc.) is 6 =

Seized, 15 (Type Property Loss/Etc.) is 10 = Drugs, and Data

Element 20 (Suspected Drug Type) is entered, both Data Element

21 (Estimated Quantity) and 22 (Type Measurement) must be

entered. 

(364)

5) If X = Over 3 Drug Types, two other codes must also be entered.

(362)

6) If X = Over 3 Drug Types is entered, Data Elements 21 and 22 

must be blank.

(363)

7) When the offense is 35A Drug/Narcotic Violations and Data 

Element 14 (Type Property Loss/Etc.) is 1 = None, Data Element

20 (Suspected Drug Type) is required. If 6 = Seized was also

reported, this edit is bypassed.

(392)

21 Estimated Drug Quantity

1) Must be numeric entry with zero left-fill. The decimal fractional

quantity, if entered, must be expressed in thousandths as three

digits.
Data Element Edits

39

(302)

2) If entered, Data Elements 20 (Suspected Drug Type) and 22 (Type

Drug Measurement) must also be entered.

(366)

22 Type Drug Measurement

1) Must be a valid code.

(304)

2) 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 Type Drug Measurement codes are applicable to any Data

Element 20 (Suspected Drug Type) code.

(367)

3) If entered, Data Elements 20 (Suspected Drug Type) and 21 

(Estimated Drug Quantity) must also be completed.

(368)

4) Data Element 21 (Estimated Quantity) must have a value of 1 

when XX = Not Reported is entered for Data Element 22 (Type 

Measurement). Submission of a Not Reported indication requires

that a value of 1 also be submitted as a quality assurance check. 

Once the Type Measurement has been determined, a Group “A”

Incident Report would be resubmitted reflecting the completed

data.

(384)
Data Element Edits

40

4. Data Element—Victim Segment Edits

23 Victim (Sequence) Number

1) Must be present— cannot be blank.

(401)

2) Must be numeric entry (001 through 999) with zero left-fill. The

purpose of the field is to distinguish one victim from another. 

(402)

24 Victim Connected to UCR Offense Code(s)

1) Must be present—cannot be blank.

(401)

2) Must be a valid code.

(404)

3) If more than one code entered, cannot be a duplicate.

(406)

4) If the Offense Code is a Crime Against Person, Data Element 25 

(Type of Victim) must be I = Individual. 

(464)

5) If the Offense Code is a Crime Against Society, Data Element 25

(Type of Victim) must be S = Society. 

(465)

6) If the Offense Code is a Crime Against Property, Data Element 25

(Type of Victim) cannot be S = Society. 

(467)
Data Element Edits

41

7) Each Offense Code entered must have a corresponding Offense 

Segment. 

(466)

8) Certain Offense Codes cannot occur to the same victim in the same 

incident by UCR definitions (mutually exclusive), while others are

an element of another offense and should not be reported as having 

happened to the victim along with that offense (Lesser Included). 

The chart presented in section III, error number 478, shows the

invalid combinations.

(478)

25 Type of Victim

1) Must be present—cannot be blank.

(401)

2) Must be a valid code. 

(404)

26 Age of Victim

1) Must be present if Data Element 25 (Type of Victim) is I = Individual.

(453)

2) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

3) If Data Element 35 (Relationship of Victim to Offender) contains a

relationship of SE = Spouse, then the victim cannot be less than 10 

years old.

(450)
Data Element Edits

42

4) Exact Age

a) Must be a valid code if alpha characters, i.e., NN, NB, or BB.

 (404)

b) A single two-character age must be in first two positions of the 

 field, not the third and fourth.

 (408)

5) Age Range

The FBI’s computer will store the average age, rounded down. For

example, if the range is 16 through 19, average is 17.5 years old

and is stored as 17 years.

a) Must be four numeric digits.

 (409)

b) First pair must be less than second pair.

 (410)

c) The low age in a range cannot be 00 (unknown).

 (422)

6) When the offense is 36B Statutory Rape, the victim’s age cannot 

exceed the maximum age possible based upon the state statute for

this offense.

(481)

27 Sex of Victim

1) Must be a valid code. 

(404)
Data Element Edits

43

2) Must be present if Data Element 25 (Type of Victim) is I = Individual.

(453)

3) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

28 Race of Victim

1) Must be a valid code.

(404)

2) Must be present if Data Element 25 (Type of Victim) is I = Individual.

(453)

3) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

29 Ethnicity of Victim

1) Must be a valid code.

(404)

2) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

30 Resident Status of Victim

1) Must be a valid code.

(404)
Data Element Edits

44

2) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

31 Aggravated Assault/Homicide Circumstances

1) Must be a valid code.

(404)

2) If more than one code entered within Aggravated Assault/Murder 

category, cannot be a duplicate.

(406)

3) Can only be entered when one or more Data Element 24 (Victim 

Connected to UCR Offense Codes) entries are:

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

09C = Justifiable Homicide

13A = Aggravated Assault

(419)

4) If 20 = Criminal Killed by Private Citizen or 21 = Criminal Killed by

Police Officer is entered, then Data Element 32 (Additional 

Justifiable Homicide Circumstances) must be entered.

(455)

5) Value 10 = Unknown Circumstances is mutually exclusive with any

other code—no other code can be entered. Enter 10 only if no

other code applies.

(456)

6) No more than one circumstance category (i.e., Aggravated

Assault, Negligent Manslaughter, etc.) can be entered.

(456)
Data Element Edits

45

7) When 08 = Other Felony Involved is entered, a minimum of two 

offenses must be entered for Data Element 6 (UCR Offense Code)

or a minimum of two individual victims must be submitted for the

incident.

(480)

8) The Aggravated Assault/Homicide Circumstance Code must be 

valid for the offense the victim was connected to. Refer to 

Volume 1: Data Collection Guidelines, section VI, Data Element

31 for a complete list of the values appropriate for the particular

offense.

(462, 463, 477)

32 Additional Justifiable Homicide Circumstances

1) Must be a valid code.

(404)

2) If it is entered, Data Element 31 (Aggravated Assault/Homicide 

Circumstances) must show a justifiable homicide circumstance, i.e.,

code 20 or 21.

(457)

33 Type Injury

1) Must be present when the UCR Offense Code is:

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion/Blackmail

(401)
Data Element Edits

46

2) Must be a valid code.

(404)

3) If more than one code entered, cannot be a duplicate.

(406)

4) Value N = None is mutually exclusive with any other value entered,

i.e., N is to be used only if no other code applies.

(407)

5) Can only be entered when one or more Data Element 24 (Victim

Connected to UCR Offense Codes) entries are:

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion/Blackmail

(419)

6) When Data Element 24 (Victim Connected to UCR Offense 

Codes) is 13B = Simple Assault, there cannot be major injury 

codes which would indicate an aggravated assault. The permissible

codes are M = Apparent Minor Injury and N = None. If an

additional offense is connected to the victim involving injury, major

injury codes are permitted.

(479)

34 Offender Number(s) to be Related

1) Enter only if one or more of the offenses entered into Data Element

24 [Victim Connected to UCR Offense Code(s)] is a Crime 

Against Person or is a Robbery Offense (120). If more than 10 
Data Element Edits

47

offenders satisfy this criteria, choose the 10 closest in relationship. 

For example, if 15 offenders were neighbors and 1 was the brother,

enter the brother as 1 of the 10 offenders in this data element.

(459)

2) Must be numeric entry with zero left-fill if entered.

(402)

3) Data Element 25 (Type of Victim) must be I = Individual for data

to be entered.

(458)

4) If more than one number entered, cannot be a duplicate.

(406)

5) 00 may only be entered if there is only one Offender Segment

submitted where nothing was known about identity and number of

offender(s). For additional information, refer to Volume 2, section I.

(468)

6) The corresponding Offender Segment must be present.

(070)

35 Relationship(s) of Victim to Offender(s)

1) Every offender indicated in Data Element 34 [Offender Number(s)

to be Related] requires an entry here except when the number is 00

(Unknown). This field must be blank in instances when 00 is

entered.

(460)

2) Must be a valid code.

(404)
Data Element Edits

48

3) Husbands and wives (i.e., spouses) must be at least 10 years of age.

(450, 550)

4) The sex of the victim and/or offender must reflect the implied 

relationship. The following relationships must reflect either the

Same or Different sex codes depending upon this relationship:

Relationship Sex Code

BG = Victim was Boyfriend/

 Girlfriend Different

XS = Victim was Ex-Spouse Different

SE = Victim was Spouse Different

CS = Victim was Common-Law

Spouse Different

HR = Homosexual Relationship Same

(553)

5) The age of the victim and/or the offender must reflect the implied

relationship. The following relationships must be consistent with

the victim’s age in relation to the offender’s age:

Relationship Victim’s Age Is

CH = Victim was Child Younger

PA = Victim was Parent Older

GP = Victim was Grandparent Older

GC = Victim was Grandchild Younger

(554)

6) Relationship cannot be entered when Data Element 34 (Offender

Number to be Related) is 00 = Unknown.

(468)

7) When VO = Victim Was Offender is entered, a minimum of two

Victim and two Offender Segments must be submitted. VO 

indicates situations such as brawls and domestic disputes. In most

cases, each victim is also the offender; therefore, every victim
Data Element Edits

49

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)

8) When entered, VO = Victim Was Offender can only be entered 

once in a victim record and can refer to an offender only once. A 

single victim cannot be two offenders.

(471, 474)

9) When the related offender has unknown values entered for Age, 

Sex, and Race, the relationship must be RU = Relationship

Unknown. This edit ensures a logical relationship, e.g., if brother

was entered, age, sex, and race would not be unknown values.

(472)

10) In a multiple offender incident, a victim cannot have a relationship

of SE = Spouse to more than one offender.

(475)

11) In a multiple victim incident, two or more victims cannot have a

victim relationship of SE = Spouse to the same offender.

(476)

5. Data Element—Offender Segment Edits

36 Offender (Sequence) Number

1) Must be present—cannot be blank.

(501)

2) Must be numeric entry with zero left-fill. The purpose of the field

is to distinguish one offender from another and to identify the

situation where nothing was known about the number of offenders

or who they were. For example, if a corpse was found in a ditch

and there were no eyewitnesses or other information that would
Data Element Edits

50

provide data about possible offenders, 00 = Unknown would be

entered. However, if five offenders were seen running from the

scene, then five offender records would be submitted.

(502)

3) If the incident is exceptionally cleared, then 00 cannot be entered. 

00 indicates that nothing was known about the offender(s)

regarding number and any identifying information. One of the

criteria for exceptionally clearing an incident is that at least one of

the offenders be known.

(557)

4) For a Justifiable Homicide (UCR Offense Code 09C), at least one

of the offenders must have known information for Age, Sex, and 

Race. Consequently, 00 is not valid as an offender sequence number.

(559)

5) If the number is 00 = Unknown, no other Offender Segments can

be submitted.

(555)

37 Age of Offender

1) Must be present when Data Element 36 (Offender Sequence 

Number) is other than 00 = Unknown.

(501)

2) Cannot be entered when Data Element 36 (Offender Sequence 

Number) is 00 = Unknown.

(552)

3) When an incident is cleared exceptionally, at least one of the 

offenders must have known values in Age, Sex, and Race.

(558)
Data Element Edits

51

4) For a Justifiable Homicide (UCR Offense Code 09C), at least one

of the offenders must have known information for Age, Sex, and

Race.

(559)

5) If Data Element 35 (Relationship of Victim to Offender) contains a

relationship of SE = Spouse, then the offender cannot be less than

10 years old.

(550)

6) Exact Age

a) Must contain numeric entry of 00 through 99.

 (556)

b) A single two-character age must be in the first two positions of

 the field, not the third and fourth.

 (508)

7) Age Range

The FBI’s computer will store the average age, rounded down. For

example, if the range is 16 through 19, average is 17.5 years old

and is stored as 17 years.

a) Must be four numeric digits.

 (509)

b) First pair must be less than second pair.

 (510)

c) The low age in a range cannot be 00 (unknown).

 (522)
Data Element Edits

52

38 Sex of Offender

1) Must be present when Data Element 36 (Offender Sequence

Number) is other than 00 = Unknown.

(501)

2) Must be a valid code.

(504)

3) Cannot be entered when Data Element 36 (Offender Sequence

Number) is 00 = Unknown.

(552)

4) When an incident is cleared exceptionally, at least one of the

offenders must have known values in Age, Sex, and Race.

(558)

5) For a Justifiable Homicide (UCR Offense Code 09C), at least one

of the offenders must have known information for Age, Sex, and

Race.

(559)

6) For a Forcible Rape (UCR Offense Code 11A) or a Statutory Rape

(UCR Offense Code 36B), one or more of the offenders must have

a different sex than the rape victim.

(560)

39 Race of Offender

1) Must be present when Data Element 36 (Offender Sequence

Number) is other than 00 = Unknown.

(501)

2) Must be a valid code.

(504)
Data Element Edits

53

3) Cannot be entered when Data Element 36 (Offender Sequence

Number) is 00 = Unknown.

(552)

4) When an incident is cleared exceptionally, at least one of the

offenders must have known values in Age, Sex, and Race.

(558)

5) For a Justifiable Homicide (UCR Offense Code 09C), at least one

of the offenders must have known information for Age, Sex, and

Race.

(559)

6. Data Element—Arrestee Segment Edits

Data Elements associated with a Group “A” Incident Report (Segment

Level 6) are the same as those in a Group “B” Arrest Report (Segment

Level 7). The exception is Data Element 44 (Multiple Arrestee

Segments Indicator) which is not submitted in a Group “B” Arrest

Report. The first digit of each error number refers to the applicable

Segment Level, i.e., 6xx or 7xx.

40 Arrestee (Sequence) Number

1) Must be present—cannot be blank.

(601, 701)

2) Must be numeric entry of 01 to 99 with zero left-fill.

(602, 702)

41 Arrest (Transaction) Number

1) Must be present—cannot be blank.

(601, 701)
Data Element Edits

54

2) Must be left-justified with blank right-fill if under 12 characters in

length.

(616, 716)

3) Valid character combinations can include A through Z, 0 through 9,

hyphens, and/or blanks. For example, 89-123-SC is valid, but

89+123*SC is invalid.

(617, 717)

4) Must be blank right-fill if under 12 characters in length. Cannot

have embedded blanks between the first and last characters entered.

(615, 715)

42 Arrest Date

1) Must be present—cannot be blank.

(601, 701)

2) 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 Tape

and Year of Tape fields on the data record. For example, if Month

of Tape and Year of Tape are 06/1999, the arrest date cannot

contain any date 07/01/1999 or later.

(605, 705)

3) Cannot be earlier than Data Element 3 (Incident Date/Hour).

(665)

4) Arrestee Segments (Level 6) submitted with a Segment Action
Data Element Edits

55

Type of W = Time-Window Submission cannot have Data Element

42 (Arrest Date) earlier than the Base Date. This also applies to

any subsequent M = Modify of a previously submitted W =

Time-Window Submission. The date edit also applies to Group

“B” submissions.

(620, 720)

43 Type of Arrest

1) Must be present—cannot be blank.

(601, 701)

2) Must be a valid code.

(604, 704)

44 Multiple Arrestee Segments Indicator

1) Must be present—cannot be blank.

(601)

2) Must be a valid code.

(604)

45 UCR Arrest Offense Code

1) Must be present—cannot be blank.

(601, 701)

2) Must be a valid code. This code does not have to match one of the

code(s) entered for Data Element 6 (UCR Offense Code) within

Offense Segment(s) submitted in a Group “A” Incident Report.

(604, 704)
Data Element Edits

56

3) The UCR Arrest Offense Code cannot be 09C = Justifiable

Homicide because this offense does not result in a subsequent arrest

of the offender.

(670)

46 Arrestee Was Armed With

1) Must be present—cannot be blank.

(601, 701)

2) Must be a valid code.

(604, 704)

3) If more than one code entered, cannot be a duplicate.

(606, 706)

4) Value 01 = Unarmed is mutually exclusive with any other value,

i.e., it is to be used only if no other code applies.

(607, 707)

5) The third character must be A = Automatic or blank.

(654, 754)

6) If the firearm is Automatic, add A as the third character of code;

valid only with codes:

11 = Firearm (Type Not Stated)

12 = Handgun

13 = Rifle

14 = Shotgun

15 = Other Firearm

(655, 755)
Data Element Edits

57

47 Age of Arrestee

1) Must be present—cannot be blank.

(601, 701)

2) If age is under 18, then Data Element 52 (Disposition of Arrestee

Under 18) must be entered.

(652, 752)

3) Exact Age

a) Must contain numeric entry of 00 through 99.

 (664, 757)

b) A single two-character age must be in first two positions of 

 the field, not the third and fourth.

 (608, 708)

c) When the age is unknown, do not confuse 99 = Over 98

 Years Old with 00 = Unknown. Whenever 99 is entered, a 

 warning message is produced.

 (641, 741)

4) Age Range

The FBI’s computer will store the average age, rounded down. For

example, if the range is 16 through 19, average is 17.5 years old

and is stored as 17 years.

a) Must be four numeric digits.

 (609, 709)

b) First pair must be less than second pair.

 (610, 710)
Data Element Edits

58

c) The low age in a range cannot be 00 (unknown).

 (622, 722)

48 Sex of Arrestee

1) Must be present—cannot be blank.

(601, 701)

2) Must be a valid code. Although U = Unknown is a valid code for

victim and offender sex, it is not valid for arrestees.

(667, 758)

49 Race of Arrestee

1) Must be present—cannot be blank.

(601, 701)

2) Must be a valid code.

(604, 704)

50 Ethnicity of Arrestee

If entered, must be a valid code.

(604, 704)

51 Resident Status of Arrestee

If entered, must be a valid code.

(604, 704)

52 Disposition of Arrestee Under 18

1) Must be a valid code.

 (604, 704)
Data Element Edits

59

2) Must be entered if arrestee age is under 18.

(652, 752)

3) Cannot be entered if arrestee age is over 17.

(653, 753)

4) If not entered but Data Element 47 (Age of Arrestee) reflected an

age-range for a juvenile, a warning message will be generated. 

This only happens when the low age is a juvenile and the high age

is an adult, but the average age is a juvenile.

(640, 740)

7. Data Element—Zero-reporting Segment Edits

Month Zero-reporting Month

The month entered into positions 38 through 39 on Segment Level 0

must be a valid month of 01 through 12.

(090)

Year Zero-reporting Year

The year entered into positions 40 through 43 on Segment Level 0

must be four numeric digits.

(091)

Incident Zero-reporting Incident Number

The incident number entered into positions 26 through 37 on

Segment Level 0 must be 12 zeros.

(092)

 Month/Year Zero-reporting Month/Year

The month and year entered into positions 38 through 43 on Segment

Level 0 cannot be earlier than January 1 of the previous calendar

year, or before the date the agency converted over to NIBRS.

(093)

Additionally, the month and year entered into positions 38 through 43
Data Element Edits

60

cannot exceed the Month of Tape and Year of Tape entered into

positions 7 through 12.

(094)

C. Global Edits

The following edits look at the incident as a whole, rather than at a specific data element

and reflect relationships among segments that must be addressed within the participant’s software. 

The edits are grouped by category. The capitalized heading associated with each 

sequentially numbered edit requirement reflects the general edit, with full explanation provided

beneath it. The number in parentheses following each edit description is the corresponding error

number that will be generated by the FBI’s software if the error condition is found.

General Category

1. DUPLICATE SEGMENTS NOT ALLOWED

When a Group “A” Incident Report is submitted, the individual segments comprising the

incident cannot contain duplicates. For example, if two Offense Segments have the same value

for Data Element 6 (UCR Offense Code), or if two Property Segments have the same code

entered in Data Element 14 (Type Property Loss/Etc.), an error will be detected.

(262, 376, 451, 551)

2. SEGMENT ACTION TYPES MUST AGREE WITH SEGMENT LEVEL

The values of I = Incident Report, A = Add Arrest, M = Modify, W = Time-Window

Submission, and D = Delete must be applicable to appropriate Segment Levels (0 through 7) as

shown:

Action Valid Only With These Levels

I Segment levels 1 through 6

A 0 = Zero-Reporting Segment

 6 = Arrestee Segment

 7 = Group “B” Arrest Report

M 1 = Administrative Segment

*3 = Property Segment

*6 = Arrestee Segment

 7 = Group “B” Arrest Report

W 1 = Administrative Segment
Data Element Edits

61

 3 = Property Segment

 6 = Arrestee Segment

D 0 = Zero-Reporting Segment

 1 = Administrative Segment

*3 = Property Segment

*6 = Arrestee Segment

 7 = Group “B” Arrest Report

*Valid only when previously submitted as W.

 (057)

3. CANNOT HAVE DUPLICATE REPORTS SUBMITTED

Submitting two Group “A” Incident Reports having the same ORI and Incident Number

will generate an “Incident Already on File” error condition (i.e., duplicate incident report). 

Ensure that each participant uses unique incident numbers within the ORI.

(056)

4. GROUP “A” INCIDENT REPORTS MUST HAVE A LEVEL 1 SEGMENT

The first level within an I = Incident Report must be the Administrative Segment (Level 

1).

(055)

5. GROUP “A” INCIDENT REPORTS REQUIRE MINIMUM OF FOUR SEGMENTS

If an I = Incident Report is submitted, the following segments must be included:

Administrative Segment; Offense Segment; Victim Segment; and Offender Segment.

(075)

6. 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, if four Offender Segments are submitted, the sequence numbers

would normally be 01, 02, 03, and 04; but could be 02, 03, 05, and 07.
Data Element Edits

62

The gaps in numbers could occur, for instance, where all offenders had initially been

entered into the participant’s database with consecutive sequence numbers. Then, one of the

offenders was 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 Numbers to be Related).

(none)

7. RECORDS MUST BE ON THE FBI’S DATABASE TO BE MODIFIED

When submitting a transaction to M = Modify an existing segment on the FBI’s database,

the record to be modified must have been successfully added to the FBI’s database in a prior

submission.

The modify transaction implies that Exceptional Clearance, Recovered Property, and/or

Arrestee Segments had previously been submitted as W = Time-Window Submissions. Data no

longer maintained will be removed from the FBI’s database and stored on permanent backup

tapes. This archival mechanism may also create Time-Window Segments in which the participant

could submit modify transactions as necessary. Additional information regarding Time-Window

Segments and the methodology the FBI uses to delete Group “A” Incident Reports after archiving

them to backup can be found in Volume 2, section I. 

(053)

8. THE FBI PROCESSING DATE CANNOT BE BEFORE THE DATE THE MAGNETIC

 MEDIA REPRESENTS

The Month/Year in positions 7 through 12 of each record cannot be after the month and

year the FBI processes the magnetic media.

(060)

9. ALL SEGMENTS ON THE MAGNETIC MEDIA MUST HAVE THE SAME CONTROL

 INFORMATION

Each segment on the magnetic media submitted to the FBI must contain the same Month

of Tape and Year of Tape values in positions 7 through 12. The first segment processed will be

compared with all other segments to check for this condition.

(058)
Data Element Edits

63

10. ONLY ONE MONTHLY MAGNETIC MEDIA PER MONTH CAN BE SUBMITTED

Once a monthly submission has been processed by the FBI, the participant cannot submit

another magnetic media having the same values for Month of Tape and Year of Tape. The next

submission would contain the value for the next month. Although an error message is not

produced in this situation, control mechanisms are in place that will detect this situation

operationally, and the FBI’s UCR staff would then investigate the facts concerning this duplication.

(none)

11. ALL SEGMENTS MUST BE FROM SAME STATE

For nonfederal participants, all segments on the submitted tape must be from the same

state. This will be checked by comparing the two-character state abbreviation in Data Element 1

(ORI Number); all must have the same value.

(059)

12. ALL SEGMENTS FOR AN INCIDENT MUST BE IN NUMERIC ORDER

All segments for a Group “A” Incident Report must be in numeric 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)

13. VALID RECORD LEVELS ARE 0 THRU 7 AND L

Every record submitted must have a valid record level as reflected above. Levels 1

through 7 are for Group “A” Incident Reports and Group “B” Arrest Reports, Level L for Law

Enforcement Officers Killed and Assaulted (LEOKA), and Level 0 for Zero-Reporting.

(051)

14. WHEN WINDOW SEGMENTS HAVE PREVIOUSLY BEEN SUBMITTED, DO NOT 

 SUBMIT A GROUP “A” INCIDENT REPORT

Before a Group “A” Incident Report is added to a file, the software checks for the

presence of any Time-Window Segments on file, i.e., an Exceptional Clearance Administrative

Segment, a Recovered Property Segment, or an Arrestee Segment. If any are present, the

submission is rejected. To reduce the chance of this error occurring, participant’s software should

address the following circumstances that could cause the error: (1) The participant previously

submitted Time-Window Segments and then submitted the complete
Data Element Edits

64

Group “A” Incident Report; and (2) the participant’s computer was not programmed properly to

account for the FBI’s purge process. (During the FBI’s annual purge of 2-year-old incidents,

Window records were created as specified in Volume 2, section I; computers must account for

this purge.)

(087)

Administrative Segment Edits

15. EXCEPTIONALLY CLEARED SUBMISSIONS REQUIRE TWO DATA ELEMENTS

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission must contain Data Elements 4 (Cleared Exceptionally) and 5

(Exceptional Clearance Date).

(157)

16. DATA RECEIVED PRIOR TO BASE DATE WILL BE REJECTED

Specifications concerning the FBI’s 2-year database can be found in Volume 2, section I.

If an I = Incident Report was submitted with a date entered into Data Element 3 (Incident

Date/Hour) that is outside the base-date calculation reflected in the above documentation, the

incident will be rejected. For example, if the Month of Tape and Year of Tape contains a value of

01/1999, but the incident date is 12/25/1997, the segment will be rejected. The exception occurs

when an exceptional clearance is being submitted with a Segment Action Type of W =

Time-Window Submission. The incident date may be any past date but cannot be any earlier than

January 1, 1950.

(171)

17. TIME-WINDOW SEGMENT BEING MODIFIED MUST HAVE OFFENSE CODE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify for a previously submitted W = Time-Window Submission must have at least one

UCR Offense Code in the Window UCR Offense Code section starting in position 58.

(169)

18. INCIDENTS BEING MODIFIED MUST BE ON FILE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify must already be on the FBI file with Data Element 1 (ORI Number) and Data

Element 2 (Incident Number). The participant’s software must be able to determine this.

(160)
Data Element Edits

65

19. SEGMENT ACTION TYPE W MUST HAVE OFFENSE(S) ENTERED

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission must have at least one UCR Offense Code entered in the Window

UCR Offense Code section starting in position 58.

(158)

Also, offenses must be Group “A” offenses, not Group “B.”

(177)

20. POSITIONS 58-87 MUST BE BLANK FOR GROUP “A” INCIDENT REPORTS

Administrative Segments (Level 1) submitted with a Segment Action Type that is not 

W = Time-Window Submission cannot have an entry in the Window UCR Offense Code section

starting in position 58.

(159)

21. GROUP “A” CANNOT HAVE OFFENSES IN POSITIONS 58-87 ON TAPE SEGMENT

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify for a previously submitted I = Incident Report cannot have any entries in the

Window Offense Code section starting in position 58.

(168)

22. INCIDENT DATE CANNOT BE AFTER YEAR [yyyy] and MONTH [mm] OF TAPE

The date entered into Data Element 3 (Incident Date/Hour) cannot be later than that

entered within the Month of Tape and Year of Tape fields on the data record. For example, if

Month of Tape and Year of Tape are 06/1999, Data Element 3 then could not contain any date

07/01/1999 or later. On the other hand, this date can be earlier than 06/1999, thus including

crimes occurring in previous months.

(170)

23. NIBRS DATA RECEIVED FOR AN ORI FROM WHICH SUMMARY DATA WERE

 PREVIOUSLY RECEIVED WILL BE REJECTED

At some point, the participant will convert its local agencies from Summary reporting to

Incident-Based Reporting (IBR). Once the participant starts to send IBR 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 FBI’s Summary System and NIBRS for the same month will

be rejected by the FBI.
Data Element Edits

66

In other words, if the participant sends IBR data for an agency for the first time on the

September 1999, monthly tape, 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 Summary System already contains

aggregate data for the months prior to IBR 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. 

(173)

Offense Segment Edits 

24. ONLY 10 OFFENSES PER GROUP “A” INCIDENT REPORT ALLOWED

The maximum number of offenses that can be submitted for a Group “A” Incident Report

is ten.

(263)

25. EACH OFFENSE SEGMENT MUST HAVE A VICTIM SEGMENT LINKED TO IT

Each Offense Segment must have at least one Victim Segment pointing to it via Data

Element 24 (Victim Connected to UCR Offense Codes). An Offense Segment cannot stand

alone; it must have at least one Victim Segment linked to it.

(065)

Property Segment Edits

26. PROPERTY OFFENSES MUST HAVE A PROPERTY SEGMENT

If an I = Incident Report is submitted that contains an Offense Segment for an offense of

Crime Against Property, Kidnaping, Gambling, or Drug/Narcotic Offense, a Property Segment

must also be submitted.

(074)
Data Element Edits

67

27. DRUG PROPERTY SEGMENT MUST HAVE AN OFFENSE SEGMENT FOR UCR

 OFFENSE CODE 35A

If a Property Segment containing 10 = Drugs/Narcotics for Data Element 15 (Property

Description) is submitted and Data Element 16 (Value of Property) is blank, there must be an

Offense Segment for 35A = Drug/Narcotic Violations.

(382)

28. OFFENSES FOR “W” ACTION SEGMENTS PERTAINING TO RECOVERED PROPERTY

 MUST BE OFFENSES THAT REQUIRE PROPERTY SEGMENTS

When Recovered Property is submitted in a Property Segment (Level 3) with a Segment

Action Type of W = Time-Window Submission, all associated offense codes must allow for a

recovered property segment.

(371)

In addition, Data Element 14 (Type Property Loss/Etc.) must be 5 = Recovered. No

other property loss, etc., code is valid.

(378)

29. CRIME AGAINST PROPERTY OFFENSES MUST BE SUBMITTED WHEN PROPERTY

 SEGMENTS (LEVEL 3) ARE SUBMITTED

Property Segments can only be submitted with offenses relating to Crimes Against

Property, Kidnaping, Gambling, or Drug/Narcotic Offenses.

(076)

30. TYPE PROPERTY LOSS/ETC. CODES MUST BE APPLICABLE TO THE OFFENSE

Specifications regarding which Data Element 14 (Type Property Loss/Etc.) codes can be

submitted for offenses requiring Property Segments (Level 3) submissions can be found in section I of

this manual. For example, a completed Arson (200) requires a loss code of 2 = Burned.

(081)

31. POSITIONS 278-307 MUST BE BLANK ON GROUP “A” SUBMISSIONS

Property Segments (Level 3) submitted with a Segment Action Type of 

W = Time-Window Submission and M = Modify (if record to be modified was a previously sent

window record) are the only action types that can contain entries in the Window UCR Offense

Code section starting in position 278.

(369)
Data Element Edits

68

32. TIME-WINDOW SUBMISSIONS MUST HAVE AN OFFENSE ENTERED STARTING IN

 POSITION 278

Property Segments (Level 3) submitted with a Segment Action Type of 

W = Time-Window Submission must have at least one UCR Offense Code entered in the Window

UCR Offense Code section starting in position 278.

(370)

33. PROPERTY SEGMENTS SUBMITTED AS TIME-WINDOW CANNOT ALREADY EXIST

 ON THE FBI’S DATABASE

Property Segments containing Recovered Property submitted with a Segment Action Type

of W = Time-Window Submission will be added to the FBI’s database if not already on file. If the

Property Segment had been sent previously, it must first be deleted before resubmitting;

otherwise, the submission will be rejected. Refer to Volume 2, section I for additional

information.

(377)

34. MODIFYING OTHER THAN RECOVERED PROPERTY IS NOT ALLOWED

Property Segment (Level 3) submitted with a Segment Action Type of M = Modify must

contain a 5 = Recovered in Data Element 14 (Type Property Loss/Etc.).

(379)

35. CANNOT MODIFY PROPERTY RECORD THAT IS NOT ON THE FBI’S DATABASE

Property Segments (Level 3) submitted with a Segment Action Type of M = Modify can

only modify a Property Segment that was previously submitted as a W = Time-Window

Submission.

(380)

36. CANNOT DELETE PROPERTY RECORD THAT IS PART OF A GROUP “A” 

 INCIDENT REPORT

Property Segments (Level 3) submitted with a Segment Action Type of D = Delete can

only delete a Property Segment that was previously submitted as a W = Time-Window

Submission.

(381)
Data Element Edits

69

37. PROPERTY LOSS = 6 AND OFFENSES 35A AND 35B REQUIRE SPECIFIC ATTENTION

 FOR PROPERTY DESCRIPTIONS OF 10 AND 11

To ensure that 35A and 35B Drug/Narcotic Offenses are properly reported, Data Element

15 (Property Description) cannot be 11 = Drug/Narcotic Equipment for a 35A Drug/Narcotic

Violation. Similarly, 10 = Drugs/Narcotics cannot be entered for a 35B Drug Equipment

Violation. This is enforced by software when there is a single Crime Against Property offense.

However, in multiple Crimes Against Property offenses where one offense is a 35A

Drug/Narcotic Violation and the other is, for example, a 120 Robbery that involves 11 = Drug/

Narcotic Equipment, it can be entered. In this case, FBI software bypasses the above edit. 

Similarly, 10 = Drugs/Narcotics can be entered along with a 35B Drug Equipment Violation as

long as that property is involved in the 120 Robbery.

(387)

37.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, etc.), then this edit is bypassed.

Offense Allowed Property Descriptions

220 BURGLARY

240 MOTOR VEHICLE THEFT

NO 29-Structures-Single Occupancy Dwellings

 NO 30-Structures-Other Dwellings

NO 31-Structures-Commercial/Business

NO 32-Structures-Industrial/Manufacturing

NO 33-Structures-Public/Community

NO 34-Structures-Storage

NO 35-Structures-Other
Data Element Edits

70

23A LARCENY/POCKET-PICKING

23B LARCENY/PURSE-SNATCHING

NO 01-Aircraft

NO 03-Automobiles

NO 04-Bicycles

NO 05-Buses

NO 12-Farm Equipment

NO 15-Heavy Construction/Industrial Equipment

NO 18-Livestock

NO 24-Other Motor Vehicles

NO 28-Recreational Vehicles

NO 29-Structures-Single Occupancy Dwellings

NO 30-Structures-Other Dwellings

NO 31-Structures-Commercial/Business

NO 32-Structures-Industrial/Manufacturing

NO 33-Structures-Public/Community

NO 34-Structures-Storage

NO 35-Structures-Other

NO 37-Trucks

NO 39-Watercraft

23C LARCENY/SHOPLIFTING

NO 01-Aircraft

NO 03-Automobiles

NO 05-Buses

NO 12-Farm Equipment

NO 15-Heavy Construction/Industrial Equipment

NO 18-Livestock

NO 24-Other Motor Vehicles

NO 28-Recreational Vehicles

NO 29-Structures-Single Occupancy Dwellings

NO 30-Structures-Other Dwellings

NO 31-Structures-Commercial/Business

NO 32-Structures-Industrial/Manufacturing

NO 33-Structures-Public/Community

NO 34-Structures-Storage

NO 35-Structures-Other

NO 37-Trucks

NO 39-Watercraft
Data Element Edits

71

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

NO 03-Automobiles

NO 05-Buses

NO 24-Other Motor Vehicles

NO 28-Recreational Vehicles

NO 29-Structures-Single Occupancy Dwellings

NO 30-Structures-Other Dwellings

NO 31-Structures-Commercial/Business

NO 32-Structures-Industrial/Manufacturing

NO 33-Structures-Public/Community

NO 34-Structures-Storage

NO 35-Structures-Other

NO 37-Trucks

23H LARCENY/ALL OTHER LARCENY

NO 03-Automobiles

NO 05-Buses

NO 24-Other Motor Vehicles

NO 28-Recreational Vehicles

NO 37-Truck

(390)

37.2 WARNING - 280 OFFENSE HAS RECOVERED VEHICLE BUT 240 DOES NOT SHOW

 STOLEN

When a Stolen Property Offense (280) and a Motor Vehicle Theft (240) are connected to

an incident in which vehicles are recovered, stolen vehicles should also be reported.

(343)

Victim Segment Edits

38. A VICTIM MUST BE CONNECTED TO ALL OFFENDERS

When a victim is connected to a Crime Against Person or Robbery UCR Offense Code, all

Offender Sequence Numbers (Data Element 36) must be entered in Data Element 34

(Offender Numbers to be Related). If more than ten offenders, use the ten closest in relationship
Data Element Edits

72

to the victim. In other words, if there were 15 offenders and 14 were neighbors and 1 was the

brother, ensure that the brother was 1 of the 10 offenders entered.

(085)

39. CRIMES AGAINST SOCIETY CAN ONLY HAVE ONE VICTIM SEGMENT

If the only Offense Segment (Level 2) submitted is a Crime Against Society, there can 

only be one Victim Segment. This victim must have a value of S = Society/Public in Data

Element 25 (Type of Victim).

(080)

40. VICTIM REFERENCES TO OFFENSE CODES MUST HAVE OFFENSE SEGMENT

 COUNTERPARTS

Each UCR Offense Code entered into Data Element 24 (Victim Connected to UCR

Offense Codes) must have a corresponding Offense Segment. A victim cannot be connected to an

offense when the offense itself is not present.

(466)

Arrestee Segment Edits

41. PARTICIPANT MUST KEEP TRACK OF ARRESTEE SEQUENCE NUMBERS

When submitting Arrestee Segments (Level 6) or Group “B” Arrest Reports (Level 7)

with Segment Action Type of A = Add Arrest, the participant’s data processing software must

keep track of the correct value to assign to Data Element 40 (Arrestee Sequence Number). 

Normally, the first arrestee should have a value of 01. But when there are multiple arrestees for

the same incident, the next sequential number would be assigned by the participant. Submitting

Arrestee Segments with duplicate numbers will result in a Segment Already On File error

message.

(661, 751)

41.1 ARREST SEGMENTS SUBMITTED AS TIME-WINDOW CANNOT ALREADY EXIST

 ON THE FBI’S DATABASE

Arrest Segments (Level 6) submitted with a Segment Action Type of W = Time-Window

Submission will be added to the FBI’s database if not already on file. Submitting an Arrest

Segment with the same ORI Number, Incident Number, and Arrestee Sequence Number (Data

Element 40) will result in an Arrestee Already on File error message.

(064)
Data Element Edits

73

42. ARREST SEGMENT REQUIRES CLEARANCE INDICATOR FOR TIME-WINDOW

 SUBMISSIONS

Arrestee Segments (Level 6) submitted with a Segment Action Type of W = TimeWindow Submission must have a Y or N in the Window Clearance Indicator (position 80 of the

Segment).

(657)

43. GROUP “A” INCIDENT REPORT ARRESTEE SEGMENTS MUST HAVE A BLANK IN

 TIME-WINDOW POSITIONS

Arrestee Segments (Level 6) submitted with a Segment Action Type other than 

W = Time-Window Submission must have a blank in the Window Clearance Indicator (position

80 of the Segment) and no UCR Offense Codes can be entered in the Window UCR Offense

Code section in positions 81 through 110.

(658)

44. SEGMENT ACTION TYPE W MUST HAVE OFFENSE(S) ENTERED

Arrestee Segments (Level 6) submitted with a Segment Action Type of W = TimeWindow Submission must have at least one UCR Offense Code entered in the Window UCR

Offense Code section in positions 81 through 110.

(659)

Also, offenses must be Group “A” offenses, not Group “B.”

(671)

45. GROUP “A” INCIDENT REPORT MUST BE ON FILE WHEN ARREST SEGMENTS ARE 

 SUBMITTED AS ADDS

The initial Group “A” Incident Report must be on the FBI’s database when subsequent

Segment Action Types of A = Add Arrestee are submitted for additional arrestees.

(660)

46. CANNOT DELETE AN ARREST WHEN THE GROUP “A” INCIDENT REPORT IS ON

 THE FBI’S DATABASE

A submission cannot be made to delete an Arrest Segment from a Group “A” Incident

Report currently active in the FBI’s database. Arrestee Segments (Level 6) submitted with a

Segment Action Type of D = Delete must have been previously submitted as a W = TimeWindow Submission for the delete request to be valid.

(662)
Data Element Edits

74

47. CANNOT MODIFY AN ARREST WHEN THE GROUP “A” INCIDENT REPORT IS ON

 THE FBI’S DATABASE

A submission cannot be made to modify an Arrest Segment on a Group “A” Incident

Report currently active in the FBI’s database. Arrestee Segments (Level 6) submitted with a 

Segment Action Type of M = Modify must have been previously submitted as a W = TimeWindow Submission for the modify request to be valid.

(663)

48. ONLY ONE ARRESTEE RECORD CAN HAVE A “Y” IN THE CLEARANCE BYTE ON

 TIME-WINDOW SUBMISSION

When two or more Arrestee Segments (Level 6) are submitted as W = Time-Window

Submission Segments in the same incident, only one can have a Y in the Window Clearance

Indicator in position 80 of the Segment.

(668)

49. NO ARRESTEE RECORDS ARE PERMITTED 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).

(669)

50. CANNOT SUBMIT DUPLICATE GROUP “B” ARRESTEE SEGMENTS TO THE FBI

The Group “B” Arrest Report (Level 7) submitted as an Add cannot currently be 

active in the FBI’s database. If multiple arrestees are involved in the incident, the participant must

ensure that Data Element 40 (Arrestee Sequence Number) is unique for each Arrestee Segment

submitted.

(759)

51. LEVEL 7 ARRESTS MUST HAVE A GROUP “B” OFFENSE

Group “B” Arrestee Segments (Level 7) must contain a Group “B” Offense Code in Data

Element 45 (UCR Arrest Offense).

(760)
Data Element Edits

75

52. NO ARRESTEE SEGMENTS ALLOWED WITH AN ARREST DATE ON OR EARLIER 

 THAN THE EXCEPTIONAL CLEARANCE DATE

Whenever an Exceptional Clearance is submitted in the Administrative Segment

(Level 1), there can be no Arrestee Segments (Level 6) associated with the Group “A” Incident

Report having an Arrest Date (Data Element 42) on or earlier than the Exceptional Clearance

Date. This is also true for Segment Action Type of W = Time-Window Submissions. This is also

true for Segment Action Type A = Add, when submitting subsequent arrests to an already existing

Group “A” Incident Report. 

(071)

53. NUMBER OF ARRESTEES CANNOT BE GREATER THAN NUMBER OF OFFENDERS

When arrests are made for Group “A” Incident Report incidents, the number of arrests

cannot be greater than the number of offenders. For example, if the number of offenders was at

first unknown and the case was later cleared with an arrest, the Group “A” Incident Report must

be resubmitted with at least one offender. Another example would be if the incident was initially

submitted with one offender and 3 months later two arrests were made. In this case, the incident

would be resubmitted showing two offenders and two arrests.

(656)

D. UCR Offense Code Edits

In addition to edits specified within section I, a finer level of editing criteria is presented

below for selected offenses. These edits should also be incorporated into the participant’s

software. The number in parentheses following each edit description is the corresponding error

number that will be generated by the FBI’s software if the error condition is found.

Offense Edit

09C Justifiable Homicide

a) Data Element 31 (Aggravated Assault/Homicide Circumstances) can only have

codes of:

20 = Criminal Killed by Private Citizen

21 = Criminal Killed by Police Officer

No other code is allowable.

(463)
Data Element Edits

76

b) When a Justifiable Homicide is reported, no other offense may be reported in 

the Group “A” Incident Report. Other offenses would be submitted on

another Group “A” Incident Report.

(266)

c) Administrative Segments (Level 1) submitted with a Segment Action Type of

W = Time-Window Submission cannot have this offense entered in the 

Window UCR Offense Code section starting in position 58. 

Property Segments (Level 3) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have this offense entered in the

Window UCR Offense Code section starting in position 278.

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have this offense entered in the 

Window UCR Offense Code section starting in position 81. By definition a 

justifiable homicide never involves an arrest of the offender (the person who 

committed the justifiable homicide).

For any subsequent M = Modify of a previously submitted W = Time-Window

Submission, this is also true.

(121, 321, 621)

d) 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)

11A Forcible Rape

Data Element 27 (Sex of Victim) must be M = Male or F = Female to be 

connected to this offense code.

(469)
Data Element Edits

77

13A Aggravated Assault

Data Element 31 (Aggravated Assault/Homicide Circumstances) can only have 

codes of 01 through 06, and 08 through 10. All other codes, including 07 = Mercy

Killing, are not valid because they do not relate to an aggravated assault.

(462)

13B Simple Assault

Data Element 13 (Type Weapon/Force Involved) can only have codes of:

40 = Personal Weapons

90 = Other

95 = Unknown

99 = None

All other codes are invalid because they do not relate to a simple assault.

(265)

220 Burglary/Breaking and Entering

Data Element 25 (Type of Victim) cannot have a value of S = Society/Public.

(461)

23A-23H Larceny Offenses

When only larceny offenses are submitted, Property Descriptions (Data Element 

15) for vehicles cannot be entered. In order to report stolen vehicles, one or more

of the property offenses must logically allow for stolen vehicles. The following

vehicle codes are considered invalid: 03 = Automobiles, 05 = Buses, 24 = Other

Motor Vehicles, 28 = Recreational Vehicles, and 37 = Trucks.

(268)

36B Statutory Rape

Data Element 27 (Sex of Victim) must be M = Male or F = Female to be

connected to this offense code.

(469)
Data Element Edits

78

90I Runaway

Data Element 47 (Age of Arrestee) must be 01 through 17 on a Group “B” Arrest

Report.

(761)
79

III. ERROR NUMBERS AND MESSAGES

A. General Information

This section should not be used to determine how to program the participant’s computer

system; instead, section I and section II should be used for that purpose. The reasons for not

using this section in this manner are set forth below. Section III can be used as a reference source

when encountering FBI-detected errors that are returned on the Error Data Set (EDS) described

in Volume 2, section III. 

Some errors involve multiple data elements, and there can be any number of reasons that

can cause the specific error to be detected. In some cases, correcting the error condition may

involve adjusting data relationships and/or data elements not specifically mentioned within the

error explanation. Therefore, it is not practical to attempt to show every possible cause for each

specific error detected. Instead, this document will only describe the end effect of the error

condition detected by the computer. 

Furthermore, programming software based on the error messages and descriptions will

embed ambiguities and inconsistencies into the software. In many cases, other factors must be

considered that are not provided in the error message and description in order to correctly

program the computer. Again, section I and section II provide all editing criteria necessary for

software development concerning edit checks.

1. Multiple-cause Error Situations

Some errors have multiple-cause possibilities. For example, if Data Element 4 (Cleared

Exceptionally) contained a value of N = Not Applicable and Data Element 5 (Exceptional

Clearance Date) was entered, what is the error? Is it that the date was entered, or was an N value

entered incorrectly? In these situations, the explanation provided will describe the overall

problem; the true cause of the error will have to be determined by analysis. The following

example shows the Error Number and Message with description for the above error situation.

Error 

Number Message

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.
Error Numbers and Messages

80

2. Additional Error Resolution Information 

Within the Error Data Set (EDS) error records are additional identifying data that, when

taken together, uniquely identify an error. These data are Year, Month, Magnetic Media Record

Number, Segment Action Type, ORI Number, Incident Number, Segment Level, UCR Offense

Code, Person Sequence Number, Type Property Loss/Etc., Data Element Number, Error

Number, Data Value/Code in Error, Error Message, and Tape Volume Serial Number. These will

assist with error resolution. 

As previously mentioned, section I and section II should be used for instructions on how

to program a computer for correct submission of data. The error descriptions contained within

section III will only describe the end effect of an error condition, not necessarily what the

underlying data error was that triggered the error condition. Therefore, in some cases additional

error analysis will be necessary to determine the precise cause of FBI-detected errors. 

If participating computer systems are properly programmed, there will not be any errors. 

As a result, researching reasons for FBI-detected errors and correcting those errors will not be

necessary. 

3. Error Number Assignment

The error numbers are presented in numerical sequence. All errors pertaining specifically

to an Administrative Segment (Level 1) will be in the numeric range of 100 through 199; each

error for an Offense Segment (Level 2) will be in the numeric range of 200 through 299; etc. 

The exceptions are errors found in FBI control programs and structure checks. These

types of errors will be in the numeric range of 001 through 089 and indicate exceptional

conditions such as missing segments, duplicate segments, etc. Zero-Reporting Segment (Level 0)

errors are in the range of 090 through 099. Warning messages are assigned n40 through n49 (n =

0-7 corresponding to segment level); these will not cause a rejection of the incident. 

4. Source of Data Element Values

Located in Volume 1, section VI are all the valid codes and their meanings applicable for

each data element. That section should be referenced when establishing computer codes for data

submitted to the FBI. The personnel responsible for software development should also be aware

of the FBI editing performed for each data element as described in section I and section II of this

manual. 
Error Numbers and Messages

81

B. Error Numbers and Messages

Structure Check Errors

Error

Number Message

001 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required on the Zero-Reporting Segment

(Level 0).

015 CANNOT HAVE EMBEDDED BLANKS BETWEEN FIRST AND LAST 

NON-BLANK CHARACTERS

Zero-Reporting Segment (Level 0). Although Data Element 2 (Incident Number)

should be entered with 12 zeros, a pre-edit found embedded blanks between the

first and last significant characters.

016 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Zero-Reporting Segment (Level 0). Although Data Element 2 (Incident Number)

should be entered with 12 zeros, a pre-edit found a blank in the first position. It

must begin in position 1 and must also contain 12 zeros.

017 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Zero-Reporting Segment (Level 0). Although Data Element 2 (Incident Number)

should be entered with 12 zeros, a pre-edit discovered characters other than A

through Z, 0 through 9, hyphens, and/or blanks had been entered. 

050 LEVELS ARE OUT OF NUMERIC ORDER FOR THIS INCIDENT

All segments for a Group “A” Incident Report must be in numeric order. In this

case, one was not. 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 TAPE

Any record level on the tape that is other than 0 through 7 or L (LEOKA) will

generate an error.

052 NOT A VALID ORI—NOT ON UCR ORI FILE

Data Element 1 (ORI Number) must be a valid nine-character NCIC number.
Error Numbers and Messages

82

053 RECORD NOT ON FILE

A transaction was submitted to M = Modify an existing segment on the FBI’s

database. However, the record to be modified is not on file. 

The modify transaction implies that Exceptional Clearance, Recovered Property,

and/or Arrestee Segments are on file as window records, not complete Group “A”

Incident Reports. Regardless, the data segment to be modified is not in the FBI’s

file.

055 CANNOT HAVE AN INITIAL INCIDENT RECORD WITHOUT STARTING WITH 

RECORD LEVEL 1

When an I = Incident Report is submitted, the first segment must be the

Administrative Segment (Level 1). In this case, the first record received for the

incident was not the Administrative Segment.

056 INCIDENT ALREADY ON FILE—PREVIOUSLY ADDED TO FILE ON [mm/dd/yyyy]

A Group “A” Incident Report was previously added to the FBI’s database on the

date shown within the error message and is presently on file. Another report was 

processed with the same ORI and Incident Number, resulting in this error. 

057 ACTION TYPE IS NOT VALID FOR THIS RECORD LEVEL

The values of I = Incident Report, A = Add, M = Modify, W = Time-Window

Submission, and D = Delete must be applicable to appropriate Segment Levels 

(0 through 7) as the following shows:

Action Valid Only With These Levels

I Segment Levels 1 through 6

A 0 = Zero-Reporting Segment

 6 = Arrestee Segment

 7 = Group “B” Arrest Report

M 1 = Administrative Segment

 *3 = Property Segment

*6 = Arrestee Segment

 7 = Group “B” Arrest Report

W 1 = Administrative Segment

 3 = Property Segment

 6 = Arrestee Segment
Error Numbers and Messages

83

D 0 = Zero-Reporting Segment

 1 = Administrative Segment

*3 = Property Segment

*6 = Arrestee Segment

 7 = Group “B” Arrest Report

*Valid only when previously submitted as W.

058 ALL SEGMENTS ON MAGNETIC MEDIA MUST HAVE SAME CONTROL INFO - 

YR=[year] MO=[month] 

Each segment on the magnetic media submitted to NIBRS must contain the same

Month of Tape and Year of Tape values in positions 7 through 12. The first

segment processed will be compared with all other segments to check for this

condition. In this case, the record processed did not have the same information

and was rejected.

059 ALL SEGMENTS ON MAGNETIC MEDIA MUST BE FROM SAME STATE -

STATE=[state]

All segments on the submitted magnetic media must be from the same state for

nonfederal participants. This will be checked by comparing the two-character state

abbreviation in Data Element 1 (ORI Number); all must have the same value.

060 PROCESSING DATE [mmyyyy] PRECEDES MONTH/YEAR IN POSITIONS 7-12 

CONTAINING [mmyyyy]

The FBI received and processed the magnetic media on a date that was earlier than

that reflected within positions 7 through 12 (Month/Year) of each record. This is

an error because data were submitted for a month that is a future month.

The Month/Year in positions 7 through 12 of each record cannot be after the

month and year the FBI processes the magnetic media.

064 ARRESTEE ALREADY ON FILE

When an Arrest Segment is submitted with a Segment Action Type of W = TimeWindow Submission, the identifying information (ORI Number, Incident Number,

and Arrestee Sequence Number) must be unique. When error number 064

appears, an arrestee was already on file with this identifying information.
Error Numbers and Messages

84

065 EACH LEVEL 2 OFFENSE MUST HAVE AT LEAST ONE VICTIM

Each Offense Segment submitted must have at least one Victim Segment(s)

pointing to it via Data Element 24 (Victim Connected to UCR Offense Code). In

this case, no Victim Segment points to the referenced Offense Segment. An

Offense Segment cannot stand alone; it must have a Victim Segment linked to it.

070 THE CORRESPONDING OFFENDER RECORD MUST BE PRESENT

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

071 CANNOT HAVE ARRESTS IF CLEARED EXCEPTIONALLY

Whenever an Exceptional Clearance is submitted in the Administrative Segment

(Level 1), there can be no Arrestee Segments (Level 6) associated with the Group

“A” Incident Report having an Arrest Date (Data Element 42) on or earlier than

the Exceptional Clearance Date. In this instance, the incident had arrestees with a

date preceding the Exceptional Clearance Date.

072 RECOVERED PROPERTY MUST ALSO BE SUBMITTED AS STOLEN

Data Element 15 (Property Description) contains property that was reported as

recovered without also being reported as stolen within that same incident. Any

property being reported as recovered must first be reported as stolen. This edit

does not apply for property description 38 = Vehicle Parts/Accessories only, to allow

reporting of 5 = Recovered in Data Element 14 when property descriptions of 03 =

Automobiles, 05 = Buses, 37 = Trucks, 28 = Recreational Vehicles, or 24 = Other

Motor Vehicles are reported as stolen.

Ensure that the property description code was entered correctly. Perhaps the

stolen or recovered property codes were entered incorrectly, or the recovered

property had not originally been reported as stolen.

073 NUMBER OF RECOVERED VEHICLES CANNOT BE GREATER THAN THE 

NUMBER STOLEN

When Data Element 18 (Number of Stolen Motor Vehicles) is 01 to 99, the

number must be equal to or greater than the number entered in Data Element 19

(Number of Recovered Motor Vehicles).
Error Numbers and Messages

85

074 PROPERTY RECORD (LEVEL 3) MUST EXIST WITH THIS OFFENSE

When an I = Incident Report is submitted that contains an Offense Segment for a

Crime Against Property, Kidnaping, Gambling, or Drug/Narcotic Offense,

Property Segment(s) must also be submitted. In this case, no Property Segments

were submitted.

075 MISSING A MANDATORY RECORD LEVEL FOR A COMPLETE INCIDENT

When an I = Incident Report is submitted, the following segments must be

included: Administrative Segment, Offense Segment, Victim Segment, and an

Offender Segment. One or more of these segments is missing.

076 PROPERTY RECORD (LEVEL 3) CANNOT EXIST WITH OFFENSES SUBMITTED

A Property Segment (Level 3) was submitted for a Group “A” Incident Report

without an applicable property offense code. Property Segments can only be

submitted with offenses relating to Crimes Against Property, Kidnaping, Gambling,

or Drug/Narcotic Offenses.

077 NEED A PROPERTY LOSS CODE OF 1 OR 8 WHEN THIS OFFENSE IS ATTEMPTED

Data Element 7 (Offense Attempted/Completed) is A = Attempted and Data

Element 6 (UCR Offense Code) is a Crime Against Property, Gambling,

Kidnaping, or Drug/Narcotic Offense. However, there is no Data Element 14

(Type Property Loss/Etc.) of 1 = None or 8 = Unknown.

078 A VALID PROPERTY LOSS CODE DOES NOT EXIST FOR THIS COMPLETED 

OFFENSE

If Data Element 6 (UCR Offense Code) is a Crime Against Property, Kidnaping,

Gambling, or Drug/Narcotic Offense, and Data Element 7 (Offense

Attempted/Completed) is C = Completed, a Property Segment (Level 3) must be

sent with a valid code in Data Element 14 (Type Property Loss/Etc.).

080 CRIMES AGAINST SOCIETY CAN ONLY HAVE ONE VICTIM

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 can be submitted. In this instance,

more than one victim segment was submitted.
Error Numbers and Messages

86

081 THIS PROPERTY LOSS CODE CANNOT EXIST WITH THE OFFENSES SUBMITTED

Data Element 14 (Type Property Loss/Etc.) has a loss code that is not applicable

to any of the offenses submitted. Refer to section I of this manual for the correct

values to use for each of the offenses.

084 RECOVERED PROPERTY VALUE CANNOT BE GREATER THAN THE VALUE 

WHEN STOLEN

When Data Element 14 (Type Property Loss/Etc.) contains Property Segments for

both 7 = Stolen/Etc. and 5 = Recovered, the recovered property cannot have

value(s) greater than corresponding value(s) reported stolen.

If this error appears for Property Description 38 = Vehicle Parts/Accessories, the

value exceeded the value of the stolen vehicles.

085 WHEN CONNECTED, EACH VICTIM MUST BE CONNECTED TO ALL OFFENDERS 

When a victim is connected to a Crime Against Person or Robbery UCR Offense

Code, all Offender Sequence Numbers (Data Element 36) must be entered in Data

Element 34 (Offender Numbers to be Related). If there are more than ten

offenders, use the ten closest to the victim. In this case, the Victim Segment does

not point to all the offenders.

086 THE LAST TWO POSITIONS OF THE PARTICIPANT’S ORI ARE INVALID

A nonfederal participant must have 00 in positions 8 and 9 of Data Element 1 (ORI

Number). A federal participant must use its two-character code assigned by the

UCR; no other participant’s code can be used. In this submission, the last two

positions were entered incorrectly.

087 WINDOW SEGMENTS ALREADY ON FILE WITH THIS INCIDENT NUMBER

A Group “A” Incident Report was submitted but was not added to the FBI’s

database. Already on file is either (1) a Recovered Property Segment or (2) an

Arrestee Segment.

There are several reasons this situation could occur. First, a duplicate incident

number might have been assigned. Second, the participant previously submitted

Time-Window Segments and then submitted the complete Group “A” Incident

Report. Last, during the FBI’s annual purge of 2-year old incidents, Window

records were created as specified in Volume 2, section I. The participant’s

computer was not programmed properly to account for the purge process.
Error Numbers and Messages

87

088 GROUP “A” AND GROUP “B” REPORTS CANNOT HAVE SAME IDENTIFIER 

(CONFLICT IN SEG = X)

Segment Level 7 (Group “B” Arrest Report) cannot be submitted when a Segment

Level 1, 3, or 6 exists with the same control identifiers of Data Element 1 (ORI)

and Data Element 2 (Incident Number) as the Segment Level 7’s ORI and Data

Element 41 (Arrest Transaction Number). Similarly, a Segment Level 1, 3, or 6

cannot be submitted when a Segment Level 7 already exists. This edit includes any

Time-Window Submissions.

Possible Causes:

1) Group “A” Incident Report is immediately followed by a Group “B” Arrest 

Report. The Group “A” is added to the FBI’s database; the Group “B” is 

rejected. Volume 1 provides instructions concerning the proper way to submit 

an incident that has both Group “A” and “B” offenses.

2) A Group “B” Arrest Report submitted as a Segment Level 7 does not have a 

unique value in Data Element 41 (Arrest Transaction Number) to avoid matching

an unrelated Group “A” Incident Report submission for the same ORI.

Zero-reporting Segment Errors

Error

Number Message

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.

092 ZERO-REPORTING INCIDENT NUMBER MUST BE ALL ZEROS

A Segment Level 0 was submitted, but the incident number entered into positions

26 through 37 was not all zeros.
Error Numbers and Messages

88

093 ZERO-REPORTING MONTH/YEAR WAS PRIOR TO THE BASE DATE

A Segment Level 0 was submitted with a month and year entered into positions 38

through 43 that is earlier than January 1 of the previous year or before the date the

agency converted over to NIBRS.

094 ZERO-REPORTING MONTH/YEAR EXCEEDED MONTH/YEAR OF TAPE

A Segment Level 0 was submitted with a month and year entered into positions 38

through 43 that was later than the Month of Tape and Year of Tape entered into

positions 7 through 12.

Note: Error Numbers 001, 015, 016, and 017 are also Zero-Reporting segment 

errors.

Administrative Segment Errors 

Error

Number Message

101 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

104 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contain a value that is not specified

within Volume 1, section VI.

105 [An Appropriate DATE Error Message]

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. 

The date cannot be later than that entered within the Month of Tape and Year of

Tape fields on the data record. For example, if Month of Tape and Year of Tape

are 06/1999, the date entered cannot be 7/01/1999 or greater. 

The error message will pinpoint what error occurred. For example, DAT11:

MONTH EXCEEDS 12 and DAT14: DAY EXCEEDS 31 are some of the date

error messages that are displayed.
Error Numbers and Messages

89

115 CANNOT HAVE EMBEDDED BLANKS BETWEEN FIRST AND LAST 

NON-BLANK CHARACTERS

Data Element 2 (Incident Number) contains embedded blanks between the first and

last significant characters. 

116 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Element 2 (Incident Number) must be left-justified with blank right-fill. 

Since the number is less than 12 characters, it must begin in position 1; one or

more blanks were entered starting in position 1 followed by the data.

117 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Data Element 2 (Incident Number) can only have character combinations of A

through Z, 0 through 9, hyphens, and/or blanks. For example, 89-123-SC is valid,

but 89+123*SC is invalid.

118 DATE CANNOT BE ON OR AFTER THE INACTIVE DATE [yyyymmdd] 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. No data from this ORI will be accepted after this

date.

120 EXCEPTIONAL CLEARANCE DATE CANNOT PREDATE BASE DATE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have an Exceptional Clearance Date (Data

Element 5) earlier than the Time-Window Base Date. For any subsequent 

M = Modify of a previously submitted W = Time-Window Submission, this is also

true. Refer to Volume 2, section I, for additional information on the Base Date. 

121 JUSTIFIABLE HOMICIDE (09C) IS NOT A VALID WINDOW OFFENSE CODE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have a Window UCR Offense Code (Data

Element 6) of 09C = Justifiable Homicide. For any subsequent M = Modify of a

previously submitted W = Time-Window Submission, this is also true.

151 REPORT INDICATOR MUST BE BLANK OR “R”

Within Data Element 3 (Incident Date/Hour) is a report 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.

152 INVALID HOUR ENTRY
Error Numbers and Messages

90

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.

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.

154 CLEARED EXCEPTIONALLY CANNOT CONTAIN “N” WITH SEGMENT ACTION 

TYPE “W” 

 

Administrative Segments (Level 1) submitted with a Segment Action Type of

W = Time-Window Submission cannot contain an N = Not Applicable in Data

Element 4 (Cleared Exceptionally).

155 CLEARANCE DATE [yyyymmdd] PREDATES INCIDENT DATE [yyyymmdd]

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.

157 MUST BE PRESENT FOR TIME-WINDOW SEGMENT

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission must contain Data Elements 4 (Cleared

Exceptionally) and 5 (Exceptional Clearance Date). Both must be present to be a

valid submission.

158 OFFENSE CODE FIELD MUST HAVE ENTRY WITH SEGMENT ACTION 

TYPE “W”

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission must have at least one UCR Offense Code entered

in the Window UCR Offense Code section.

159 POSITIONS 58-87 MUST BE BLANK FOR GROUP “A” INCIDENT REPORT
Error Numbers and Messages

91

Administrative Segments (Level 1) submitted with a Segment Action Type that is

not W = Time-Window Submission cannot have an entry in the Window UCR

Offense Code section.

160 INCIDENT NOT ON FILE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify must already be on the FBI file with Data Element 1 (ORI Number)

and Data Element 2 (Incident Number).

161 CANNOT MODIFY GROUP “A” INCIDENT DATE THIS WAY—ON FILE IS 

[yyyymmddrhh]

Administrative Segments (Level 1) submitted with a Segment Action Type of

M = Modify cannot change the date in Data Element 3 (Incident Date/Hour) of

Segments which were previously submitted with a Segment Action Type of 

I = Incident Report. 

162 CANNOT MODIFY GROUP “A” REPORT FLAG THIS WAY—ON FILE IS 

[yyyymmddrhh]

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify cannot change the Report Date Indicator (position 46 of the segment)

of Segments which were previously submitted with a Segment Action Type of 

I = Incident Report.

163 CANNOT MODIFY GROUP “A” INCIDENT HOUR THIS WAY—ON FILE IS 

[yyyymmddrhh]

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify cannot change the hour in Data Element 3 (Incident Date/Hour) of

Segments which were previously submitted with a Segment Action Type of 

I = Incident Report.

164 CLEARED EXCEPTIONALLY FIELD MUST CONTAIN “N” WHEN ARRESTEES 

WERE REPORTED

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify must have an N = Not Applicable in Data Element 4 (Exceptional

Clearance Indicator) when arrestees were already present for the Group “A”

Incident Report.

165 CANNOT BE BLANK OR EQUAL “N” FOR NON GROUP “A” SEGMENT
Error Numbers and Messages

92

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify cannot have an N = Not Applicable in Data Element 4 (Exceptional

Clearance Indicator) when the Incident was previously submitted as a 

W = Time-Window Submission.

166 CANNOT HAVE ENTRY IN EXCEPTIONAL CLEARANCE DATE IF CLEARED 

EXCEPTIONALLY IS “N”

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify with an N = Not Applicable in Data Element 4 (Exceptional

Clearance Indicator) cannot have an entry in Data Element 5 (Exceptional

Clearance Date).

167 DATE CANNOT BE BLANK FOR NON GROUP “A” SEGMENT

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify for a previously submitted W = Time-Window Submission must have

a date in Data Element 5 (Exceptional Clearance Date).

168 GROUP “A” CANNOT HAVE OFFENSES IN POSITIONS 58-87 ON MAGNETIC

MEDIA SEGMENT

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify for a previously submitted I = Incident Report cannot have any entries

in the Window UCR Offense Code section, positions 58 through 87 on the tape.

169 TIME-WINDOW SEGMENT BEING MODIFIED MUST HAVE OFFENSE CODE

Administrative Segments (Level 1) submitted with a Segment Action Type of 

M = Modify for a previously submitted W = Time-Window Submission must have

at least one UCR Offense Code in the Window UCR Offense Code section,

positions 58 through 87 on the tape.

170 INCIDENT DATE CANNOT BE AFTER YEAR [yyyy] AND MONTH [mm] OF TAPE 

Data Element 3 (Incident Date/Hour) date is later than the year and month that the

magnetic media represents. For example, the May 1999 magnetic media cannot

contain incidents happening later than this date.

171 INCIDENT DATE IS OUTSIDE THE BASE DATE CALCULATION

A Group “A” Incident Report was submitted with a date entered into Data

Element 3 (Incident Date/Hour) that is earlier than January 1 of the previous year,

using the Month of Tape and Year of Tape as a reference point.

For example, if the Month of Tape and Year of Tape contain a value of 01/1999,
Error Numbers and Messages

93

but the incident date is 12/25/1997, the incident will be rejected. Volume 2, section I,

provides specifications concerning the FBI’s 2-year database. 

Note: The exception is when an exceptional clearance is being submitted with a

Segment Action Type of W = Time-Window Submission. The incident

date may be any past date, but cannot be any earlier than January 1,

1950.

172 INCIDENT DATE/HOUR FOR “I” RECORDS CANNOT PREDATE 01/01/1991

Data Element 3 (Incident Date/Hour) cannot be earlier than 01/01/1991. This is

applied to all I = Incident Report submissions. This beginning date will eliminate 

dates that are known to be obviously incorrect since NIBRS began accepting data

on this date. 

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 Summary

reporting to Incident-Based 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 Summary

System 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

Summary System 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. 
Error Numbers and Messages

94

174 EXCEPTIONAL CLEARANCE DATE PREDATES DATE ORI WENT IBR [yyyymmdd]

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission or M = Modify cannot have a date earlier than

when the ORI converted to Incident-Based Reporting (IBR). Data Element 5

(Exceptional Clearance Date) was earlier.

175 CANNOT CALCULATE BASE DATE FROM INCIDENT DATE [yyymmdd]

The tape control date (positions 7 through 12, month and year) and Data Element

3 (Incident Date/Hour) must both be valid dates for calculating timeframes.

176 INCIDENT DATE FOR WINDOW RECORDS CANNOT BE WITHIN BOUNDARIES OF

GROUP “A” INCIDENT

Administrative Segments (Level 1) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have a date in Data Element 3 (Incident

Date/Hour) which would be a valid date for a Group “A” Incident. For any

subsequent M = Modify of a previously submitted W = Time-Window Submission,

this is also true.

177 GROUP “B” OFFENSE CODES CANNOT BE ENTERED IN POSITIONS 58-87 ON 

SEGMENT 1

A Segment Action Type of W = Time-Window Submission erroneously contains

one or more Group “B” offense codes. Only Group “A” Offense Codes are

allowed in these positions for this type of submission. 

Offense Segment Errors

Error

Number Message

201 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

202 CONTAINS NONNUMERIC ENTRY

Data Element 10 (Number of Premises Entered) is not a numeric entry of 01

through 99.
Error Numbers and Messages

95

204 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contains a value that is not specified

within Volume 1, section VI. 

206 ERROR - DUPLICATE VALUE=[value]

The data element in error is one that contains multiple data values. When more

than one code is entered, none can be duplicate codes.

207 ERROR - MUTUALLY EXCLUSIVE VALUE=[value]

The data element in error 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.

215 CANNOT HAVE EMBEDDED BLANKS BETWEEN FIRST AND LAST NON-BLANK 

CHARACTERS

Data Element 2 (Incident Number) contains embedded blanks between the first and

last significant characters. 

216 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Element 2 (Incident Number) must be left-justified with blank right-fill. 

Since the number is less than 12 characters, it must begin in position 1; one or

more blanks were entered starting in position 1 followed by the data.

217 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Data Element 2 (Incident Number) can only have character combinations of A

through Z, 0 through 9, hyphens, and/or blanks. For example, 89-123-SC is valid,

but 89+123*SC is invalid.

219 DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES

Data Element 12 (Type Criminal Activity) can only be entered when the UCR

Offense Code is: 

250 = Counterfeiting/Forgery

280 = Stolen Property Offenses

35A = Drug/Narcotic Violations

35B = Drug Equipment Violations

39C = Gambling Equipment Violations

370 = Pornography/Obscene Material

520 = Weapon Law Violations
Error Numbers and Messages

96

Data Element 12 (Gang Information) can only be entered when the UCR Offense

Code is:

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

100 = Kidnaping/Abduction

120 = Robbery

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

13A = Aggravated Assault

13B = Simple Assault

13C = Intimidation

Data Element 13 (Type of Weapon/Force Involved) can only be entered when 

the UCR Offense Code is:

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

09C = Justifiable Homicide

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion

520 = Weapon Law Violations

251 INVALID CODE

Data Element 7 (Offense Attempted/Completed) must be a valid code of A or C.

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).
Error Numbers and Messages

97

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 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. Since a burglary offense was not entered, the Method of Entry

should not have been entered.

255 AUTOMATIC INDICATOR MUST BE BLANK OR “A”

In Data Element 13 (Type of Weapon/Force Involved), the third character must be

A = Automatic or blank. In this case, a value other than the two mentioned was

entered.

256 OFFENSE CODES OF 09A, 09B, 09C, 13A, 13B, AND 13C MUST HAVE ENTRY OF “C”

Data Element 7 (Offense Attempted/Completed) code must be C = Completed if

Data Element 6 (UCR Offense Code) is an Assault or Homicide.

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) and if Data Element 9 (Location Type) contains 14 = Hotel/Motel/

Etc. or 19 = Rental Storage Facility.

258 WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN “A” IN THE AUTO

INDICATOR

In Data Element 13 (Type of Weapon/Force Involved), A = Automatic is the third

character of code. It is valid only with the following codes: 

11 = Firearm (Type Not Stated)

12 = Handgun

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.
Error Numbers and Messages

98

262 DUPLICATE 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).

263 CANNOT HAVE MORE THAN 10 OFFENSES

A Group “A” Incident Report was submitted with more than 10 Offense Segments

(Level 2). The maximum number allowable is 10.

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 [weapon-code] WITH AN OFFENSE OF 13B

An Offense Segment (Level 2) was submitted for 13B = Simple Assault. 

Accordingly, 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 AN 09C OFFENSE

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 [weapon-code] WITH AN OFFENSE OF [offense]

The homicide offense shown within the error message must have a code in Data

Element 13 (Type Weapon/Force Involved) other than 99 = None. In this case,

None was entered. Some type of weapon/force must be used in a homicide

offense.

268 A LARCENY OFFENSE CANNOT HAVE A MOTOR VEHICLE PROPERTY 

DESCRIPTION ENTERED

The only property offenses submitted were larceny offenses that contained

Property Descriptions (Data Element 15) for one or more of the vehicle codes. 

Stolen vehicles cannot be reported for a larceny.
Error Numbers and Messages

99

Analysis will be necessary to see how to correct the problem. Perhaps a data entry

error was made resulting in a vehicle code being entered by mistake, or maybe a

second property offense segment should be submitted that logically allows for

stolen vehicles, etc. FBI software cannot determine the intent.

269 POSSIBLE CLASSIFICATION ERROR OF AGGRAVATED ASSAULT 13A CODED AS 

SIMPLE 13B

A Simple Assault (13B) was submitted, but Data Element 13 (Type Weapon/

Force Involved) has a weapon code reflecting an Aggravated Assault (13A)

offense. Either the wrong weapon code was entered or the offense should have

been classified as an Aggravated Assault (13A).

Property Segment Errors

Error

Number Message

301 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

302 CONTAINS NONNUMERIC ENTRY

Must be numeric entry with zero left-fill. 

If Data Element 21 (Estimated Quantity) has the error, note that any decimal

fractional quantity must be expressed in thousandths as three numeric digits. If no

fractional quantity was involved, then all zeros should be entered.

304 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contain a value that is not specified

within Volume 1, section VI.

305 [An Appropriate DATE Error Message]

Data Element 17 (Date Recovered) date components 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 be earlier than Data

Element 3 (Incident Date/Hour).
Error Numbers and Messages

100

The date cannot be later than that entered within the Month of Tape and Year of

Tape fields on the data record. For example, if Month of Tape and Year of Tape

are 06/1999, the date entered cannot be 07/01/1999 or later.

The error message will pinpoint what error occurred. For example, DAT11:

MONTH EXCEEDS 12 and DAT14: DAY EXCEEDS 31 are some of the date

error messages that are displayed.

306 ERROR - DUPLICATE VALUE=[value]

The data element in error is one that contains multiple data values. When more

than one code is entered, none can be duplicate codes.

If more than one code is entered in Data Element 20 (Suspected Drug Type), the

same code cannot be entered within the same type measurement category. In

other words, cocaine cannot be reported in grams and pounds (same weight

category), but can be reported in grams and liters (weight and capacity categories). 

For the drug type of U = Unknown, this does not apply; U = Unknown can be

entered only once.

315 CANNOT HAVE EMBEDDED BLANKS BETWEEN FIRST AND LAST NON-BLANK 

CHARACTERS

Data Element 2 (Incident Number) contains embedded blanks between the first and

last significant characters. 

316 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Element 2 (Incident Number) must be left-justified with blank right-fill. 

Since the number is less than 12 characters, it must begin in position 1; one or

more blanks were entered starting in position 1 followed by the data.

317 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Data Element 2 (Incident Number) can only have character combinations of A

through Z, 0 through 9, hyphens, and/or blanks. For example, 95-123-SC is valid,

but 95+123*SC is invalid.

320 RECOVERED DATE CANNOT PREDATE BASE DATE

Property Segments (Level 3) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have a Date Recovered (Data Element 17) 
Error Numbers and Messages

101

before the date which is calculated using the base date technique (January 1 of the

year prior to the current year, or earlier than the date the agency converted to

IBR). For any subsequent M = Modify of a previously submitted W = TimeWindow Submission, this also applies.

321 JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE CODE

Property Segments (Level 3) submitted with a Segment Action Type of W = TimeWindow Submission cannot have a Window UCR Offense Code (Data Element 6)

of 09C = Justifiable Homicide. For any subsequent M = Modify of a previously

submitted W = Time-Window Submission, this also applies.

342 WARNING - PROPERTY DESC(15) HAD VALUE (16) THAT EXCEEDED

 THRESHOLD OF [$ value]

This is a warning message only.

Data Element 16 (Value of Property) contains a value that exceeds an

FBI-assigned threshold amount. The participant should check to see if the value

entered is a data entry error, or if the value is correct. In addition to various

thresholds assigned to particular property descriptions, 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, a warning message is

generated. In this case, the cents were entered as whole dollars.

343 WARNING - 280 OFFENSE HAS RECOVERED VEHICLE BUT 240 DOESN'T SHOW 

STOLEN

This is a warning message only.

This warning is generated when a 280 Stolen Property Offense and a 240 Motor

Vehicle Theft are submitted that contain questionable property reporting. When

the incident contains a recovered vehicle but does not also have a stolen vehicle,

this warning message is created.

The incident should be reviewed and if there was indeed a stolen vehicle, the

incident should be resubmitted reflecting both stolen and recovered vehicles.
Error Numbers and Messages

102

351 PROPERTY VALUE OF ZERO IS NOT ALLOWED

Data Element 16 (Value of Property) has a value of zero entered for dependent

code in Data Element 15 (Property Description); zero (0) value cannot be entered

for this property description. If the value is unknown, enter a value of $1;

otherwise, the value of the property must be entered for the code.

Zero values must be entered for:

09 = Credit/Debit Cards

22 = Nonnegotiable Instruments

Zero values are optional for:

77 = Other

99 = (special category)

 

352 DATA ELEMENTS 15 - 22 MUST BE BLANK WHEN PROPERTY LOSS CODE = 1 OR

8

When this error occurs, data were found in one or more of the referenced data

elements. These data elements must be blank based on other data element values

that prohibit data being entered in these data elements.

For example, if Data Element 14 (Type property Loss/Etc.) is 8 = Unknown, Data

Elements 15 through 22 must be blank. If it is 1 = None and offense is 35A, then

Data Elements 15 through 19 and 21 through 22 must be blank. If it is 1 = None

and offense is not 35A, 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. Determine which of the data elements

was entered incorrectly.

354 DATA ELEMENT 15 WAS NOT ENTERED, BUT VALUE ($) WAS 

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
Error Numbers and Messages

103

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 (Property Value) were not entered.

357 PROPERTY LOSS (14) MUST BE 7 WITH AN OFFENSE CODE OF 240 FOR DATA TO

BE ENTERED

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.

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

359 ALL NONVEHICULAR PROPERTY DESCRIPTIONS WERE ENTERED

When Data Element 18 (Number of Stolen Motor Vehicles) is entered, Data

Element 15 (Property Description) must contain at least one of the following

vehicle codes:

03 = Automobiles

05 = Buses

24 = Other Motor Vehicles

28 = Recreational Vehicles

37 = Trucks

When Data Element 19 (Number of Recovered Motor Vehicles) is entered and is

01 through 99, Data Element 15 (Property Description) must contain at least one

of the following vehicle codes:

03 = Automobiles

05 = Buses

24 = Other Motor Vehicles

28 = Recreational Vehicles
Error Numbers and Messages

104

37 = Trucks

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. 

361 DATA MUST EXIST WITH AN OFFENSE CODE OF 240 AND A PROPERTY 

LOSS 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. There are less than three codes

present.

363 WITH A CODE OF “X” BOTH QUANTITY (21) AND MEASUREMENT (22) 

MUST BE BLANK

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;

one or both of them were entered.

364 WITH DATA ENTERED BOTH QUANTITY (21) AND MEASUREMENT (22) 

MUST BE PRESENT

When Data Element 6 (UCR Offense Code) is 35A = Drug/Narcotic Violations, 14

(Type Property Loss/Etc.) is 6 = Seized, 15 (Type Property Loss/Etc.) is 10 =

Drugs, and Data Element 20 (Suspected Drug Type) is entered, both Data Element

21 (Estimated Quantity) and 22 (Type Measurement) must also be entered.

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
Error Numbers and Messages

105

be 6 = Seized, and Data Element 15 (Property Description) must be 10 = Drugs/

Narcotics. 

There could be multiple underlying reasons causing this error to be detected. One

of them might be that Data Element 20 (Suspected Drug Type) was entered by

mistake. Perhaps the code entered in Data Element 15 (Property Description)

should have been 01 = Aircraft, but by entering the code as 10 = Drugs/Narcotics, 

someone thought that Data Element 20 must be entered, etc.

366 WITH DATA ENTERED BOTH TYPE (20) AND MEASUREMENT (22) 

MUST BE PRESENT

Data Element 21 (Estimated Quantity) was entered, but 20 (Suspected Drug Type)

and/or 22 (Type Measurement) were not entered; both must be entered.

367 DRUG TYPE MUST BE “E”, “G”, OR “K” FOR A VALUE OF “NP”

Data Element 22 (Type Measurement) was entered with NP 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 WITH DATA ENTERED BOTH TYPE (20) AND QUANTITY (21) MUST BE PRESENT

Data Element 22 (Type Measurement) was entered, but 20 (Suspected Drug Type)

and/or 21 (Estimated Quantity) were not entered; both must be entered.

369 MUST BE BLANK WHEN ACTION TYPE = I (INITIAL)

Property Segments (Level 3) submitted with a Segment Action Type code of 

W = Time-Window Submission and M = Modify (if record to be modified was a

previously sent window record) are the only action types that can contain entries in

the Window UCR Offense Code section, positions 278 through 307.

370 MUST HAVE AN ENTRY WITH AN ACTION TYPE OF W (WINDOW)

Property Segments (Level 3) submitted with a Segment Action Type of 

W = Time-Window Submission or M = Modify must have at least one UCR
Error Numbers and Messages

106

Offense Code entered in the Window UCR Offense Code section, positions 278

through 307.

371 GAMBLING, KIDNAPING, AND CRIMES AGAINST PROPERTY ARE THE ONLY 

VALID OFFENSES

A Segment Action Type of W = Time-Window Submission or M = Modify was

submitted for Recovered Property on a Property Segment (Level 3). When

submitted, all associated offense codes must allow for a recovered property

segment. In this instance, offense codes other than those mentioned were

submitted.

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

375 MANDATORY FIELD WITH THE PROPERTY LOSS CODE ENTERED

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.

376 DUPLICATE PROPERTY SEGMENT ON MAGNETIC MEDIA (TYPE LOSS = 

[loss-code])

When a Group “A” Incident Report is submitted, the individual segments

comprising the incident cannot contain duplicates. In this case, two property 

segments were submitted having the same entry in Data Element 14 (Type

Property Loss/Etc.).

377 PROPERTY SEGMENT A-O-F ADDED ON [yyyymmdd] RECOVERY DATE = 

[yyyymmdd]

A Property Segment (Level 3) was submitted with a Segment Action Type of 
Error Numbers and Messages

107

W = Time-Window Submission that is already on the FBI’s database. Since the

record is Already-On-File (AOF), it cannot be added again in this manner. Either

delete and resubmit, or submit as a modify.

378 ATTEMPT TO ADD OTHER THAN RECOVERED PROPERTY IS NOT ALLOWED

A Segment Action Type of W = Time-Window Submission or M = Modify was

submitted for a Property Segment (Level 3). Accordingly, Data Element 14 (Type

Property Loss/Etc.) must be 5 = Recovered. In this instance, a code other than 

5 = Recovered was submitted.

379 ATTEMPT TO MODIFY OTHER THAN RECOVERED PROPERTY IS NOT

ALLOWED

Property Segment (Level 3) submitted with a Segment Action Type of 

M = Modify must contain a 5 = Recovered in Data Element 14 (Type Property

Loss/Etc.).

380 CANNOT MODIFY PROPERTY—GROUP “A” ADDED [yyyymmdd] DATA

ELEMENT 3 = [yyyymmdd]

Property Segments (Level 3) submitted with a Segment Action Type of 

M = Modify can only modify a Property Segment that was previously submitted as

a W = Time-Window Submission. 

381 CANNOT DELETE PROPERTY—GROUP “A” ADDED [yyyymmdd] DATA 

ELEMENT 3 = [yyyymmdd]

Property Segments (Level 3) submitted with a Segment Action Type of 

D = Delete can only delete a Property Segment that was previously submitted as 

a W = Time-Window Submission. 

382 AN OFFENSE OF 35A MUST BE SUBMITTED WITH THIS DATA

A Property Segment was submitted with Data Element 15 (Property Description)

of 10 = Drugs/Narcotics, and Data Element 16 (Value of Property) containing

blanks. Under these circumstances, there must be an Offense Segment for 

35A = Drug/Narcotic Violations. No such offense was submitted. 

383 PROPERTY VALUE MUST BE BLANK FOR 35A (SINGLE OFFENSE)

Data Element 16 (Value of Property) has a value other than zero entered. Since
Error Numbers and Messages

108

Data Element 15 (Property Description) code is 10 = Drugs/Narcotics and the only

Crime Against Property offense submitted is a 35A = Drug/Narcotic Violations,

Data Element 16 (Value of Property) must be blank. 

384 WITH A MEASUREMENT OF “XX” (NOT REPORTED) DRUG QUANTITY MUST = 1

Data Element 21 (Estimated Quantity) does not have a value of 1 where 

XX = Not Reported was entered for Data Element 22 (Type Measurement). 

Submission of a Not Reported indication requires that a value of 1 also be

submitted as a quality assurance check. Once the Type Measurement has been

determined, a Group “A” Incident Report containing the completed data should be

resubmitted.

387 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

To ensure that 35A-35B Drug/Narcotic Offenses-Drug Equipment Violations

are properly reported, Data Element 15 (Property Description) of 11 = Drug/

Narcotic Equipment is not allowed with only a 35A Drug/Narcotic Violation.

Similarly, 10 = Drugs/Narcotics is not allowed with only a 35B Drug Equipment

Violation.

388 NUMBER STOLEN IS LESS THAN NUMBER OF VEHICLE CODES

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 unknown (00).

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 unknown (00).
Error Numbers and Messages

109

390 ILLOGICAL PROPERTY DESCRIPTION FOR THE OFFENSE(S) SUBMITTED

A property code was entered in Data Element 15 (Property Description) that is

illogical for the property offense.

Either the offense was classified incorrectly in Data Element 6 (UCR Offense

Code) or the wrong property description code was entered. For example, 

18 = Livestock would be an illogical object of a Larceny/Pocket-Picking offense.

391 PROPERTY VALUE MUST BE ZERO FOR DESCRIPTION [property description code]

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

392 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. (This error was formerly error number 341, a warning

message.)

Victim Segment Errors

Error

Number Message

401 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

402 CONTAINS NONNUMERIC ENTRY

Must contain numeric entry with zero left-fill.

404 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contain a value that is not specified 

within Volume 1, section VI.
Error Numbers and Messages

110

406 ERROR - DUPLICATE VALUE=[value]

The 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 age-range was being attempted. If so, the field must contain 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.

415 CANNOT HAVE EMBEDDED BLANKS BETWEEN FIRST AND LAST NONBLANK

CHARACTERS

Data Element 2 (Incident Number) contains embedded blanks between the first and

last significant characters.

416 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Element 2 (Incident Number) must be left-justified with blank right-fill. 

Since the number is less than 12 characters, it must begin in position 1; one or

more blanks were entered starting in position 1 followed by the data.

417 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Data Element 2 (Incident Number) can only have character combinations of A
Error Numbers and Messages

111

through Z, 0 through 9, hyphens, and/or blanks. For example, 89-123-SC is valid,

but 89+123*SC is invalid.

419 DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES

Data Element 31 (Aggravated Assault/Homicide) can only be entered when one or

more Data Element 24 (Victim Connected to UCR Offense Codes) entries are: 

09A = Murder and Nonnegligent Manslaughter

09B = Negligent Manslaughter

09C = Justifiable Homicide

13A = Aggravated Assault

Data Element 33 (Type Injury) can only be entered when one or more Data

Element 24 (Victim Connected to UCR Offense Codes) entries are: 

100 = Kidnaping/Abduction

11A = Forcible Rape

11B = Forcible Sodomy

11C = Sexual Assault With An Object

11D = Forcible Fondling

120 = Robbery

13A = Aggravated Assault

13B = Simple Assault

210 = Extortion/Blackmail

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 10

Data Element 35 (Relationship of Victim to Offender) contains a relationship of

SE = Spouse. When this is so, the age of the victim cannot be less than 10 years.

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
Error Numbers and Messages

112

segments were submitted having the same entry in Data Element 23 (Victim

Sequence Number).

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.

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.

456 ONLY ONE VALUE GREATER THAN OR EQUAL TO 10 CAN BE ENTERED

Data Element 31 (Aggravated Assault/Homicide Circumstances) was entered with

two entries, but was rejected for one of the following reasons:

1) Value 10 = Unknown Circumstances is mutually exclusive with any other

value.

2) More than one category (i.e., Aggravated Assault, Negligent Manslaughter,

etc.) was entered.

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

459 NEED A CRIME AGAINST PERSON OR ROBBERY FOR DATA TO BE ENTERED
Error Numbers and Messages

113

Data Element 34 (Offender Numbers To Be Related) was entered but should only

be entered if one or more of the offenses entered into Data Element 24 [Victim 

Connected to UCR Offense Code(s)] is a Crime Against Person or is a Robbery

Offense (120). None of these types of offenses were entered. 

460 RELATIONSHIP MUST BE ENTERED WHEN AN OFFENDER NUMBER (34) EXISTS

Corresponding Data Element 35 (Relationship of Victim to Offenders) data must

be entered when Data Element 34 (Offender Numbers To Be Related) is entered

with a value greater than 00.

461 VICTIM TYPE CANNOT EQUAL “S” WITH AN OFFENSE OF 220

Data Element 25 (Type of Victim) cannot have a value of S = Society/Public when

the offense is 220 = Burglary/Breaking and Entering.

462 INVALID AGGRAVATED ASSAULT/HOMICIDE FOR 13A OFFENSE

An Offense Segment (Level 2) was submitted for 13A = Aggravated Assault. 

Accordingly, Data Element 31 (Aggravated Assault/Homicide Circumstances) can

only have codes of 01 through 06 and 08 through 10. 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

Data Element 24 (Victim Connected to UCR Offense Codes) contains a Crime

Against Person, but Data Element 25 (Type of Victim) is not I = Individual.

465 ENTRY FOR TYPE OF VICTIM MUST BE “S” WHEN THIS OFFENSE CODE IS 

ENTERED

Data Element 24 (Victim Connected to UCR Offense Codes) contains a Crime

Against Society, but Data Element 25 (Type of Victim) is not S = Society.

466 OFFENSE MUST BE SUBMITTED AS LEVEL 2 RECORD IF VICTIM IS CONNECTED
Error Numbers and Messages

114

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. 

467 ENTRY FOR TYPE OF VICTIM CANNOT BE “S” WHEN THIS OFFENSE CODE

 IS ENTERED

Data Element 24 (Victim Connected to UCR Offense Codes) contains a Crime

Against Property, but Data Element 25 (Type of Victim) is S = Society. This is

not an allowable code for Crime Against Property offenses.

468 RELATIONSHIP CANNOT BE ENTERED WHEN RELATED TO OFFENDER

NUMBER “00”

Data Element 35 (Relationship of Victim to Offenders) 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 = Forcible Rape and 36B = Statutory Rape.

470 WHEN “VO” RELATIONSHIP IS PRESENT, MUST HAVE TWO OR MORE VICTIMS 

AND OFFENDERS

Data Element 35 (Relationship of Victim to Offenders) 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).

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
Error Numbers and Messages

115

Data Element 35 (Relationship of Victim to Offenders) has a relationship to the

offender that is not logical. In this case, the offender was entered with unknown

values for age, sex, and race. Under these circumstances, the relationship must be

entered as RU = Relationship Unknown.

474 ONLY ONE “VO” RELATIONSHIP CAN BE ASSIGNED TO A SPECIFIC OFFENDER

Two or more Victim Segments have Data Element 35 (Relationship of Victim to

Offenders) with a relationship of VO = Victim Was Offender that point to 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 

[UCR offense code] 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). Only those

circumstances listed in Volume 1, section VI, are valid for the particular offense.

478 VICTIM CONNECTED TO AN INVALID COMBINATION OF OFFENSES

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 

offenses of aggravated assault.
Error Numbers and Messages

116

Note: Aggravated assault is a lesser included offense of murder, forcible rape,

forcible 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, forcible rape, forcible sodomy, sexual assault with an object,

forcible fondling, and robbery.

4) Intimidation - Intimidation is a lesser included offense of murder, aggravated 

assault, forcible rape, forcible sodomy, sexual assault with an object, forcible 

fondling, and robbery.

5) Negligent Manslaughter - Murder, aggravated assault, simple assault, and

intimidation are mutually exclusive offenses. Uniform Crime Reporting

Handbook, NIBRS Edition, page 17, defines negligent manslaughter as “The

killing of another person through negligence.” Page 12 of the same publication

shows that assault offenses are characterized by “unlawful attack[s].” 

6) Forcible Rape - Aggravated assault, simple assault, intimidation, and forcible 

fondling are lesser included offenses of forcible rape.

Incest and statutory rape are mutually exclusive offenses and cannot occur with

forcible rape. The prior two offenses involve consent, while the latter involves

forced action against the victim’s will.

7) Forcible Sodomy - Aggravated assault, simple assault, intimidation, and 

forcible fondling are lesser included offenses of forcible sodomy.

Incest and statutory rape are mutually exclusive offenses and cannot occur 

with forcible sodomy. The prior two offenses involve consent, while the latter 

involves forced action against the victim’s will.

8) Sexual Assault with an Object - Aggravated assault, simple assault, 

intimidation, and forcible 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 forced action against the victim’s will.

9) Forcible Fondling - Simple assault and intimidation are lesser included offenses

of forcible fondling.
Error Numbers and Messages

117

Incest and statutory rape are mutually exclusive offenses and cannot occur 

with forcible fondling. The prior two offenses involve consent, while the latter

involves forced action against the victim’s will.

Note: Forcible fondling is a lesser included offense of forcible rape, forcible

sodomy, and sexual assault with an object.

10) Incest - Forcible rape, forcible sodomy, sexual assault with an object, and 

forcible fondling are mutually exclusive offenses. Incest involves consent, 

while the prior offenses involve forced sexual relations against the victim’s 

will.

11) Statutory Rape - Forcible Rape, forcible sodomy, sexual assault with an 

object, and forcible fondling are mutually exclusive offenses. Statutory rape 

involves consent, while the prior offenses involve forced 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.

The chart on the following page shows the NIBRS offenses that cannot occur

to the same victim in the same incident.
Error Numbers and Messages

118

09A - Murder X X X X X

09B - Negligent Manslaughter X X X X X

11A - Forcible Rape X X X X X X X

11B - Forcible Sodomy X X X X X X X

11C - Sexual Assault w/Object X X X X X X X

11D - Forcible Fondling X X X X X X X X

120 - Robbery X X X X X X X X X X X X X

13A - Aggravated Assault X X X X X X X X X

13B - Simple Assault X X X X X X X X X X

13C - Intimidation X X X X X X X X X X

23A - Pocket-picking X X

23B - Purse-snatching X X

23C - Shoplifting X X

23D - Theft From Building X X

23E - Theft From Coin Machine X X

23F - Theft From Motor Vehicle X X

23G - Theft of Motor Vehicle Part X X

23H - All Other Larceny X X

240 - Motor Vehicle Theft X X

36A - Incest X X X X X

36B - Statutory Rape X X X X X

09C Justifiable Homicide cannot

occur with any other offense

09A - Murder09B - Negligent Manslaughter11A - Forcible Rape11B - Forcible Sodomy11C - Sexual Assault w/Object11D - Forcible Fondling120 - Robbery13A - Aggravated Assault13B - Simple Assault13C - Intimidation23A - Pocket-picking23B - Purse-snatching23C - Shoplifting23D - Theft From Building23E - Theft From Coin Machine23F - Theft From Motor Vehicle23G - Theft of Motor Vehicle Part23H - All Other Larceny240 - Motor Vehicle Theft36A - Incest36B - Statutory Rape

Each “X” on the chart where offenses intersect denotes that those two offenses cannot occur to

the same victim in an incident. 
Error Numbers and Messages

119

479 SIMPLE ASSAULT (13B) CANNOT HAVE MAJOR INJURIES

A Simple Assault (13B) was 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 Aggravated Assault (13A) or the victim’s injury

should not have been entered as major.

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 MUST BE LESS THAN [maximum for state] FOR STATUTORY

RAPE (36B)

Among the states, the age at which a victim is considered a statutory rape victim

varies. The victim’s age exceeds the maximum age possible for a statutory rape in

the state.

Offender Segment Errors

Error

Number Message

501 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

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—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contain a value that is not specified

within Volume 1, section VI. 
Error Numbers and Messages

120

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 age-range 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

Data Element 2 (Incident Number) contains embedded blanks between the first and

last significant characters. 

516 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Element 2 (Incident Number) must be left-justified with blank right-fill. 

Since the number is less than 12 characters, it must begin in position 1; one or

more blanks were entered starting in position 1 followed by the data.

517 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

Data Element 2 (Incident Number) can only have character combinations of A

through Z, 0 through 9, hyphens, and/or blanks. For example, 89-123-SC is valid,

but 89+123*SC is invalid.

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 10

Data Element 35 (Relationship of Victim to Offender) contains a relationship of

SE = Spouse. When this is so, the age of the offender cannot be less than 10
Error Numbers and Messages

121

years.

551 DUPLICATE OFFENDER SEGMENT ON TAPE

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), 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. 

553 SEX OF VICTIM AND OFFENDER DOES NOT REFLECT THE RELATIONSHIP

Data Element 35 (Relationship of Victim to Offenders) has a relationship that is

inconsistent with the offender’s sex. The sex of the victim and/or offender must

reflect the implied relationship. For example, if the relationship of the victim to

offender is SE = Spouse, then the victim’s sex cannot be the same as the offender’s

sex.

The following relationships must reflect either the Same or Different sex codes

depending upon this relationship:

Relationship Sex Code

BG = Victim was Boyfriend/Girlfriend Different

XS = Victim was Ex-Spouse Different

SE = Victim was Spouse Different

CS = Victim was Common-Law Spouse Different

HR = Homosexual Relationship Same 

554 AGE OF VICTIM AND OFFENDER DOES NOT REFLECT THE RELATIONSHIP

Data Element 35 (Relationship of Victim to Offenders) 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.
Error Numbers and Messages

122

The following relationships must be consistent with the victim’s age in relation to

the offender’s age:

Relationship Victim’s Age Is

CH = Victim was Child Younger 

PA = Victim was Parent Older 

GP = Victim was Grandparent Older 

GC = Victim was Grandchild Younger 

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.

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

In order 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.

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

559 OFFENDER DATA MUST BE PRESENT IF OFFENSE CODE IS 09C, JUSTIFIABLE 

HOMICIDE

The incident was submitted with Data Element 6 (UCR Offense Code) value of

09C = Justifiable Homicide, but unknown information was submitted for all the 
Error Numbers and Messages

123

offender(s). At least one of the offenders must have known information for Age,

Sex, and Race.

560 VICTIM’S SEX CANNOT BE SAME AS ALL OFFENDERS FOR OFFENSES OF

11A AND 36B

The victim connected to the 11A (UCR Offense Code for Forcible Rape) or 36B

(UCR Offense Code for Statutory Rape) offense had the same sex (Data Element 27)

as all of the offenders submitted for the incident. At least one offender must have

a different sex than the victim.

Arrestee Segment Errors

Error

Number Message

601 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

602 CONTAINS NONNUMERIC ENTRY

Data Element 40 (Arrestee Sequence Number) must be numeric entry of 01 to 99

with zero left-fill.

604 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contains a value that is not specified

within Volume 1, section VI. 

605 [An Appropriate DATE Error Message]

Data Element 42 (Arrest Date) date components 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.

The date cannot be greater than that entered within the Month of Tape and Year of

Tape fields on the data record. For example, if Month of Tape and Year of Tape

are 06/1999, the date entered cannot be 07/01/1999 or greater. 

The error message will pinpoint what error occurred. For example, DAT11:
Error Numbers and Messages

124

MONTH EXCEEDS 12 and DAT14: DAY EXCEEDS 31 are some of the date

error messages that are displayed.

606 ERROR - DUPLICATE VALUE=[value]

Data Element 46 (Arrestee Was Armed With) 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, the entry shown between the brackets

in [value] above 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 age-range 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

The data element in error contains embedded blanks between the first and last

significant characters. 

616 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

Data Elements 2 (Incident Number) and 41 (Arrest Transaction Number) must be

left-justified; one or more blanks were entered starting in position 1 followed by

the data.

617 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS
Error Numbers and Messages

125

Data Elements 2 (Incident Number) and 41 (Arrest Transaction Number) can only

have character combinations of A through Z, 0 through 9, hyphens, and/or blanks. 

For example, 89-123-SC is valid, but 89+123*SC is invalid.

620 ARREST DATE CANNOT PREDATE BASE DATE

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have Data Element 42 (Arrest Date) earlier

than the Base Date.

This also applies to any subsequent M = Modify of a previously submitted 

W = Time-Window Submission.

621 JUSTIFIABLE HOMICIDE IS NOT A VALID WINDOW OFFENSE 

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

W = Time-Window Submission cannot have a UCR Offense Code of 

09C = Justifiable Homicide within the window offense area on the data record. By

definition a justifiable homicide never involves an arrest of the offender (the person

who committed the justifiable homicide).

This also applies to any subsequent M = Modify of a previously submitted 

W = Time-Window Submission.

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

640 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, then the 

disposition must be entered.

These circumstances were flagged by the computer as a possible discrepancy

between age and disposition and should be checked for possible correction by the

participant.

641 WARNING - ARRESTEE HAD AN AGE OF 99 OR OLDER 
Error Numbers and Messages

126

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.

652 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

disposition must be entered.

653 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

juvenile disposition cannot be entered 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.

655 WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN “A” IN THE AUTO

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

A weapon code other than those mentioned was entered with the automatic

indicator. An automatic weapon is, by definition, a firearm.

656 THIS ARRESTEE EXCEEDED THE NUMBER OF OFFENDERS (nn) ON 

THE GROUP “A” INCIDENT

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.

657 VALID VALUES FOR WINDOW CLEARANCE INDICATOR ARE “Y” OR “N”
Error Numbers and Messages

127

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

W = Time-Window Submission must have a Y or N in the Window Clearance

Indicator (position 80 of the Segment).

658 MUST BE BLANK WHEN ACTION TYPE IS NOT “W” (WINDOW)

Arrestee Segments (Level 6) submitted with a Segment Action Type other than

W = Time-Window Submission must have a blank in the Window Clearance

Indicator (position 80 of the Segment) and no UCR Offense Codes can be entered

in the Window UCR Offense Code section (positions 81 through 110).

659 AN OFFENSE MUST EXIST WHEN ACTION TYPE = “W” (WINDOW)

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

W = Time-Window Submission must have at least one UCR Offense Code entered

in the Window UCR Offense Code section (positions 81 through 110).

660 GROUP “A” INCIDENT REPORT NOT ON FILE

The initial Group “A” Incident Report associated with the current submission is

not in the FBI’s database. The Arrestee Segment (Level 6) submitted with a

Segment Action Type of A = Add was rejected because the incident is not in the

FBI’s database. 

661 DUPLICATE ARRESTEE SEGMENT ON FILE—ADDED ON [yyyymmdd]

When a Group “A” Incident Report or Segment Action Type of A = Add

[Arrestee] is submitted, the individual segments comprising the incident cannot

contain duplicates. In this case, two arrestee segments have the same entry in Data

Element 40 (Arrestee Sequence Number).

662 CANNOT DELETE AN ARREST WHEN GROUP “A” INCIDENT REPORT ON FILE

A submission was made to delete an Arrest Segment from a Group “A” Incident

Report currently active in the FBI’s database. The request was rejected because

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

D = Delete must have been previously submitted as a W = Time-Window

Submission.

For some reason the participant’s computer links the incident with a Time-Window

Arrest Segment instead of the original Group “A” Incident Report that is currently

active in the FBI’s database. 

663 CANNOT MODIFY AN ARREST WHEN GROUP “A” INCIDENT REPORT ON FILE

A submission was made to modify an Arrest Segment on a Group “A” Incident

Report currently active in the FBI’s database. The request was rejected because
Error Numbers and Messages

128

Arrestee Segments (Level 6) submitted with a Segment Action Type of 

M = Modify must have been previously submitted as a W = Time-Window

Submission.

For some reason the participant’s computer links the incident with a Time-Window

Arrest Segment instead of the original Group “A” Incident Report that is currently

active in the FBI’s database. 

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.

665 ARREST DATE CANNOT BE BEFORE THE INCIDENT START DATE

Data Element 42 (Arrest Date) cannot be earlier than Data Element 3 (Incident

Date/Hour). A person cannot be arrested before the incident occurred.

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

668 ARRESTEE RECORD PREVIOUSLY SUBMITTED WITH A “Y” IN THE 

CLEARANCE BYTE

This error involves two or more Arrestee Segments (Level 6) in the same incident,

where two or more contain a Y in the Window Clearance Indicator (position 80 of

the Segment). Only one of the arrests can have this indicator value of Y. 

These were submitted as W = Time-Window Submission segments.

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
Error Numbers and Messages

129

Data Element 45 (UCR Arrest Offense Code) was entered with 09C = Justifiable

Homicide. This is not a valid arrest offense.

671 GROUP “B” OFFENSE CODES CANNOT BE ENTERED IN POSITIONS 81-110 ON 

SEGMENT 6

A Segment Action Type of W = Time-Window Submission contains one or more

Group “B” offense codes. Only Group “A” Offense Codes are allowed in these

positions for this type of submission.

Group “B” Arrest Report Errors

Error

Number Message

701 MUST BE PRESENT—MANDATORY FIELD

The data field must be entered; it is required.

702 CONTAINS NONNUMERIC ENTRY

Data Element 40 (Arrestee Sequence Number) must be numeric entry of 01 to 99

with zero left-fill.

704 INVALID DATA VALUE—NOT ON FBI VALIDATION TABLE

The data within the referenced data element contain a value that is not specified

within Volume 1, section VI.

705 [An Appropriate DATE Error Message]

Data Element 42 (Arrest Date) date components 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.

The date cannot be greater than that entered within the Month of Tape and Year of

Tape fields on the data record. For example, if Month of Tape and Year of Tape

are 06/1999, the date entered cannot be 07/01/1999 or greater. The error message

will pinpoint what error occurred. For example, DAT11: MONTH EXCEEDS 12

and DAT14: DAY EXCEEDS 31 are some of the date error messages that are

displayed.

706 ERROR - DUPLICATE VALUE=[value]
Error Numbers and Messages

130

Data Element 46 (Arrestee Was Armed With) contains multiple data values. When

more than one code is entered, none can be duplicate codes.

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, the entry shown between the brackets

in [value] above 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

The data element in error contains embedded blanks between the first and last

significant characters. 

716 MUST BE LEFT-JUSTIFIED—BLANK DETECTED IN FIRST POSITION

The data element in error must be left-justified with blank right-fill. Since the

number is less than 12 characters, it must begin in position 1; one or more blanks

were entered starting in position 1 followed by the data.

717 CANNOT HAVE CHARACTERS OTHER THAN A-Z, 0-9, HYPHENS, AND/OR BLANKS

The data element in error can only have character combinations of A through Z, 0

through 9, hyphens, and/or blanks. For example, 89-123-SC is valid, but

89+123*SC is invalid.

720 ARREST DATE CANNOT PREDATE BASE DATE
Error Numbers and Messages

131

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. 

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

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

These circumstances were flagged by the computer as a possible discrepancy

between age and disposition and should be checked for possible correction by the

participant.

741 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 is over 98 years old. The submitter should verify that 99 = Over 98

Years Old is not being confused the with 00 = Unknown.

751 ARRESTEE NUMBER ALREADY EXISTS

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

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

disposition must be entered.

753 FOR AGE GREATER THAN 17 DISPOSITION SHOULD NOT BE ENTERED

Data Element 52 (Disposition of Juvenile) was entered, but Data Element 47 (Age
Error Numbers and Messages

132

of Arrestee) is 18 or greater. Whenever an arrestee’s age indicates an adult, the

juvenile disposition cannot be entered 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.

755 WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN “A” IN THE AUTO

INDICATOR

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.

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.

758 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 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
Error Numbers and Messages

133

Data Element 45 (UCR Arrest Offense). The offense code submitted is not a

Group “B” offense code.

761 AGE MUST BE 01-17 FOR A RUNAWAY OFFENSE

Data Element 47 (Age of Arrestee) must be 01 through 17 for offense code of 

90I = Runaway on a Group “B” Arrest Report.