LIBRS Validation Specifications
LIBRS Specifications Documentation
This document contains information about the Segments, Data Elements, Requirements, Errors, and Warnings that LIBRS uses in the validation of Incident Data.
Required Segments
The LIBRS Flat File is a space-delimited file generated by following the requirements in this document. Each section of this document outlines individual Segments. Each Segment is an
individual lines in the LIBRS Flat File that contain varying information about the incident. Those bits of information are bound by the LIBRS Data Elements and their definitions/available
values.
The information from an RMS needs to be output to the LIBRS Flat File in the exact specifications that are listed in this document. If not, a number of errors will occur. These errors and
their common causes and resolutions can be found in the Data Elements Defintions section of this page.
In the event that no incident data is present for submission, the LIBRS Flat File should contain two Segments followed by a blank line (three lines in total):
Submission Header (00)
Submission Trailer (99)
[Blank Line]
Alternative Zero Submission Format (Both behave the same way, use whatever works best for you):
Submission Header (00)
Zero Record (01)
Submission Trailer (99)
Whenever you are submitting a file with data, however, the following segments should always be included for all Incidents that have a value of ‘I’ for DE C5:
00 - Submission Header
10 - Administrative Segment
20 - Offense Segment
40 - Offender Segment
41 - Offender Using Segment/Gaming Motivation
50 - Victim Segment
99 - Submission Trailer
Whenever you want to submit a Deletion to us (used to either permanently remove an Incident from being reported, or simply to delete and re-add because there are changes that
have been made to the Incident that need to be reflected) you need to ensure the following is included:
00 - Submission Header
10 - Administrative Segment (With DE C5 - Action Type = 'D')
99 - Submission Trailer
Please note in all of these cases, the Submission Header and Trailer should only occur once per file. You can use any of the action types in the same Flat File. For instance, you can
include all of the Deletes you’d like to make and the top of the file (after the Submission Header) and then follow it up with all of the Insertions that you’d like to make, or if you prefer
include the Delete line just before the Insertion Segments for the Incident; it’s purely personal preference.
Data Types in this Document
In the tables that describe the Segment Layouts, you will find the following Formats listed:
Format Symbol Format Meaning
N Numeric
A Alphabetic
A/N Alpha/Numeric
D Date
G (Space) Blank Space
LIBRS Segments
LIBRS, like NIBRS, it built up on Segments that contain different information about the Incidents that are being reported. This portion of this document outlines the LIBRS Segments, and
the building blocks (Referred to as Data Elements) That make them up.
Submission Header (00)
Description
The Submission Header contains the information related to the Agency that is submitting the LIBRS Flat File, as well as information about the file itself, such as the Reporting Period it
encompasses and the Spec Version that it was generated with (Currently we are only accepting LIBRS Spec 2.5)
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 00 1-2 2 N
C2 Submitting Agency 3-22 20 A
C3 Submission Date 23-30 8 D
C4 Reporting Period 31-36 6 D
C10 Software ID 37-41 5 A/N
C11 Software Version 42-51 10 A/N
C12 LIBRS Spec Indicator 52-54 3 A/N
** Future Expansion Buffer 55-56 2 G (Space)
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** G (Space)
Segment 00 Errors and Explanations
Error
Error Message Explaination of Error
Number
Segment 00 needs to be the first line in the Flat File. There shouldn’t be any blank spaces
1 FIRST SEGMENT NOT 00 SEGMENT DESCRIPTOR
above it, and it should always appear ONLY on Line 1
MULTIPLE 00 SEGMENTS ENCOUNTERED.ONLY ONE PER Only one Header Segment should be present per Flat File. Multiple incidents in being in
10003
SUBMISSION ALLOWED.DATA CANNOT BE PROCESSED FURTHER. the same Flat File does not require multiple Segment 00’s.
The Second Line in a LIBRS Flat File must be one of the following Segments:
10I, 10D, 10A, 10W
10050 SEGMENTS ARE OUT OF NUMERIC ORDER FOR THIS INCIDENT 30W
60A, 60W
A Segment 00 with a Reporting Period year later than 2019 must have spec indicator ‘2.5’
90038 INVALID LIBRS SPEC
in the positions 52-54. We no longer accept LIBRS 2.2 Spec and older.
Zero Record (01)
Description
Segment 01 is used when there are no Incidents to report; IE a Zero Report. The segment can only be used when there are no Incidents present in the Flat File; there cannot be any
Segments present other than 00, 01, and 99:
-Header Segment-
01000000000000ZZ
99000003ZZ
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 01 1-2 2 N
2 Incident Number - All Zeroes "000000000000" 3-14 12 N
C8 End of Segment Marker 15-16 2 A
C9 Padding 17-150 ** A/N
Segment 01 Errors and Explanations
None
Administrative (10)
Description
The Administrative Segment contains basic information about the Incident that is being reported. It acts as the indication for LIBRS that a the next portion of Information is for a
different incident from the previous on that was processed. This segment should always be included when:
Performing an Action Type of ‘I - Insertion’ for an Incident.
Performing a ‘D - Deletion’ Action Type for an Incident.
If you desire to delete and resubmit the Incident (easiest way to process changes for us), then simply insert a Segment 10 with a ‘D’ as DE C5 , followed by the whole
incident again (including another Segment 10 with a ‘I’ for C5).
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 10 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
L53 Location of Incident (Geographical Coordinates) 25-36 12 A/N
L54 Station/Division/Precinct Identifier 37-42 6 A
3 Incident Date/Hour 43-53 11 A
4 Cleared Exceptionally 54 1 A
5 Exceptional Clearance Date 55-62 8 D
** Future Expansion Buffer 63-82 20 G (Space)
C8 End of Segment Marker 83-84 2 A
C9 Padding 85-150 ** G (Space)
Segment 10 Errors and Explanations
Error
Error Message Explaination of Error
Number
CANNOT HAVE AN INITIAL INCIDENT RECORD WITHOUT The first segment after the Submission Header when submitting new data (Action Type ‘I’)
10055
STARTING WITH RECORD SEGMENT 10 must be an Administrative Segment (10).
MISSING A MANDATORY RECORD SEGMENT FOR A COMPLETE
10075 When an Action Type of Incident Report (‘I’) is submitted, this segment must be included.
INCIDENT
Administrative Modification (11)
Description
Segment 11, Administrative Modification, is only used when performing an update to a Time Window Submission Incident (DE C5, Action Type = ‘M’). Agencies should be aware that
information submitted via time windows is stored separately by the FBI and is not combined back in with normal submissions and may or may not be reported in some publications nor
counted towards overall totals.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 11 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number 25-36 12 A
** Future Expansion Buffer 37-56 20 G (Space)
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** G (Space)
Segment 11 Errors and Explanations
Error
Error Message Explaination of Error
Number
INCIDENT NUMBERS IN SEGMENTS 11 AND 63 MUST MATCH THE When using Segment 11, the Incident Number that is included must match the one
11017
INCIDENT NUMBERS IN SEGMENTS 10 AND 60 RESPECTIVELY provided in Segment 10.
Segment 11 was either missing, or did not have a matching Action Type (DE C5)
11097 SEGMENT 11 AND/OR 63 MISSING
compared to the Incident’s Administrative Segment (Segment 10).
Offense (20)
Description
Segment 20, Offense Segment, contains information about the particular Offenses that occurred in the Incident. Note that only one Victim can be tied to an Offense, so if you have
multiple Victims of the same Offense you will need to include multiple Segment 20’s to link those Victims to the Offense.
We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 20 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
L6 Offense Sequence Number 25-27 3 N
6 Louisiana Revised Statute Number 28-39 12 A
7 Offense Attempted/Completed 40 1 A
24 Offense Connected to Victim Sequence Number 41-43 3 N
9 Location Type 44-45 2 N
10 Number of Premises Entered 46-47 2 A/N
11 Method of Entry 48 1 A
12 Type of Criminal Activity/Gang Information Nos. 1, 2 and 3 49-51 1 (3x) A
13 Type of Weapon/Force Involved Nos. 1, 2, and 3 52-60 3 (3x) A
N6 Agency Supplied NIBRS Code 61-63 3 A
70 Inchoate Modifier 64-65 2 A
** Future Expansion Buffer 66-80 14 G (Space)
C8 End of Segment Marker 81-82 2 A
C9 Padding 83-150 ** G (Space)
Important Notes
Only one Victim can be related to an Offense Segment. If you have multiple Victims of the same offense, you need to include multiple Offense Segments that link to those
Victims.
Please note that DE’s 12 and 13 are actually three Data Elements Combined into one. Each instance of the Data Element is either 1 or 3 characters long and can include up to 3
instances, so long as mutually exclusive values are not used.
See Type of Criminal Activity/Gang Information Nos. 1, 2 and 3 and Type of Weapon/Force Involved Nos. 1, 2, and 3 for more details.
Segment 20 Errors and Explanations
Error
Error Message Explaination of Error
Number
MISSING A MANDATORY
10075 RECORD SEGMENT FOR When an Action Type of Incident Report (‘I’) is submitted, this segment must be included.
A COMPLETE INCIDENT
AT LEAST ONE Each Incident must have at least one Offender listed. If no specific details about the Offender are known, use ‘000’ for the Offender
14058 OFFENDER MUST HAVE Sequence Number (DE 36) to denote ‘Unknown Offender’ (NIBRS 09C is exempt from this, and must contain a known Offender).
VALUES Additionally, the number of Offender and Offender Using (Segments 40 and 41) should match.
MISSING SEGMENT 20
20000 Each Incident must have at least one Offense Segment (Segment 20) present.
(OFFENSE)
Property (30)
Description
Segment 30, Property Segment, is used to identify that Properties are involved in the listed Offenses. It only contains general information about these Properties, such as the number of
Stolen or Recovered Vehicles. Further Details are expected to be entered in Segments 31, 32, and 33.
We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 30 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
18 Number of Stolen Motor Vehicles 25-26 2 A/N
19 Number of Recovered Motor Vehicles 27-28 2 A/N
** Future Expansion Buffer 29-48 20 G (Space)
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** G (Space)
Segment 30 Errors and Explanations
Error
Error Message Explaination of Error
Number
When DE C5 (Action Type) is ‘I’, Property Segments 30 and 31 must exist submitted with an Offense
Segment (20) whose NIBRS is a ‘Crime Against Property’:
120
200, 210, 220, 240, 250, 270, 280, 290
26A, 26B, 26C, 26D, 26E
23A, 23B, 23C, 23D, 23E, 23F, 23G, 23H
PROPERTY RECORD (SEGMENT 30 & 31) MUST EXIST 510
10074
WITH THIS OFFENSE 90A, 90Z (If Applicable)
Additionally, the following Offenses are included in this requirement:
Kidnaping (100)
Gambling (39A, 39B, 39C, and 39D)
Drug/Narcotic (35A and 35B)
Segments 30 and 31 should not be included when the Incident is comprised of only the following
Offense Codes:
09A, 09B, 09C
11A, 11B, 11C, 11D
13A, 13B, 13C
PROPERTY RECORD (SEGMENT 30 & 31) CANNOT EXIT
10076 36A, 36B
WITH OFFENSES SUBMITTED
370
40A, 40B
520
90B through 90Z (If Applicable)
Property Description (31)
Description
Segment 31, Property Description, includes specific details about the Properties that are involved in the Incident. One Segment 31 should be included for each Property that is involved
in the Incident.
We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 31 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
14 Type of Property Loss / Etc. 25 1 N
15 Property Description Type 26-27 2 A/N
16 Value of Property 28-36 9 N
17 Date Recovered 37-44 8 D
20 Suspected Drug Type 45-46 2 A
21 Estimated Drug Quantity 47-59 13 A/N
22 Type Drug Measurement 60-61 2 A
P1 Property Sequence Number 62-64 3 N
** Future Expansion Buffer 65-81 17 G (Space)
C8 End of Segment Marker 82-83 2 A
C9 Padding 84-150 ** G (Space)
Segment 31 Errors and Explanations
Error
Error Message Explaination of Error
Number
When DE C5 (Action Type) is ‘I’, Property Segments 30 and 31 must exist submitted with an Offense
Segment (20) whose NIBRS is a ‘Crime Against Property’:
120
200, 210, 220, 240, 250, 270, 280, 290
26A, 26B, 26C, 26D, 26E
23A, 23B, 23C, 23D, 23E, 23F, 23G, 23H
PROPERTY RECORD (SEGMENT 30 & 31) MUST EXIST 510
10074
WITH THIS OFFENSE 90A, 90Z (If Applicable)
Additionally, the following Offenses are included in this requirement:
Kidnaping (100)
Gambling (39A, 39B, 39C, and 39D)
Drug/Narcotic (35A and 35B)
Segments 30 and 31 should not be included when the Incident is comprised of only the following
Offense Codes:
09A, 09B, 09C
11A, 11B, 11C, 11D
13A, 13B, 13C
PROPERTY RECORD (SEGMENT 30 & 31) CANNOT EXIT
10076 36A, 36B
WITH OFFENSES SUBMITTED
370
40A, 40B
520
90B through 90Z (If Applicable)
Property Modification (32)
Description
Segment 32, Property Modification, is only used when performing a Time Window Submission (Action Type ‘W’) or a Modification (Action Type ‘M’) to a Time-Window Submission.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 32 1-2 2 N
C5 Action Type (“W” or “M”, only) 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number 25-36 12
** Future Expansion Buffer 37-56 20 G (Space)
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** G (Space)
Segment 32 Errors and Explanations
None
Property/Offense (33)
Description
Segment 33, Property/Offense Relationship, is used to distinctly relate a Property to an Offense. This Segment is not mandatory, though you will most likely experience Errors if you do
not include it.
When this segment is not included, LIBRS will perform a Cross Product between all Properties and all Offenses. We have measures in place to help limit incorrect Properties from being
associted with Invalid Offenses (EG: Drugs being associated with Motor Vehicle Theft Offenses), however the best way to ensure that Properties are being appropriately linked up to
their Offenses is by including a Segment 33 for each Property/Offense Relationship.
We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 33 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
P1R Property Sequence Number Reference 25-27 3 A
L6R Offense Sequence Number Reference 28-30 3 A
** Future Expansion Buffer 31-50 20 G (Space)
C8 End of Segment Marker 51-52 2 A
C9 Padding 53-150 ** G (Space)
Important Notes:
The Property/Offense Segment is used to connect incident property (stolen, retrieved, etc.) to an offense. This connection, or relationship, is established using the Property
Sequence Number (Data Element P1) and the Offense Sequence Number (Data Element L6).
This Segment is optional in the sense that if it is missing LIBRS will interpret properties to offenses automatically using a cross product (EG all offenses are associated with all
properties). Depending on the Offenses in the Incident, this can cause LIBRS to infer properties to incompatible Offenses.
LIBRS uses the NIBRS Code of the Offenses to determine if it should apply properties to them to minimize the cases that this happens in. However, there are some NIBRS Codes
that include both ‘Crimes Against People’ and ‘Crimes Against Property’ Offenses.
EG: 13B Contains both LRS 14:35 (Simple Battery - Crime Against Person) as well as LRS 14:60 (Aggravated Burglary - Crime Against Property) that break this assumption.
Therefore it is always best to include this Segment when Properties are involved.
Successful Segment 33 Inference Example
An incident is submitted with a NIBRS 23H ‘Crime Against Property’ Offense, as well as a NIBRS 11A ‘Crime Against Person’ Offense, along with one or more properties that are intended
to be linked to the 23H Offense. Since NIBRS 11A has no related Offenses that are a ‘Crime Against Property’, if Segment 33 is missing LIBRS knows that it should not apply the
properties to the 11A Offense. As a result, LIBRS will only infer the properties to be related to the 23H Offense, successfully validating the Incident submission.
Unsuccessful Segment 33 Inference Example
An incident is submitted with a NIBRS 23H ‘Crime Against Property’ Offense, as well as a NIBRS 13B ‘Crime Against Person’ Offense, along with one or more properties that are intended
to be linked to the 23H Offense. Since 13B has some offenses that are ‘Crime Against Property’, if Segment 33 is missing LIBRS cannot know that it shouldn’t apply the properties to the
13B Offense. As a result, LIBRS will interpret all properties to be related to all offenses, which in this case will throw validation errors.
Segment 33 Errors and Explanations
Error
Error Message Explaination of Error
Number
PROPERTY MUST HAVE A VALID RELATIONSHIP TO All properties submitted within an incident must be related to at least one Offense. Please ensure that all
90018
AT LEAST ONE OFFENSE Properties are linked to an Offense through a Segment 33.
Each Property/Offense segment submitted must have unique combinations of Property Sequence Number
References (DE P1R) to Offense Sequence Number References (DE L6R).
DUPLICATE - A PRIOR PROPERTY OFFENSE
90023 SEGMENT ALREADY EXISTS WITH THE SAME
Both Properties and Offenses can both be related to multiples of each other (EG One Property to Multiple
SEQUENCE NUMBERS
Offenses), however, Property/Offense segments cannot relate a single Property to a Single Offense
multiple times.
Ivalid Combinations of NIBRS Offense Codes and Property Descriptions
There are a number of illogical combinations for various NIBRS Offense Codes (Data Element 6) having certain Property Descriptions (Data Element 15). For example, it is illogical for
Purse Snatching (NIBRS Code 23B) to be connected to property having a Property Description data value of Aircraft (01) or Livestock (18).
The table below shows invalid combinations of NIBRS Offense Codes and Property Descriptions. X’s on this table represent that the combination of the Property Description and NIBRS
Code are incompatible and should NOT be used together.
Invalid Property Descriptions 220 23A 23B 23C 23D 23E 23F 23G 23H 240
01 X X X
03 X X X X X X X X
04 X X
05 X X X X X X X X
12 X X X
15 X X X
18 X X X
24 X X X X X X X X
28 X X X X X X X X
29 X X X X X X X X X
30 X X X X X X X X X
31 X X X X X X X X X
32 X X X X X X X X X
33 X X X X X X X X X
34 X X X X X X X X X
35 X X X X X X X X X
37 X X X X X X X X
39 X X X
78 X X
Offender (40)
Description
Segment 40, Offender Segment, is used to submit information about the suspected Offender(s) that are involved in an Incident. You should have as many Offender Segments as you
have Suspects.
Offenders are linked to their Offenses by their Victims. Segment 20 - Offense Segment contains a Victim Sequence Number that denotes who the victim of the Offense was. Segment 52
- Victim/Offender Relationship then links the Offender to the Victim, which, in turn, links the Offender to the Offense.
More information and common questions and errors can be found on the LIBRS FAQ for this Segment here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 40 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
36 Offender Sequence Number 25-27 3 N
37 Age of Offender 28-30 3 A
L37 Date of Birth of Offender (LIBRS Only) 31-38 8 D
38 Sex of Offender 39 1 A
39 Race of Offender 40 1 A
8A Bias Motivation / Bias Crime Type 41-42 2 A
39A Ethnicity of Offender 43 1 A
** Future Expansion Buffer 44-62 20 G (Space)
C8 End of Segment Marker 63-64 2 A
C9 Padding 65-150 ** G (Space)
Segment 40 Errors and Explanations
Error
Error Message Explaination of Error
Number
MISSING A MANDATORY RECORD SEGMENT FOR A COMPLETE
10075 When an Action Type of Incident Report (‘I’) is submitted, this segment must be included.
INCIDENT
THIS ARRESTEE EXCEEDED THE NUMBER OF OFFENDERS ON Number of Arrestee Segments (Segment 60) cannot exceed the number of Offender
16056
THE INCIDENT Segments (Segment 40)
Offender Using/Gaming Motivation (41)
Description
Segment 41, Offender Using/Gaming, is used to denote additional aspects about the potential motive behind an Offender’s behavior.
More information and common questions and errors can be found on the LIBRS FAQ for this Segment here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 41 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
36 Offender Sequence Number 25-27 3 N
8 Offender Suspected of Using / Gaming Motivation 28 4 (4x 1 Char) A
** Future Expansion Buffer 32-48 20 G (Space)
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** G (Space)
Segment 41 Errors and Explanations
Error
Error Message Explaination of Error
Number
MISSING A MANDATORY RECORD SEGMENT FOR A COMPLETE When an Action Type of Incident Report (‘I’) is submitted, this segment must be
10075
INCIDENT included.
Victim (50)
Description
Segment 50, Victim Segment, is used to report the relevent personal attributes of the Victims of the Offenses in the Incident. You should have as many Segment 50’s as you have unique
Victims. This means you should not repeat Society as a Victim for each Offense that is a Crime Against Society, and instead only have a single Segment 50 to represent it.
More information and common questions and errors can be found on the LIBRS FAQ for this Segment here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor – 50 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
25 Victim Type 28 1 A
26 Age (At Time of Incident) 29-31 3 A
L26 Date of Birth (LIBRS Only) 32-39 8 D
27 Sex 40 1 A
28 Race 41 1 A
29 Ethnicity 42 1 A
30 Resident Status 43 1 A
31 Aggravated Assault / Homicide Circumstance Nos. 1 and 2 44-47 2 (2x) N
** Deprecated Data Element 48-49 2 G (Space)
32 Additional Justifiable Homicide Circumstance 50 1 A
25A Type of Officer Activity/Circumstance 51-52 2 N
25B Officer Assignment Type 53 1 A
25C Officer ORI, Other Jurisdiction 54-62 9 A
** Future Expansion Buffer 63-68 6 G (Space)
C8 End of Segment Marker 69-70 2 A
C9 Padding 71-150 ** G (Space)
Important Notes
Data Element 31 - Aggrevated Assault/Homicide Circumstance is repeated twice. In the past this was repeated three times, however this has since been eliminated, which has
resulted in a blank space on Characters 48 and 49.
Segment 50 Errors and Explanations
Error
Error Message Explaination of Error
Number
MISSING A MANDATORY RECORD SEGMENT FOR A
10075 When an Action Type of Incident Report (‘I’) is submitted, this segment must be included.
COMPLETE INCIDENT
VICTIMS OF ‘I’ OR ‘L’ MUST BE ASSOCIATED WITH AT
According to the NIBRS IEPD Requirements (Error 085), when there is more than one Offender in an
LEAST TWO OFFENDERS WHEN MULTIPLE SEGMENT
90044 Incident, and a Victim is tied to a Crime Against Person or a Robbery and is also a Victim Type of ‘I -
40’S EXIST AND CRIME IS AGAINST PERSON OR
Individual’ or ‘L - Law Enforcement’, then the Victim must be associated with at least two Offenders.
ROBBERY
Victim Injury (51)
Description
Segment 51, Victim Injury, includes information about the sustained Injuries of a Victim of an Offense.
The main thing to note about it is that it required to be included when a Segment 50 (Victim Segment) is present with a Victim Type of ‘I - Individual’ or ‘L - Law Enforcement’, and the
Offense is of one of the following NIBRS Codes:
100, 120
11A, 11B, 11C, 11D
210
13A, 13B
64A, 64B
90Z
Otherwise, it should NOT be included. Additionally, you should not supply a Segment 51 without an Injury Type (DE 33).
More information and common questions and errors can be found on the LIBRS FAQ for this Segment here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 51 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
33 Injury Type 28 1 A
** Future Expansion Buffer 29-48 20 G (Space)
C8 End of Segment Marker 49-50 2 A
C9 Padding 51-150 ** G (Space)
Segment 51 Errors and Explanations
Error
Error Message Explaination of Error
Number
DATA MUST BE ENTERED FOR SPECIFIC Segment 51 must be present for each Victim Sequence Number (DE 23) that has a Victim Type (DE 25) of ‘I -
15020
OFFENSES Individual’ or ‘L - Law Enforcement’.
Victim/Offender Relation (52)
Description
Segment 52, Victim/Offender Relationship, is what links the Victims to the Offenders, and thereby links the Offenders to the Offenses.
If a Victim of Type ‘I - Individual’ or ‘L - Law Enforcement’ is present in the Incident, and the Offense is a Crime Against Person or a Robbery, then this Segment needs to be included.
Otherwise it should NOT be included.
More information and common questions and errors can be found on the LIBRS FAQ for this Segment here.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 52 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
23 Victim Sequence Number 25-27 3 N
34 Offender Number to be Related 28-30 3 N
35 Relationship of Victim to Offender 31-32 2 A
** Future Expansion Buffer 33-52 20 G (Space)
C8 End of Segment Marker 53-54 2 A
C9 Padding 55-150 ** G (Space)
Segment 52 Errors and Explanations
Error
Error Message Explaination of Error
Number
MISSING VICTIM/OFFENDER SEGMENT
Victim/Offender Relationship (Segment 52) must be present for each Victim Sequence Number (DE 23) that has a
15005 OR RELATIONSHIP (SEGMENT 52 OR DE
Victim Type (DE 25) of ‘I - Individual’ or ‘L - Law Enforcement’ that is a victim of a Crime Against Person or a Robbery.
L6)
SEGMENT 52 MISSING–MUST BE
22081 This Segment must be included if the Victim is of Type I or L.
PRESENT IF VICTIM TYPE IS ‘I’ OR ‘L’
Arrestee (60)
Description
Segment 60, Arrestee Segment, is used to define whether or not an Offender was arrested for an Offense or not. Since Offenders can be known but not apprehended, there needs to be
another Segment that details the information about their Arrest when the time comes.
Segment 60 can also be used with Action Type ‘A - Arrest’ in order to add Arrest Information to an already submitted Incident. Though, it’s recommended to simply generate a Delete
for the Incident and then resubmit it.
You should include an Arrestee Segment for each Offender that has been arrested in relation to an Offense. While NIBRS allows Arrestees to not be linked to an Offender (EG Someone
that’s not listed on the Incident is listed as the arrestee for it), LIBRS does not allow this. Any Arrestee that’s present in this Segment should also have a Segment 40 (Offender)
associated with them.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 60 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrest Sequence Number 25-27 3 N
41 Arrest Number/Local Booking Number for Arrest* 28-39 12 A
L55 Arrest Transaction Number 40-54 15 A/N
L40 Arrestee Name 55-74 20 A
42 Arrest Date 75-82 8 D
43 Arrest Type 83 1 A
44 Multiple Arrestee Segment Indicator 84 1 A
47 Age (At Time of Arrest) 85-87 3 A
L47 Date of Birth 88-95 8 D
48 Sex 96 1 A
49 Race 97 1 A
50 Ethnicity 98 1 A
51 Resident Status 99 1 A
52 Disposition of Arrestee Under 18 100 1 A
C6 Clearance Indicator (to be used for Time Window Submission only) 101 1 A
** Future Expansion Buffer 102-118 17 G (Space)
C8 End of Segment Marker 119-120 2 A
C9 Padding 121-150 ** G (Space)
Important Notes
Data Element 52 - Disposition of Arrestee Under 18 must be included for any arrestee that is 17 or younger.
Previously, Louisiana Law stated that 17 Year Olds were Adults rather than Juveniles, however this changed in 2020, which has led to a bit of confusion about this Data
Element.
Data Element 44 - Multiple Arrestee Indicator should be used when an Offender is Arrested and associated with more than one Incident. The arrest of the Individual will clear all
Incidents that they are a part of, however it should not be counted that two arrests were made. The Multiple Arrestee Indicator allows you to specify that an individual was
arrested for another Incident, which has cleared this Incident by arrest, but to not count this arrest for Crime Statistics.
Segment 60 Errors and Explanations
Error
Error Message Explaination of Error
Number
THIS ARRESTEE EXCEEDED THE NUMBER OF Number of Arrestee Segments (Segment 60) cannot exceed the number of Offender Segments
16056
OFFENDERS ON THE INCIDENT (Segment 40)
The Arrestee Segment submitted with an Action Type of ‘A’ (Add an Arrest) was rejected because the
16060 INCIDENT REPORT NOT ON FILE
incident is not on the LIBRS database.
Arrestee Armed (61)
Description
Segment 61, Arrestee Armed, denoted the details about whether or not an Arrestee was armed with a weapon at the time of their arrest. This segment should appear for each Segment
60 (Arrestee) Segment that is present in the Incident Report.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 61 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrestee Sequence Number 25-27 3 N
46 Arrestee Armed With at Time of Arrest 28-30 3 A
** Future Expansion Buffer 31-50 20 G (Space)
C8 End of Segment Marker 51-52 2 A
C9 Padding 53-150 ** G (Space)
Segment 61 Errors and Explanations
Error
Error Message Explaination of Error
Number
SEGMENT 61 MISSING–MUST HAVE ONE PER An Arrestee Armed Segment (Segment 61) is required for each Arrestee Segment (Segment 60) that is
16080
ARRESTEE SEGMENT present in the LIBRS Incident Report.
SEGMENTS 61 and 62 CAN ONLY BE PRESENT An Arrestee Armed Segment (Segment 61) is not to be included unless there is an Arrestee Segment
16099
WHEN SEGMENT 60 EXISTS (Segment 60) present in the LIBRS Incident Report.
Arrestee Statute (62)
Description
Segmetn 62, Arrestee Statute, is what’s used to say what Statute an Arrestee was Arrested for. At this time, Data Element L45 - Arrest Connection to Offense is optional, however if it is
to be included there are particular requirements for it. Please review the definition of the Data Element to ensure that it’s being correctly applied.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 62 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
40 Arrestee Sequence Number 25-27 3 N
45 Louisiana Revised Statute Number of Arrest 28-39 12 A
L45 Arrest Connection to Offense 40-54 15 A
N45 Agency Supplied NIBRS Code 55-57 3 A
70 Inchoates Modifier 58-59 2 A
** Future Expansion Buffer 60-74 15 G (Space)
C8 End of Segment Marker 75-76 2 A
C9 Padding 77-150 ** G (Space)
Segment 62 Errors and Explanations
Error
Error Message Explaination of Error
Number
SEGMENT 62 MISSING–MUST HAVE AT LEAST ONE An Arrestee Statute Segment (Segment 62) is required for each Arrestee Segment (Segment 60) that is
16081
PER ARRESTEE SEGMENT present in the LIBRS Incident Report.
SEGMENTS 61 and 62 CAN ONLY BE PRESENT An Arrestee Statute Segment (Segment 62) is not to be included unless there is an Arrestee Segment
16099
WHEN SEGMENT 60 EXISTS (Segment 60) present in the LIBRS Incident Report.
Arrestee Modification (63)
Description
Segment 63, Arrestee Modification, is only used when making a Modification to an Arrestee’s Information that was submitted as a Time-Window Submission.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 63 1-2 2 N
C5 Action Type 3 1 A
1 ORI Number 4-12 9 A
2 Incident Number 13-24 12 A
6 Louisiana Revised Statute Number of Incident 25-36 12 A
** Future Expansion Buffer 37-56 20 A
C8 End of Segment Marker 57-58 2 A
C9 Padding 59-150 ** A/N
Segment 63 Errors and Explanations
Error
Error Message Explaination of Error
Number
INCIDENT NUMBERS IN SEGMENTS 11 AND 63 MUST MATCH THE When using Segment 63, the Incident Number that is included must match the
11017
INCIDENT NUMBERS IN SEGMENTS 10 AND 60 RESPECTIVELY one provided in Segment 60.
Segment 63 was either missing, or did not have a matching Action Type (DE C5)
11097 SEGMENT 11 AND/OR 63 MISSING
compared to the Incident’s Arrestee Segment (Segment 60).
Submission Trailer (99)
Description
Segment 99, Submission Trailer, should be the last line in your Flat File, and should only appear once per file.
Segment Layout
Data Element Number Description of Data Element Position(s) Length Format
C1 Segment Descriptor - 99 1-2 2 N
C7 Number of Segments Transferred 3-8 6 N
C8 End of Segment Marker 9-10 2 A
C9 Padding 11-150 ** A/N
Important Notes
Data Element C7 - Number of Segments Transferred should be a six-digit long number that is front-padded with 0’s that contains the number of lines in the Flat File (Including
the Header and Trailer Segments). For instance, if Segment 99 appears on line number 512 in your Flat File, DE C7 should be ‘000512’.
Segment 99 Errors and Explanations
Error
Error Message Explaination of Error
Number
LAST LINE OR SEGEMENT
19901 Last line in data submission is not Segment 99 (Submission Trailer).
NOT 99 SEGMENT TYPE
NUMBER OF SEGMEMTS
Number of Segments Transferred field (Data Element C7) in Submission Trailer is not a valid numeric field. The Number of
FIELD IN 99 SEGMENT IS
19902 Segments Transferred should be a number with front-padded zeros (0) to make up a six-digit number. EG If there are 25 lines in
NOT A VALID NUMERIC
the Flat File (including the Footer Segment), then The Number of Segments Transferred should be ‘000025’.
FIELD
NUMBER OF SEGMENTS ON
Number of Segments Transferred (Data Element C7) in Submission Trailer Segment does not match Record Count for data
SUBMISSION TRAILER DOES
19903 submission. The number of lines in the Flat File, including the Header and Footer Segments, is the number that should be used in
NOT MATCH RECORD
the Number of Segments Transferred (front-padded with zeros to make a six-digit number).
COUNT
LIBRS Data Element Definitions
This portion of the document contains information about the specific requirements that go into each of the LIBRS Data Elements. For the short list of available values for each Data
Element, go here.
ORI Number (1)
Description: NCIC originating agency identifier number. This field should follow the format of ‘LAXXXXXXX’, where XXXXXXX is the 7-digit code for the Agency’s ORI Number.
Data Characteristics: 9 Character Numeric/Alpha. Cannot be blank, and must start with ‘LA’.
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 This is a required Data Element, and it cannot be left blank. 10001
MANDATORY FIELD
Must be a valid 9-character NCIC number, where the last 2 positions of the ORI must reflect ‘00’ for all state and
NOT A VALID ORI–NOT
2 local agencies. This Error will also be thrown if the ORI Number that is used in the various Segments of an Incident 10052
ON LIBRS ORI FILE
Report does not match the ORI Number Specified in Segment 00 (Header Segment)
ALL ORI NUMBERS
MUST BE THOSE OF
3 First two positions must be the code of the state ‘LA’ in which the incident occurred. 10059
AGENCIES IN
LOUISIANA (LA)
VALUE MUST MATCH
THE VALUE SUPPLIED
4 The ORI Number Specified in Segments 20, 40, 41, and 50 need to match the ORI Number in Segment 10. 90042 IN ADMINISTRATIVE
SEGMENT (SEGMENT
10)
Details:
This is the 9-character NCIC Originating Agency Identifier (ORI) assigned to every law enforcement agency in Louisiana. For state or local agency submissions, the last two
positions must be “00”.
Incident Number (2)
Description: Agency unique, in-house assigned case number. It is used to link subsequent update submissions to the original submission. This number will be encrypted prior to any
dissemination of data to ensure that the recipient cannot identify the actual case. The Incident Number should contain the current year as part of it when possible to prevent
duplication/reuse of incident numbers across different years. EG 20-000001 for the first incident of 2020.
Data Characteristics: 12 Character Alpha. Cannot be Blank, and must be unique for each Agency (IE Agency A and B can both have an Incident Number 20-00001, but Agency A cannot
have two Incidents with Incident Number 20-00001).
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 This is a required Data Element, and it cannot be left blank. 10001
MANDATORY FIELD
MUST BE LEFT -
Incident Numbers be left justified, 12 or less characters long, include only Letters, Numbers, Hyphens, or Blank JUSTIFIED–BLANK
2 10016
Spaces, and the first character in an Incident Number cannot be a blank space. DETECTED IN FIRST
POSITION
INCIDENT ALREADY
This field must be unique for each incident reported by the agency; no two incidents can have the same Incident
ON FILE–PREVIOUSLY
3 Number. Some agencies ensure uniqueness by prefixing every incident number with a two-digit year followed by a 10056
ADDED TO FILE ON
number starting with 1, while others simply increment the Incident Number by one for each new incident.
[MM/DD/YYYY]
VALUE MUST MATCH
THE VALUE SUPPLIED
4 The Incident Number Specified in Segments 20, 40, 41, and 50 need to match the Incident Number in Segment 10. 90042 IN ADMINISTRATIVE
SEGMENT (SEGMENT
10)
Definitions:
Concept of time and place provides: If more than one crime was committed by the same person or group of persons and the time and space intervals separating them were
insignificant, all of the crimes make up a single incident.
An incident is considered as one or more offenses committed by the same offender or group of offenders acting in concert at the same time and place.
Acting in concert requires that the offenders actually commit or assist in the commission of the crime(s). The offenders must be aware of, and consent to, the commission of the
crime(s); or, even if non-consenting, their actions assist in the commission of the offense(s). This is important because all of the offenders in an incident are considered to have
committed all of the offenses in the incident. If one or more of the offenders did not act in concert, then there is more than one incident involved.
Same time and place means that the time interval between the offenses and the distancebetween the offenses and the distance between the locations where they occurred
were insignificant.
Normally, the offenses must have occurred during an unbroken time duration and at the same or adjourning location(s). However, incidents can also be comprised of offenses which by
their nature involve continuing criminal activity by the same offender(s) at different times and places, as long as the activity is deemed to constitute a single criminal transaction.
Regarding these situations, the reporting agency will have to use its best judgment.
Incident Date/Hour (3)
Description: Date and Time when the incident occurred or started, or at the beginning of the time period in which it occurred, or date of report if unknown. If an incident occurred
before the agency’s Base Date it should not be reported to LIBRS; it will be rejected if it is. For the most part, this really isn’t an issue, as the Base Date for most agencies is from
somewhere in 2012. However if you do run into an error regarding it, then you should remove that Incident from being reported.
Data Characteristics: 11 Character Alpha. If Unknown, Enter the Reporting Date (MMDDYYYY) followed by an ‘R’ to indicate the date is not the actual Incident Date, but rather the
Reporting Date. Leave the Time blank in this case (Not 0’s, but Blank Spaces)
Format: MMDDYYYYXHH, Where ‘X’ is either:
‘R’ to denote that the Incident Date is not known, and the Report Date is being substituted for it
Or ‘ ‘ (G - Blank Space) to denote that the supplied value is the actual Incident Date.
Important Note:
In the process to certify an agency as LIBRS-compliant, when an agency reaches the Certification and Production stages, please note the following:
The “Base Date” for an agency is the date that agency starts sending actual, live data that both the State and FBI Retain. For most Agencies, this is the date in which they
started sending UCR data.
If an incident occurred before the agency’s “Base Date”, but was not reported to LIBRS until after your “Base Date” has been implemented; or this incident was already
reported in the UCR summary reports, this incident will be REJECTED (Error 11073).
If this happens, contact a member of the LIBRS staff at the Louisiana Commission on Law Enforcement.
If this incident was not reported until after your “Base Date” was implemented, your agency may have to submit an adjusted UCR summary form to capture these offenses.
Requirements:
Error
Requirement Requirement Description Error Message
Number
DATE ENTERED MUST
The date supplied for the Incident Date (DE 3) is not valid. Please ensure that the supplied date is in the MMDDYYYY
1 11005 BE A VALID
Format, and is not a date later than the current date.
CALENDAR DATE
REPORT INDICATOR
If the Incident Date is unknown, use the Report Date. Indicate a Report Date with an ‘R’ in the space before the hour.
2 11051 MUST BE BLANK OR
If this is the Incident Date, then leave the ‘Report’ indicator blank.
‘R’
If entered, the ‘HH’ Value of the Incident Date to denote the hour the Incident Occurred in must be between 00 and
3 23. Remember that midnight is the start of a new day, so Incidents that occur in the ‘00’ hour should be reported as 11052 INVALID HOUR ENTRY
occurring on the correct day. EG: Thursday at 11:59PM, or Friday at 12:00AM.
INCIDENT DATE
CANNOT BE AFTER
Incident Date/Hour cannot be later than the year and month the data submission file represents. (EG: A June 2019
4 11070 YEAR [YYYY] AND
data submission cannot contain incidents occurring after June).
MONTH [MM] OF
TAPE
INCIDENT
The Incident Date CANNOT be earlier than 01/01/1991 for Incident Report (‘I’) submissions. DATE/HOUR FOR ‘I’
5 11072
This edit will preclude dates that are obviously incorrect since the FBI began accepting data on this date. RECORDS CANNOT
PREDATE 01/01/1991
No data regarding an incident previously submitted under the Summary UCR reporting system can be submitted
with an incident date later than the date the agency commenced reporting.
It will be regarded as a duplicate submission and be rejected since the Summary UCR system already contains the
aggregate data for the months before LIBRS conversion.
In other words, if an agency sends Incident Based Reporting (IBR) data for the first time on 20 July 2019, all ‘Incident
Date/Hour’ (DE 3) entries for incidents, recovered property, and arrests must be within July, 2019 INCIDENT DATE
6 11073 CANNOT BE BEFORE
The exception is when Exceptional Clearances occur for a pre-IBR incident DATE ORI WENT IBR
In this case, ‘Incident Date/Hour’ (DE 3) may be earlier than July, 2019, but Exceptional Clearance Date (5) must be
within July, 2019
LIBRS maintains a table of start dates (Agency Base Dates) for every law enforcement agency in the state
Except for the above example, LIBRS will reject data submitted with an ‘Incident Date/Hour’ prior to the agency’s
Base Date (start date).
INCIDENT DATE FOR
Time Window Submissions are not allowed for Incidents Dates that are later than the Agency’s Base Date (Date they WINDOW RECORDS
7 11076
began submitting Incident-Based data). CANNOT BE AFTER
AGENCY’S BASE DATE
INCIDENT DATE (DE 3)
CANNOT BE GREATER
6 The Incident Date supplied in Segment 10 cannot be after the Submission Date in Segment 00. 11077 THAN THE
SUBMISSION DATE
(DE C3)
Details:
This data element is to be used to enter the month, day, year and hours when the Incident occurred or started, or the beginning of the time period in which it occurred. “Military”
twenty-four (24) hour time is to be used.
If the Incident occurred on or between midnight and 0059, enter “00” for the hour; if on or between 0100 and 0159, enter “01” for the hour if on or between 2300 and 2359, enter
“23” for the hour, etc.
If the Incident occurred at exactly midnight, it is considered to have occurred at the beginning of the next day. Therefore “00” should be entered for the hour, along with the next
day’s date.
If the Incident Date is unknown, enter the date of the report with the indicator “R” = Report after the MMDDYYYY of the Report Date.
If the Incident hour is unknown, leave the hour blank.
When LIBRS requires a Blank (G), it must be a Blank (G), NOT A ZERO.
Examples:
Example
Description
Number
1 If a robbery occurred at 9:30 p.m. on July 2, 2014, the entry should be ‘07022014G21’ (where ‘G’ is a blank).
2 If a kidnaping started at 11:30 p.m. on November 1, 2014, and ended at 6:00 p.m., on November 16, 2014, the entry should be ‘11012014G23’ (where ‘G’ is a blank).
3 If the date and hour of the incident are unknown, but the date of the report was March 15, 2014, the entry should be ‘03152014RGG’ (where ‘G’ is a blank).
4 If a burglary occurred sometime between 11:15 A.M. on June 24, 2014, and 4:30 P.M. on June 26, 2014, the entry should be 06242014G11 (where “G” is a blank).
If a rape occurred on November 15, 2013, but was not reported until January 15, 2014, this incident would reject if your agency’s “Base Date” is December 1, 2013.
This incident would not have been reported on your Return A (or whatever other forms would be applicable) for the month of November or for the month of
December of 2013.
5 If your agency submits this incident to LIBRS with an incident date of 11/15/2013, it would REJECT. It would reject because the Incident Date is prior to the date
your agency’s data is being kept by the LIBRS and NIBRS databases.
Since this incident CANNOT be accepted into LIBRS and has not been reported to UCR summary, an adjustment would have to be made on UCR Summary forms
that apply.
Cleared Exceptionally (4)
Description: Indicates whether the incident was cleared exceptionally. Note that Clearance of a single Offense will clear the entire Incident, as this data element is present in Segment
10 (Administrative Segment), of which there is only one for each Incident.
Data Characteristics: 1 Character Alpha. Cannot be blank, if the Incident is not Cleared Exceptionally then you should use ‘N’.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 This is a required Data Element, and it cannot be left blank. 10001 MUST BE PRESENT–MANDATORY FIELD
Supplied value was not a known value. Must be a code that is found on the List of Available INVALID DATA VALUE–NOT ON LIBRS
2 11004
Data Element Values VALIDATION TABLE
VALUE ENTERED CONFLICTS WITH
If an Exceptional Clearance Date (DE 5) is not entered, then Cleared Exceptionally (DE 4)
3 11053 PRESENCE OF AN ENTRY IN EXCEPTIONAL
should have a Value of ‘N’
CLEARANCE DATE
CLEARED EXCEPTIONALLY CANNOT
Administrative Segment (10) submitted with an Action Type of ‘W’ (Time Window Submission)
4 11054 CONTAIN ‘N’ WITH SEGMENT ACTION TYPE
cannot contain an ‘N’ (Not Applicable) in Cleared Exceptionally (DE 4).
‘W’
If an Incident has been Cleared Exceptionally, then by definition it cannot have been cleared CANNOT HAVE ARRESTS IF CLEARED
5 10071
by an arrest. The Incident should either not be Cleared Exeptionally, or not include an Arrest. EXCEPTIONALLY
Details:
The Cleared Exceptionally data element indicates if the incident has been cleared by an exceptional event such as the death of the offender, and if so, the reason for the
clearance. In multiple offense incidents, the exceptional clearance of one offense clears the entire incident. An incident CANNOT BE CLEARED EXCEPTIONALLY if it was previously,
or at the same time, cleared by an arrest, (that is, if an Arrestee Segment was or is being submitted).
In order to clear an offense by exceptional means, ALL of the following four conditions must be met:
The investigation must have clearly and definitely established the identity of at least one offender.
Sufficient probable cause must have been developed to support the arrest, charging, and prosecution of the offender.
The exact location of the offender must be known so that an arrest could be made.
There must be a reason outside the control of law enforcement that prevents arresting, charging, and prosecuting the offender.
DO NOT report exceptional clearance information for justifiable homicide, as no crimes have occurred, in reality.
The closing of a case or the clearing of it by an agency’s policy does not permit exceptionally clearing an offense unless all four conditions are met.
Allowed Entries
Enter one code per incident.
Cleared Exceptionally Indicators
A - Death of Offender
B - Prosecution Declined
C - Extradition Denied
D - Victim Refused to Cooperate
E - Juvenile / No Custody
O - Other (Administrative Closing)
N - Not Applicable
Examples:
Example
Description
Number
A kidnapper holding a hostage killed himself when the building in which he barricaded himself was surrounded by police. The kidnaping is cleared
1
exceptionally under, ‘Death of the Offender’.
Exceptional Cleared Date (5)
Description: The Exceptional Clearance Date is the date that the Agency was made aware that an Incident has been cleared by exceptional measures (EG: If cleared by Death of
Offender, it is not the Offenders date of Death, but rather when the Agency was made aware that the case was no longer active because of it). If The Incident is not Cleared by
Exceptional Means, then this Data Element should remain blank. Do not fill it with all Zero’s or any placeholder characters other than Blank Spaces.
Data Characteristics: 8 Character Date in the MMDDYYYY Format. If the Incident is not Cleared Exceptionally, then this Data Element should be Blank Spaces, otherwise this Data
Element should be present.
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for the Exceptional Clearance Date (DE 5) is not valid. Please ensure that the supplied date is in DATE ENTERED MUST
1 the MMDDYYY Format, and is not a date later than the reporting date. Additionally this value cannot be all zeros, it 11005 BE A VALID CALENDAR
must be a real date. DATE
EXCEPTIONAL
CLEARANCE DATE
2 The Exceptional Clearance Date (DE 5) cannot be earlier than the Incident Date (DE 3). 11055
PREDATES INCIDENT
DATE
EXCEPTIONAL
Administrative Segments (10) submitted ith an Action Type of ‘W’ (Time-Window Submission) or ‘M’ (Modify) CLEARANCE DATE
3 11074
cannot have an Exceptional Clearance Date (DE 5) earlier than the date the ORI was certified for LIBRS submission. PREDATES DATE ORI
WENT IBR
Examples:
Example
Description
Number
The incident was cleared on the books of the reporting agency on May 27. It was entered into the local computer on June 6, 2019, and was submitted to LIBRS
1
sometime in July of 2019. The date ‘05272019’ should be entered into this data element.
Offense Sequence Number (L6)
Description: The Offense Sequence Number is a Uniquely Identifying Value between 001 and 999 that is used throughout the LIBRS Data Segments to identify which particular Offense
is being referenced for validation purposes. Each Offense Segment (Segment 20) in an Incident should contain a unique Sequence Number.
Data Characteristics: 3 Character Numeric. Cannot be blank and should always be a three-digit number, front-padded with zeros as needed (EG Offense Sequence Number 1 of the
Incident would be 001)
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 Offense Sequence Number (DE L6) is a required Data Element and cannot be left blank. 10001
MANDATORY FIELD
ERROR - DUPLICATE
2 Offense Sequence Number (DE L6) cannot be repeated for multiple Segment 20’s (Offense Segment) in an Incident. 12006
VALUE
Offense Sequence Number (DE L6) should be a numeric entry, front-padded with zeros to make a three-digit number CONTAINS NON
3 15002
between 001 and 999. EG: 001, 002, 010 for Sequence Numbers 1, 2, and 10. NUMERIC ENTRY
Offense Sequence Number Reference (L6R)
Description: Offense Sequence Number Reference is used in Segment 33 to relate Properties and Offenses together. It has to match one of the Offense Sequence Numbers (DE L6) that
are present in the Segment 20(s) of the Incident, and since it’s used to relate Properties to Offenses, the same L6R can be used in Multiple Segment 33’s to relate multiple Properties to
the Offense.
Data Characteristics: 3 Character Numeric, front-padded with Zeros to make a three-digit number (EG Sequence Number 1 would be 001). Must be included in each Segment 33 of the
Incident and cannot be left blank or all zeros (000).
Requirements:
Error
Requirement Requirement Description Error Message
Number
Offense Sequence Number Reference (DE L6R) is required for each Property/Offense OFFENSE SEQUENCE NUMBER MUST BE
1 90021
Relationship Segment (Segment 33) present in the Incident; It cannot be blank. PRESENT–CANNOT BE BLANK
Offense Sequence Number Reference (DE L6R) should be a numeric entry, front-padded with OFFENSE SEQUENCE NUMBER MUST BE
2 90022
zeros to make a three-digit number. EG: 001, 002, 010 for Sequence Numbers 1, 2, and 10. NUMBER ENTRY WITH ZERO LEFT - FILL
OFFENSE SEQUENCE NUMBER DOES NOT
Offense Sequence Number Reference (DE L6R) must match the Offense Sequence Number
3 90025 MATCH ANY PROVIDED OFFENSES’
(DE L6) of one of the Offense Segments (Segment 20) submitted in the incident.
SEQUENCE NUMBERS
Details:
There is no UNIQUE constraint for the Offense Sequence Number Reference (L6R). This allows for an Offense to relate to many properties if multiple Property/Offense segments
are submitted within a single incident.
Louisiana Revised Statute (6)
Description: The Louisiana Revised Statute (LRS) Code is the State Statute that and Offender is being charged and/or Arrested for. The Master LRS List contains the list of all available
LRS Codes that LIBRS is able to have reported to it. Each of these LRS Codes have NIBRS Code(s) associated with them. This allows Officers to report the crime how they intended to the
FBI. EG: LRS 14:59/A9 is used to denote that someone shot a firearm at a train. Depending on the circumstances, the Officer may want to report this crime as a Weapons Violation (520)
or as a Descrution of Property/Vandalism (290).
LRS Codes also have Subparts and Qualifiers that can be associated with them. These, similarly to the NIBRS Code, allow the Officer to more descriptively report what happened for
Statutes that have a broad stroke of ways that it could be violated. More information on Subparts and Qualifiers is below.
Data Characteristics: 12 Character Alpha. Cannot be left blank and can only contain one (1) Hyphen (-).
Format: TT:SSSS.S/P-I
Louisiana Revised Statute Format
TT Title
SSSS.S Section
Subpart, or
Subpart with Qualifier, or
PPP/I Qualifier, or
Juvenile Qualifier, and An Inchoate Modifier, if applicable, would be indicated
by a dash with a data value behind the LRS Code that defines the offense.**
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 LRS Code (DE 6) is missing. This is a required Data Element. 10001 MUST BE PRESENT–MANDATORY FIELD
Must be a valid code on Master LIBRS/LRS Code Table. Check the Master LRS List for available INVALID DATA VALUE–NOT ON LIBRS
2 11004
codes to use. VALIDATION TABLE
Due to the addition of Inchoates (DE 70) Each LRS Code is only permitted to have one ‘-‘ in it, ONLY ONE DASH ‘-‘ ALLOWED PER LRS
3 22086
which is used to designate the Inchoate Value. OFFENSE
4
Qualifiers and Subparts
Qualifiers and Subparts are additional information that is added to the tail-end of an LRS Code to give more definition about it whenever a statute contains multiple cases that could be
reported as different NIBRS Codes. For instance, LRS 14:67 is generally used for Theft, however the item that is being stolen can cause the NIBRS Code that should be used to change
(EG: A 14:67 with a 240 NIBRS Code is for if a vehicle is stolen, while a 14:67 with a 23H)
Examples:
Example
Description
Number
When 14:42 is submitted as a Louisiana Revised Statute LRS (6), LIBRS will need Qualifiers to determine if the offense should be classified as a forcible rape or as a
forcible sodomy. If the offense is submitted as a 14:42/V, this would translate to a forcible rape offense, whereas if this offense is submitted as a 14:42/A this
would translate to a forcible sodomy offense.
1
Without any Qualifiers, LIBRS has no way to determine which offense this LRS should be reported as, and the entire incident would be rejected. The agency will
receive the following error message: ‘This LRS Code must be submitted with a Qualifier to define offense applicable.’
If an incident involved a robbery (14:64) and a forcible rape (14:42.1/V), two LRS offenses should be submitted. The 14:64 does not require any Qualifier, but the
2
14:42.1 does require a Qualifier.
If two females were raped in an incident, two LRS offenses should be submitted for rape: One LRS should be reported for each victim – in this case, both LRS codes
3
should be submitted as 14:42.1/V for Victim 001 and 14:42.1/V for Victim 002)
4 14:90/G – “G” refers to a Qualifier (see Qualifier List) and would be reported to the FBI as the offense of Betting/Wagering (NIBRS 39A).
If the LRS offense is Aggravated Assault (14:87.2/F) and the Offender or the Arrestee was responsible for Accessory After the Fact then the agency would submit the
5 following: 14:87.2/F-A. This will be reported to the FBI as an Aggravated Assault, Accessory After the Fact as the offense and for LIBRS reporting this will be
considered as All Other Offenses (NIBRS 90Z).
Refer to the Master LIBRS/LRS Code Table to determine:
LRS Codes that are accepted
What offense the LRS code was assigned: NIBRS Code determines offense to be reported.
Index Class assigned to each LRS
IBR and NIBRS rankings.
Warning Messages will be returned for the following LRS codes:
LRS Warning
Description Warning Message
Code Number
With no Qualifier will be reported to the FBI as Driving Under WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:32.1 22025
the Influence (NIBRS 90D) DRIVING UNDER THE INFLUENCE(90 D)
With no Qualifier will be reported to the FBI as Kidnaping WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:44.1 22030
(NIBRS 100) KIDNAPPING(100)
With no Qualifier will be reported to the FBI as a Robbery WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS A
14:60 22130
(NIBRS 120) ROBBERY (120)
With no Qualifier will be reported to the FBI as a Purse WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:65.1 22035
Snatching (NIBRS 23B) PURSE - SNATCHING(23 B)
With no Qualifier will be reported to the FBI as a Credit WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:70.4 22135
Card/Automatic Teller Machine Fraud (NIBRS 26B) CREDIT CARD / AUTOMATIC TELLER MACHINE FRAUD (26B)
With no Qualifier will be reported to the FBI as Bribery (NIBRS WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:70.5 22140
510) BRIBERY (510)
With no Qualifier will be reported to the FBI as a Family WARNING THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS A
14:93 22040
Offense Nonviolent (NIBRS 90F) FAMILY OFFENSE NONVIOLENT(90 F)
With no Qualifier will be reported to the FBI as All Other WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS ALL
14:107.1 22045
Offenses (NIBRS 90Z) OTHER OFFENSE(90 Z)
With no Qualifier will be reported to the FBI as a Simple WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER IS REPORTED AS
14:129.1 22050
Assault (NIBRS 13B) SIMPLE ASSAULT(13 B)
Hard-Coded Edits for LRS Codes Without a Property Description-Based Qualifier:
LRS Warning
Description Warning Message
Code Number
WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER WILL BE REPORTED AS
When submitted with no Qualifier will be reported to the FBI as
14:67 22055 ALL OTHER LARCENY - THEFT OFFENSE (23H). IF THIS IS NOT THE CORRECT
All Other Larceny-Theft (NIBRS 23H)
PROPERTY DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE.
When LRS 14:67 is submitted with no Qualifier AND Property WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE #15 = ‘38’ WILL
14:67 Description (DE 15) is “38”, the offense will be reported to the 22060 BE REPORTED AS THEFT OF MOTO VEHICLE PARTS (23G). IF THIS IS NOT THE
FBI as Theft of Motor Vehicle Parts (NIBRS 23G) CORRECT PROPERTY DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE
WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE #15 = ‘03’, ‘05’,
When submitted with no Qualifier AND Property Description
‘24’, ‘28’, OR ‘37’ WILL BE REPORTED AS MOTOR VEHICLE THEFT (240).IF THIS IS
14:67 (DE 15) is other than: ‘03’, ‘04’, ‘05’, ‘24’, ‘28’, ‘37’ or ‘38’, the 22065
NOT THE CORRECT PROPERTY DESCRIPTION CODE, RESUBMIT WITH CORRECT
Offense will be reported as Motor Vehicle Theft (NIBRS 240)
CODE
When LRS 14:67 is submitted with no Qualifier AND Property WARNING - THIS LRS SUBMITTED WITHOUT A QUALIFIER AND DE #15 = ‘04’ WILL
14:67 Description (DE 15) is “04”, the offense will be reported as Theft 22070 BE REPORTED AS THEFT OF A BICYCLE. IF THIS IS NOT THE CORRRECT PROPERTY
of a Bicycle DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE.
WARNING - THIS LRS SUBMITTED WILL BE REPORTED AS ALL OTHER LARCENY -
LRS 14:68 will be reported to the FBI as All Other Larceny-Theft
14:68 22071 THEFT OFFENSE(23H). IF THIS IS NOT THE CORRECT PROPERTY DESCRIPTION
(NIBRS 23H)
CODE, RESUBMIT WITH CORRECT CODE.
WARNING - THIS LRS SUBMITTED AND DE #15 = ‘03’, ‘05’, ‘24’, ‘28’, OR ‘37’ WILL
When LRS 14:68 is submitted AND Property Description (DE 15)
14:68 22072 BE REPORTED AS MOTOR VEHICLE THEFT (240). IF THIS IS NOT THE CORRECT
is “03”, “05”, “24”, “28” or “37”, Motor Vehicle Theft (NIBRS 240)
PROPERTY DESCRIPTION CODE, RESUBMIT WITH CORRECT CODE.
Allowed Entries for Juvenile Qualifiers:
LIBRS accepts the following juvenile specific reportable offenses that are NOT part of the list of LRS codes. Agency should submit the following codes in this data element for juvenile
specific offenses:
LRS Code Description NIBRS Crime Against
JU:CUR Juvenile Curfew Violations will be reported to the FBI as Curfew/Loitering/Vagrancy violations 90B Society
JU:RUN Juvenile Runaways will be reported to the FBI under Runaways offense 90I Society - Not a crime
JU:TRU Juvenile Truancy will be reported to the FBI as All Other Offenses 90Z Society - Not a Crime
JU:UNG Juvenile Ungovernables will be reported to the FBI under Disorderly Conduct Offense 90C Society
LRS Qualifiers List
Qualifiers must be associated with the LRS codes as shown in the LIBRS/LRS Master Code Table. Only the combinations shown in the table below qualify as a valid entry in Data Element
# 6 (LRS of Offense) and Data Element # 45 (LRS of Arrest Offense). An agency CANNOT append these Qualifiers to any LRS Code to classify offense to be reported, unless it is a valid
LRS Code combination as classified on the LIBRS/LRS Master Code Table.
NIBRS Crime
Qualifier Description NIBRS Description
Code Against
NIBRS Crime
Qualifier Description NIBRS Description
Code Against
Murder and Nonnegligent
AA Vehicular Homicide with Intent to Kill 09A Person
Manslaughter
Anal penetration - Anal sexual intercourse with another person, forcibly and/or against that
person’s will; or not forcibly or against the persons will where the victim is incapable of giving
A Forcible Sodomy 11B Person
consent because of his/her youth or because of his/her temporary or permanent mental or physical
incapacity
Theft from Building - A theft from within a building which is either open to the general public or
B Theft from Building 23D Property
where the offender has legal access.
Theft from Coin Operated Machine - Theft from a machine or device which is operated or activated Theft from Coin Operated
C 23E Property
by the use of coins. Machine
Drug/Narcotic Violations - Offender unlawfully distributes or dispenses a controlled dangerous
substance to a recipient or to another who subsequently distributes or dispenses such controlled
D Drug/Narcotic Violations 35A Society
dangerous substance, which is the direct cause of the death of the person who ingested or
consumed the controlled dangerous substance.
Embezzlement - Unlawful misappropriation by an offender to his/her own use or purpose of
E Embezzlement 270 Property
money, property, or some other thing of value entrusted to his/her care, custody, or control.
Actual Force Used Against a Victim or Threat of Force Displaying a Weapon - Might be used to
Aggravated Assault, Person, or 13A or
F determine if a purse snatching is to be reported as Strong Arm Robbery 14:65.1/F, or as Larceny Person
Robbery 120
Theft 14:65.1
Fraud - False Pretense/Swindle/Confidence Game Intentional misrepresentation of existing fact or False
FR condition, or the use of some other deceptive scheme or device, to obtain money, goods, or other Pretense/Swindle/Confidence 26A Property
things of value. Game
Betting and Wagering - To unlawfully stake money or something else of value on the happening of
G Betting/Wagering 39A Society
an uncertain event or on the ascertainment of a fact in dispute.
Inhabited Dwelling - Structure occupied as a place of settled residence or habitat lived in regularly
H Arson 200 Property
or routinely. Arson reporting
Immovable Structures - Fixed permanent or immovable things; include house trailer or houseboat if
used as permanent dwelling.
Property
Burglary or Trespass of Real 220 or
I or
Burglary: Unlawful entry into a building or other structure with intent to commit a felony or a theft Property 90J
Society
Trespass of Real Property: To unlawfully enter land, a dwelling, or other real property
J Self Inflicted Serious Bodily Injuries All Other Offenses 90Z Person
Curfew/Loitering/Vagrancy
JU:CUR Juvenile Curfew Violations - will be reported to the FBI as curfew/loitering/ vagrancy violations 90B Society
Violations
Society -
JU:RUN Juvenile Runaways - will be reported to the FBI under Runaways offense Runaway 90I Not a
Crime
Society -
JU:TRU Juvenile Truancy - Absent from school without permission. All Other Offenses 90Z Not a
Crime
JU:UNG Juvenile Ungovernables - will be reported to the FBI as Disorderly Conduct Disorderly Conduct 90C Society
Pocket Picking - Theft of articles from another person’s physical possession by stealth where the
K Pocket Picking 23A Property
victim usually does not become immediately aware of the theft
Murder and Non Negligent Manslaughter - Willful nonnegligent killing of one human being by Murder and Non-Negligent
L 09A Person
another human being live born not an embryo or fetus in utero Manslaughter
Movable Structures - Tents, boats, airplanes, lawnmowers, hand tools, farm and construction Larceny Theft - All Other
M 23H Property
equipment, etc… not permanent dwellings Larceny
Rubbing/Touching - No actual penetration ‘indecent liberties’, ‘child molesting’, no elements of
N Forcible Fondling 11D Person
11A, 11B or 11C were applicable
Oral Intercourse - Oral sexual intercourse with another person, forcibly and/or against that person’s
will. Or, not forcibly or against the persons will where the victim is incapable of giving consent
0 Forcible Sodomy 11B Person
because of his/her youth or because of his/her temporary or permanent mental or physical
incapacity
Sexual Assault With an Object - To use an object or instrument to unlawfully penetrate, however
slightly, the genital or anal opening of the body of another person, forcibly and/or against that
P person’s will. Or, not forcibly or against the persons will where the victim is incapable of giving Sexual Assault With an Object 11C Person
consent because of his/her youth or because of his/her temporary or permanent mental or physical
incapacity
Victim Had Offender Inflict Serious Bodily Injuries to Him/Her - Victim made the offender inflict
Q Aggravated Assault 13A Person
injuries to his/her person no intent on part of the offender
Operating/Assisting Gambling - To unlawfully operate, promote, or assist in the operation of a Operating/Promoting/
R 39B Property
game of chance Assisting Gambling
NIBRS Crime
Qualifier Description NIBRS Description
Code Against
Shoplifting - The theft, by someone other than an employee of the victim, of goods or merchandise
S Shoplifting 23C Property
exposed for sale
T Threat of Force Used Against the Victim - No weapons and no physical attack used in this threat Intimidation 13C Person
Uninhabited Dwelling - Structures uninhabited or abandoned or not normally in use. Arson
U Arson 200 Property
reporting
Vaginal Penetration - With force or without force where the victim is incapable of giving consent
V Forcible Rape 11A Person
because of youth or because of temporary or permanent mental incapacity
W Fetal Death - Human embryo or fetus in utero All Other Offenses 90Z Society
Falsified Records by Forgery or Counterfeiting - Altering, copying, or imitation of something,
without authority or right, with the intent to deceive or defraud by passing the copy or thing
X Counterfeiting/Forgery 250 Property
altered or imitated as that which is original or genuine. Or, the selling, buying, or possession of an
altered, copied, or imitated thing with the intent to deceive or defraud
Destruction/Damage/Vandalism
Y Destroyed Records or Property 290 Property
of Property
Z Theft from a Motor Vehicle - Theft of articles from motor vehicle whether locked or unlocked Theft from a Motor Vehicle 23F Property
Agency Supplied NIBRS Code (N6)
Description: The NIBRS Code that the Agency Supplies is what drives LIBRS Validation. The LRS Code is important to us for analytics purposes, however we use the NIBRS Code to
effectively categroize LRS Codes into kinds of offenses, and then perform validation based on which category the LRS Code falls into.
The NIBRS Code also allows Officers to report Offenses in a more specific manner without having to go through the trouble of Subparts and Qualifiers.
Data Characteristics: 3 Character AlphaNumeric. Check here for a list of the current NIBRS Codes.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA
VALUE–NOT ON
1 Supplied value was not recognized. Please ensure that the supplied NIBRS Code is valid. 11004 LIBRS
VALIDATION
TABLE
All Offenses must have a valid NIBRS Code submitted with them. In the past, LIBRS would make an assumption based on
MUST PROVIDE
2 a ‘Default’ NIBRS Code associated with each LRS Code. This is not longer in practice, and therefore each Offense must 90034
A NIBRS CODE
now contain an Agency Submitted NIBRS Code.
CHOSEN NIBRS
The NIBRS Code that you’ve selected for this LRS Code was marked as Expired before the Incident Date of this Incident. MAPPING IS
23 86754
Please select a Different NIBRS Code. EXPIRED AS OF
INCIDENT DATE
Offense Attempted/Completed (7)
Description: Attempted/Completed is how to designate whether or not an Offense occurred to completion, or was merely attempted by the Offender. For instance, an Offender tries to
steal a car, but is caught in the act by the police. Since the Offender didn’t succeed in stealing the car, this offense would be Attempted.
The only thing to note about this is that Attempted Murder (Attempted 09A) should be reported as a Completed Aggravated Assault (Completed 13A). NIBRS does not allow for 09A
Offenses to be Attempted, so instead it should be reported as a Completed Aggravated Assault – Otherwise, the Offense is reported in the standard fashion.
Data Characteristics: 1 Character Alpha. Cannot be left blank, and must have a value of either:
A - Attempted
C - Completed
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–MANDATORY
1 Attempted/Completed (DE 7) is missing. This is a required Data Element. 10001
FIELD
Supplied value was not recognized. The only valid codes that can be used are ‘A’ (Attempted) or ‘C’
2 12051 INVALID CODE
(Completed).
Details:
This element is used to indicate whether each offense in the incident was completed or merely attempted.
Allowed Entries
Enter one code per incident.
Offense Attempted/Completed
A - Attempted
C - Completed
Examples:
Example
Description
Number
During the same incident, Victim Number One (001) was raped and the Offender attempted to rape Victim Number Two (002), but had to leave the scene before
the act was consummated due to the arrival of the police.
1
Offense 001 should be entered as Aggravated Rape (LRS 14:42/V) and have Completed (‘C’) entered in Offense Attempted/Completed (DE 7). Offense 002 should
also be entered as Aggravated Rape (LRS 14:42/V), but will have Attempted (‘A’) entered in Offense Attempted/Completed (DE 7).
Offender Suspected of Using/Gaming Motivation (8)
Description: Offender Suspected of Using/Gaming Motivation gives more context to the Offenses that are being reported. It tells us if an Offender is suspected of being on
Drugs/Narcotics or has consumed Alcohol either during or shortly before the Incident Occurred. It also gives context of whether Computer Equipment was used to perpetrate the Crime,
and if a Gaming/Gambling activity was a motivating factor in committing the crime.
Data Characteristics: Up to 4x, 1 Character Alpha. If you use ‘N’, then you cannot use any other values, and values cannot repeat (EG: AAGG and CGN are both invalid combinations). At
least one value is required to be present, but the other three slots are optional and can be left blank if nothing else applies. If another value does apply, then the mutual exclusivity and
duplicate rules need to be followed.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 Offender Suspected of Using/Gaming Motivation (DE 8) cannot be blank. 10001 MUST BE PRESENT–MANDATORY FIELD
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
3 When more than one value is present, the same value is not allowed to be repeated. 12006 ERROR - DUPLICATE VALUE
Value ‘N - Not Applicable’ is mutually exclusive with any other value. No other values should ERROR - MUTUALLY EXCLUSIVE VALUES
4 12007
be included if ‘N’ is used. USED
Details:
Offender Suspected of Using/Gaming Motivation (8) indicates that an Offender is suspected of consuming alcohol, or using drugs/narcotics during, or shortly before, the
incident; or, of using a computer, computer terminal, or other computer equipment to perpetrate the crime. Can also indicate if an Offender’s gaming activity was a motive in the
commission of a crime.
Allowed Entries
Offender Suspected of Using/Gaming Motivation
A - Alcohol
C - Computer Equipment
D - Drugs/Narcotics
G - Gaming Activity Motive for Crime
N - Not Applicable (LIBRS Only)
Examples:
Example
Description
Number
Witness to an assault reported that the Victim and Offender were in a bar drinking beer when an argument broke out and the Offender attacked the Victim with a
1
knife. Alcohol (‘A’) should be entered in Offender Suspected of Using/Gaming Motivation (DE 8).
A computer ‘hacker’ used his personal computer and the Internet to gain access to a company’s computer system and steal proprietary data. Computer Equipment
2
(‘C’) should be entered in Offender Suspected of Using/Gaming Motivation (DE 8).
Offender robbed a bank and a police officer arrested him while trying to leave the bank. Under questioning, the Offender told the officer he needed money
3 because he lost $10,000 that morning at the river boat casino. The officer also smelled alcohol on his breath. Both Alcohol (‘A’) and Gaming Activity Motive for
Crime (‘G’) should be entered into Offender Suspected of Using/Gaming Motivation (DE 8).
Bias Motivation/Bias Crime Type (8A)
Description: Bias Motivation/Crime Type gives insight into the motivation behind an Offender committing a crime. For instance, if the Offender committed the crime because of the
Race or Religion of the Victim, that should be noted here.
Data Characteristics: 2 Character Alpha. Must be present and can’t be blank. If there is no reason to suspect the Offender had a Bias Type against the Victim use ‘88’ for None, but if
not enough information is known about the Offender to determine whether or not a Bias Type was a factor in them committing the crime, use ‘99’ for Unknown.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 Bias/Motivation Type (DE 8A) cannot be blank. 10001 MUST BE PRESENT–MANDATORY FIELD
Must be a valid code that is found on the List of Available Data Element INVALID DATA VALUE–NOT ON LIBRS VALIDATION
2 11004
Values. TABLE
Details:
Bias Motivation/Bias Crime Type (8) indicates an Offender’s motivation to commit an offense because of their bias against a Victim’s race, religion, ethnicity, national origin,
sexual orientation, disability group, or other bias.
Because of the difficulty in ascertaining the Offender’s subjective motivation, bias is to be reported only when an investigation reveals sufficient objective facts to lead a
reasonable and prudent person to conclude that the Offender’s actions were motivated, in whole or in part, by bias.
In LIBRS, incidents not having facts that indicate biased motivation on the part of the Offender are to be coded as None (88), while incidents involving ambiguous facts (that is,
where some facts are present, but not conclusive) are to be coded Unknown (99).
If any Bias Motivation/Bias Crime Type codes are used, other than None (88) or Unknown (99), then the incident will be considered a hate crime, and the Louisiana Revised
Statute (DE 6) probably should be appended with the Hate Crime Penalty Enhancer (-H) to represent enhanced penalties related to hate crimes in LRS 14:107.2.
List of Allowed Entries for DE 8A is on the following page:
Allowed Entries:
Enter only one code for each Offender Segment (40):
Bias Motivation/Bias Crime Type
Race/Ethnicity/Ancestry
11 - Anti-White
12 - Anti-Black or African American
13 - Anti-American Indian / Alaskan Native
14 - Anti-Asian
15 - Anti-Multiple Races, Group
16 - Anti-Native Hawaiian or Other Pacific Islander
31 - Anti-Arab
32 - Anti-Hispanic or Latino
33 - Anti-Other Race/Ethnicity/Ancestry
Religion
21 - Anti-Jewish
22 - Anti-Catholic
23 - Anti-Protestant
24 - Anti-Islamic (Muslim)
25 - Anti-Other Religion
26 - Anti-Multiple Religions, Group
27 - Anti-Atheism/Agnosticism
28 - Anti-Mormon
29 - Anti-Jehovah’s Witness
81 - Anti-Eastern Orthodox (Russian, Greek, Other)
82 - Anti-Other Christian
83 - Anti-Buddhist
84 - Anti-Hindu
85 - Anti-Sikh
Sexual Orientation
41 - Anti-Gay (Male)
42 - Anti-Lesbian (Female)
43 - Anti-Lesbian, Gay, Bisexual or Transgender (Mixed Group)
44 - Anti-Heterosexual
45 - Anti-Bisexual
Disability
51 - Anti-Physical Disability
52 - Anti-Mental Disability
Gender
61 - Anti-Male
62 - Anti-Female
Gender Identity
71 - Anti-Transgender
72 - Anti-Gender Non-Conforming
None/Unkown
88 - None (No Bias)
99 - Unknown (Offender’s Motivation Not Known)
Location Type (9)
Description: Location Type is used as a broad-strokes description of the Location in which an Incident Occurred. It’s not meant to give particular location information about the location
that an Incident occurred (EG: the Exact Address), but rather a short code that can be used for analytics purposes.
Data Characteristics: 2 Character Alpha. Must be included and can’t be blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 Location Type (DE 9) is missing. This is a required Data Element. 10001 MUST BE PRESENT–MANDATORY FIELD
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
Details:
This data element is to be used to report the type of location/ premises where each offense took place. Only one (1) location can be entered for each offense.
List of Allowed Entries for DE 9 is on the following page:
Allowed Entries:
Enter only one (1) code per Offense Segment:
Location Type
01 - Air, Bus, Train or Terminal
02 - Bank, Savings and Loan (incl. other Financial Institutions)
03 - Bar or Night Club
04 - Church, Synagogue or Temple (includes other Religious Buildings..)
05 - Commercial or Office Building
06 - Construction Site
07 - Convenience Store
08 - Department or Discount Store
09 - Drug Store, Doctor's Office or Hospital (includes Medical Supply Building)
10 - Field or Woods
11 - Government or Public Building
12 - Grocery or Supermarket
13 - Highway, Road or Alley (includes Street)
14 - Hotel, Motel, Etc. (includes Temporary Lodgings)
15 - Jail or Prison
16 - Lake or Waterway
17 - Liquor Store
18 - Parking lot/Garage
19 - Rental storage Facility
20 - Residence/Home
21 - Restaurant
22 - School
23 - Service or Gas Station
24 - Specialty Store (incl. Fur Store, Jewelry Store, TV Store, Dress Shop, etc.)
25 - Other or Unknown (use only if no other code applies)
37 - Abandoned or Condemned Structure
38 - Amusement Park
39 - Arena, Stadium, Fairgrounds or Coliseum
40 - ATM Separate from Bank
41 - Auto Dealership (New or Used)
42 - Camp or Campground
44 - Daycare Facility
45 - Dock, Wharf, Freight or Modal Terminal
46 - Farm Facility
47 - Gambling Facility, Casino or Race Track
48 - Industrial Site
49 - Military Installation
50 - Park or Playground
51 - Rest Area
52 - School: College or University
53 - School: Elementary or Secondary
54 - Shelter: Mission or Homeless
55 - Shopping Mall
56 - Tribal Lands
57 - Community Center
58 - Cyberspace
Examples:
Example
Description
Number
An assault started in a bar (‘03’), continued into an adjoining parking lot (‘18’), and ended in the street (‘13’). As the bar was the location where the offense was
1
initiated and best describes the circumstances of the crime, Bar/Night Club (‘03’) should be entered.
Two Offenders robbed a bar. One of the Offenders raped a female customer in the bar while the other Offender stood at the door with a gun. In this case, there is
2 one incident, with two offenses: robbery and forcible rape. The location of the robbery would be Bar/Night Club (‘03’), and the location of the forcible rape would
also be Bar/Night Club (‘03’).
Number of Premises Entered (10)
Description: Number of Premises Entered is only to be used if the Incident contains a NIBRS 220 (Burglary) Offense, and the Location Type (DE 9) is 14 or 19. It is the number of
individual/separate dwellings or units that were stolen from in the 220 Offense. For instance, a single Hotel may have been burgled, but a dozen units in that hotel were stolen from.
Rather than 12 Offenses with the same location, you should use one Offense with a 12 in this Data Element.
This Data Element should be left blank if the 220 Offense did not happen in a Hotel/Motel or Storage Facility, because these are the only two Location Types that can contain multiple,
separate dwellings/units at the same address (Apartments each have an Apartment Number that you can send mail to, and therefore can be considered to be different places for the
Time and Place consideration).
Data Characteristics: 2 Character Numeric. If the described conditions don’t apply, then this value should be left as Blank Spaces (G). Otherwise it should include a two digit number,
using 01, 02, 03, etc… for single-digit numbers.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 Must be numeric entry of 01-99, if entered. 12002 CONTAINS NON NUMERIC ENTRY
In order for Number of Premises Entered (DE 10) to have a value, Location Type (DE 9) must either OFFENSE CODE MUST BE BURGLARY
2 be Hotel/Motel/Etc. (‘14’) or Rental Storage Facility (‘19’), and must be related to an Offense Code 12052 WITH LOCATION TYPE OF 14, 19 FOR
of 220. DATA TO BE ENTERED
Details:
This data element is used only if the offense is burglary and the “Hotel Rule” is applicable. In such cases, the number of structures (premises) entered is to be reported. If the LRS
offense (6) is not reportable as a Burglary (NIBRS 220), then this data element MUST be left blank.
In the Summary UCR Reporting System, the “Hotel Rule” is only applied to temporary lodging. It states: If a number of dwelling units under a single manager are burglarized,
then the offenses are most likely to be reported to the police by the manager rather than the individual tenants. The burglary should be reported as a single offense. The total
number of individual rooms, units, storage compartments, etc. entered is to be reported into this data element.
In LIBRS the “Hotel Rule” has been expanded to include rental storage facilities, i.e., “mini-storage” and “self storage” buildings.
Examples:
Example
Description
Number
A ‘self-storage’ building was burglarized and 11 rented storage compartments were forcibly entered. The number ‘11’ (for eleven compartments) should be
1
entered into Number of Premises Entered (DE 10).
Method of Entry (11)
Description: Method of Entry should only be used when there is an Offense Type of NIBRS 220. Unlike Number of Premises Entered (DE 10), there is no restriction on if it can only be
used with certain Location Types. Any location Type that is valid for use in a Burglary should include this Data Element. The available values are ‘F’ for Forced Entry (breaking of a
window or door to gain access) and ‘N’ for Non-Forced Entry (picking a lock or going through an open window to gain access).
Data Characteristics: 1 Character Alpha. Should be left blank unless the NIBRS Code is a 220 (Burglary) Offense.
Requirements:
Error
Requirment Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the List of Available INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
Data Element Values. TABLE
If Offense is not a NIBRS 220 Offense, then Method of Entry (DE 11) should not MUST BE BLANK WHEN OFFENSE IS OTHER THAN
2 12054
have a value. (BURGLARY)
Details:
This data element is to report whether force or no force was used by the burglar(s) to enter the structure.
A forced entry is where force of any degree, or a mechanical contrivance of any kind (including a passkey or skeleton key), was used to unlawfully enter a building or other
structure.
An unforced entry is one where the unlawful entry was achieved without force through an unlocked door or window.
If both forced and unforced entries were involved in the crime, the entry should be reported as having been accomplished through “Force”.
Allowed Entries:
Enter only one (1) code per Offense Segment:
Location Type
F - Force
N - No Force
Examples:
Example
Description
Number
Investigation of a burglary complaint disclosed that the Offender(s) entered the building through an unlocked street door, then forced a locked door to an office
1
and stole a typewriter. Since one door was forced, the Method of Entry should be entered as Force (“F”).
Type of Criminal Activity/Gang Information (12)
Type of Criminal Activity and Gang Information are combined into a single Data Element. This portion is split into two sections to outline the requirements for each. Which aspect of the
Data Element should be used is dependent on the NIBRS Code of the Offense.
Type of Criminal Activity Nos. 1, 2 and 3 (12)
Description: Type of Criminal Activity is used to add context to Offenses for when they’re passed on to the FBI. For instance, a 35A Offense could just as easily be a single person with
some Marijuana on them, or a major drug bust with millions of Dollars of narcotics involved. Adding a value here gives the FBI that context when it comes to Offenses that can be open-
ended like that.
Data Characteristics: Up to 3x, 1 Character Alpha. If none apply, then leave this Data Element blank. If more than one apply, then make sure that there aren’t any duplicate values being
reported (EG: BBB).
Requirements (Criminal Activity):
The following requirements are for Type of Criminal Activity Only:
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value
1 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
on the List of Available Data Element Values.
When more than one value is present, the same value is
2 12006 ERROR - DUPLICATE VALUE
not allowed to be repeated.
This Data Element must and can only contain a value if it
is associated with an Offense with one of the following
NIBRS Codes:
250, 280
3 35A, 35B 12019 DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
370, 520, 720 (720 is limited to A, I, F, or S)
39C
90A, 90Z (If 90Z is a Crime Against Property)
Type of Criminal Activity/Gang Information (DE 12) WHEN THE OFFENSE WITH NIBRS = 720;CRIMINAL ACTIVITY(DE 12) MUST BE A
4 MUST have a valid code and cannot be None when 90031 VALID CODE AND IT CANNOT BE NONE;VALID CODES FOR THE ENTRY AT
NIBRS Offense Code is 720. CRIMINAL ACTIVITY(DE 12) = ‘A’ ‘F’ ‘I’ ‘S’
List of Allowed Entries for DE 12 is on the following page:
Allowed Entries (Criminal Activity)
Up to three (3) of the following Type of Criminal Activity Codes can be entered for applicable Offenses.
Type of Criminal Activity Codes
B - Buying / Receiving
C - Cultivation / Manufacturing / Publishing
D - Distribution / Selling
E - Exploiting Children
I - Possession with Intent to Sell. Sent to NIBRS as code 'P'
O - Operating/Promotion/Assisting
P - Possessing/Concealing
T - Transporting/Transmitting/Importing
U - Using/Consuming
X - Other. Sent to NIBRS as code 'P'
A - Simple/Gross Neglect
F - Organised Abuse
I - Intentional Abuse and Torture
S - Animal Sexual Abuse
Examples (Criminal Activity):
Example
Description
Number
The Offenders published and sold pornographic photographs of children. Therefore, up to three types of Criminal Activity can be entered:
1
Cultivating/Manufacture/Publishing (“C”), Distributing/Selling (“D”), and Exploiting Children (“E”).
Gang Information Nos. 1, 2 and 3 (12)
Description: Gang Information is used to add context to Offenses for when they’re passed on to the FBI, and is used with violent and more serious crimes (Rape, Murder, Robbery,
Kidnapping, etc…).
Data Characteristics: Up to 3x, 1 Character Alpha. If none apply, then use ‘N’ for None/Unknown. If more than one apply, then make sure that there aren’t any duplicate values being
reported (EG: JGJ). If ‘N’ for None or Unkonwn is used, then no other codes can be entered with it and the remaining two spaces for data must remain as Blank Spaces.
Requirements (Gang Activity):
The following requirements are for Gang Information Only:
Error
Requirement Requirement Description Error Message
Number
This Data Element must and can only contain a value if it is associated with an Offense with one
of the following NIBRS Codes:
09A, 09B
DATA CAN ONLY BE ENTERED FOR
1 100, 120 12019
SPECIFIC OFFENSES
11A, 11B, 11C, 11D
13A, 13B, 13C
Value ‘N - None or Unknown’ is mutually exclusive with any other value. No other values should ERROR - MUTUALLY EXCLUSIVE VALUES
2 12007
be included if ‘N’ is used. USED
Details:
(Gang Information): This data element is used to provide Gang Information on Offender(s).
Definition of a Gang: A gang must meet the following criteria in order to be considered a gang:
Be an ongoing organization, association, or group of three or more persons
Have a common interest and/or activity characterized by the commission of or involvement in a pattern of criminal or delinquent conduct.
If a value of ‘N - None/Unknown’ is entered, codes “J” and “G” cannot to be entered.
Allowed Values
Up to three (3) of the following *Gang Activity Codes can be entered for applicable Offenses. ___
Type of Gang Information Codes
J - Juvenile Gang
G - Other Gang
N - None or Unknown
Examples (Gang Information):
Example
Description
Number
Two males, aged 19, were on bicycles riding through a neighborhood when they were approached by three males and forced to stop. Words were exchanged and
1 one of the bicyclists was attacked. Each of the three attackers, one, aged 16 and the other two, aged 17, had identical tattoos on their upper arm. This marking was
commonly associated with a local gang. The entry for Type of Criminal Activity/Gang Information should be Juvenile Gang (“J”).
Type of Weapon/Force Involved Nos. 1, 2 and 3 (13)
Description: Type of Weapon/Force Involved allows Officers to report what kind of weapons were used by an Offender to commit an Offense. It is restricted for use with Certain NIBRS
Codes (listed in Requirement 4 below). If one of these NIBRS Codes is present, then this Data Element has to have a value, otherwise it cannot have a value and should be all blanks.
Data Characteristics: Up to 3x, 3 Character Alpha/Numeric. First two characters should be a number that corresponds to the List of Available Data Element Values, and the third
character is used as the Automatic Weapon Designator, which is and can only be used to designate if a Firearm was an Automatic Weapon or not. If ‘N’ for None is used, then no other
Values can be included in the other slots for the Data Element.
Requirements :
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the List of
1 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
Available Data Element Values.
When more than one value is present, the same value is not allowed to be
2 12006 ERROR - DUPLICATE VALUE
repeated.
Value ‘99 - None’ is mutually exclusive with any other value. No other values
3 12007 ERROR - MUTUALLY EXCLUSIVE VALUES USED
should be included if ‘99’ is used.
This Data Element must and can only contain a value if it is associated with an
Offense with one of the following NIBRS Codes:
09A, 09B, 09C
100, 120
4 11A, 11B, 11C, 11D 12019 DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
13A, 13B
210, 520
64A, 64B
The third character of Type of Weapon/Force Involved (DE 13) can only either
5 12055 AUTOMATIC INDICATOR MUST BE BLANK OR ‘A’
be ‘A - Automatic’ or ‘ ‘ (Blank Space).
Only the following values are allowed to use the ‘A - Automatic Weapon’
indicator in Type of Weapon/Force Involved (DE 13):
11 Firearm (Type not Stated)
12 Handgun WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN ‘A’ IN
6 12058
13 Rifle THE AUTO INDICATOR
14 Shotgun
15 Other Firearm
When an Offense is a Simple Assault (NIBRS 13B), Type of Weapon/Force
INVALID WEAPON WITH AN OFFENSE OF SIMPLE ASSAULT
7 Involved (DE 13) may only be Personal Weapons (40), Other (90), or Unknown 12065
(13B); ACCEPTED WEAPON CODES ARE 40, 90, 95
(95).
For Homicide Offenses (NIBRS 09A, 09B, or 09C), Type of Weapon/Force
8 Involved (DE 13) cannot be None (99). Some Type of Weapon/Force Involved 12067 INVALID WEAPON WITH AN OFFENSE
other than None (99) must be used in a Homicide Offense.
Simple Assault Offenses (NIBRS 13B) can only use Type of Weapon/Force
Involved (DE 13) Values of:
Personal Weapons (40)
Other (90)
Unknown (95)
If the offense included one of the following Weapon Types, it should be POSSIBLE CLASSIFICATION ERROR OF AGGRAVATED
9 12069
reported as an Aggravated Assault (13A): ASSAULT ‘13A’ CODED AS SIMPLE ‘13B’
11/11A Firearm or Automatic Firearm
12/12A Handgun or Automatic Handgun
13/13A Rifle or Automatic Rifle
14/14A Shotgun or Automatic Shotgun
15/15A Other Firearm or Other Automatic Firearm
A NIBRS 13A Offense must have at least one Type of Weapon/Force Used (DE NIBRS 13A OFFENSE REQUIRES TYPE OF WEAPON/FORCE
10 13100
13) entered with it. (DE 13)
INVALID TYPE OF WEAPON / FORCE INVOLVED WITH AN
If the Offense is a NIBRS 13A (Aggravated Assault), Type of Weapon/Force
OFFENSE OF NIBRS = 13 A;WEAPON / FORCE INVOLVED
11 Involved (DE 13) cannot be None (99), and the Type of Injury (DE 33) must be 90036
CANNOT BE NONE WITH THE INJURY TYPE OTHER THAN
something other than None (N)
NONE
Details:
This data element is used to enter the Type of Weapon/Force Used (13) by an Offender.
Append an “A” if the weapon is automatic.
Any firearm that can fire more than one shot by a single pull of the trigger without manual reloading is classified as an Automatic Firearm.
Something like a Bump Stock, which is designed to simulate Automatic Fire, should not be considered Automatic because it does not meet the requirement of a single trigger
pull firing more than one round. Instead it is multiple trigger pulls that are in quick succession.
List of Allowed Entries for DE 13 is on the following page:
Allowed Entries:
Can enter up to three (3) codes for each offense:
Types of Weapon/Force Involved
11 - Firearm (type not stated)
12 - Handgun
13 - Rifle
14 - Shotgun
15 - Other Firearm
20 - Knife or Cutting Instrument
30 - Blunt Object
35 - Motor Vehicle / Vessel (When used as a weapon)
40 - Personal Weapons
50 - Poison
60 - Explosives
65 - Fire or Incendiary Device
70 - Drugs, Narcotics or Sleeping Pills
85 - Asphyxiation
90 - Other
95 - Unknown
99 - None (Mutually Exclusive to any other value)
Examples:
Example
Description
Number
Three robbers held up a bank. One was armed with a revolver, the second had a sawed-off shotgun, and the third had an automatic machine gun. The entries
1
would be: Handgun (‘12’), Shotgun (‘14’) and Other Automatic Firearm (‘15A’).
Property Sequence Number (P1)
Description: Property Sequence Number is a uniquely identifying number for each Property that’s included in the Incident. It is used to link Properties to Offenses in Segment 33’s. The
same Property Sequence Number can be used Multiple Times across Segment 33’s in an Incident, because it’s possible for a Property to be involved in more than one Offense.
Data Characteristics: 3 Character Numeric. Must be front-padded with zeros to make a three-digit number (EG: 1 would be 001). Must be unique for each Segment 31.
Requirements :
Error
Requirement Requirement Description Error Message
Number
Property Sequence Number (DE P1) cannot be repeated across multiple Segment 31’s
1 12006 ERROR - DUPLICATE VALUE
(Property Description Segment) in an Incident.
Property Sequence Number (DE P1) is a required field for each Segment 31 (Property PROPERTY SEQUENCE NUMBER MUST BE
2 90019
Description Segment) present in the Incident. PRESENT–CANNOT BE BLANK
Property Sequence Number (DE P1) should be a three-digit numeric value between 001 and PROPERTY SEQUENCE NUMBER MUST BE
3 90020
999, front-padded with Zero’s. EG: A Sequence Number of 1 would be 001. NUMBER ENTRY WITH ZERO LEFT - FILL
Details:
Each property in an incident must be assigned a unique sequence number from “001” to “999”.
Property Sequence Number Reference (P1R)
Description: Property Sequence Number Reference is only used in Segment 33 to link Properties to Offenses. It should be present in each Segment 33 in the Incident, and should
refernce the value of one of the Property Seqence Numbers (DE P1) in the Property Description Segments (Segment 31).
Data Characteristics: 3 Character Numeric. Must be front-padded with zeros to make a three-digit number (EG: 1 would be 001). May repeat across multiple Segment 33’s, as a single
property can be involved in more than one Offense.
Requirements :
Error
Requirement Requirement Description Error Message
Number
Property Sequence Number Reference (DE P1R) is a required field for each Segment 33 PROPERTY SEQUENCE NUMBER MUST BE
1 90019
(Property/Offense Relationship Segment) present in the Incident. PRESENT–CANNOT BE BLANK
Property Sequence Number Reference (DE P1R) should be a three-digit numeric value
PROPERTY SEQUENCE NUMBER MUST BE
2 between 001 and 999, front-padded with Zero’s. EG: A Sequence Number of 1 would be 90020
NUMBER ENTRY WITH ZERO LEFT - FILL
001.
Property Sequence Number Reference (DE P1R) must match the Property Sequence Number PROPERTY SEQUENCE NUMBER DOES NOT
3 (DE P1) of one of the Property Description Segments (Segment 31) submitted in the 90024 MATCH ANY PROVIDED PROPERTIES’
incident. SEQUENCE NUMBERS
Details:
There is no UNIQUE constraint for the Property Sequence Number Reference. This allows for a Property to relate to many Offenses if multiple Property/Offense segments are
submitted within a single incident.
Type of Property Loss (14)
Description: Type of Property Loss is used to describe the condition of a Property that’s associated with in an Offense. The usage of values for Property Loss Type is limited to the
NIBRS Code of the Offense that the Property is associated with, as well as whether or not the Offense was Attempted or Completed. You can see the full list of what Loss Types you can
use with which NIBRS Codes on the Allowable Property Loss Types By NIBRS Table.
Data Characteristics: 1 Character Numeric. Mandatory for each Segment 31 (Property Description Segment) that is included in the Incident.
Requirements :
Error
Requirement Requirement Description Error Message
Number
For every Property Description Segment (Segment 31) having a Type of Property Loss (DE 14) of ‘5 -
Recovered’, there must also be a corresponding Segment 31 having the same Property Description (DE 15)
code and a Type of Property Loss of 7 - Stolen/Etc’.
RECOVERED PROPERTY
1 This rule does not apply to: 10072 MUST ALSO BE
NIBRS Offense codes of 280 and 250. SUBMITTED AS STOLEN
When a Property Description of Vehicle Parts/Accessories ('38') is subsequently reported as Recovered
when a vehicle was stolen, so long as the individual parts within a vehicle were not reported as Stolen.
When one of the following NIBRS Codes is used and the Offense is ‘A - Attempted’, then the Property Loss
Type (DE 14) can only be ‘1 - None’ or ‘8 - Unknown’:
100, 120
200, 210, 220, 240, 250, 270, 280, 290
NEED A PROPERTY LOSS
23A, 23B, 23C, 23D, 23E, 23F, 23G, 23H
CODE OF ‘1’ OR ‘8’ WHEN
2 26A, 26B, 26C, 26D, 26E 10077
THIS OFFENSE IS
35A, 35B
ATTEMPTED
39A, 39B, 39C, 39D
510
90A, 90Z
THIS PROPERTY LOSS
The Type of Property Loss Code (DE 14) must be applicable to Offense(s) submitted. Refer to the List of CODE CANNOT EXIST
3 10081
Available Values for the correct values to use for each of the offenses. WITH THE OFFENSES
SUBMITTED
INVALID DATA VALUE–NOT
Property Loss Type (DE 14) is a mandatory Data Element that must be a numeric value between 1 and 8. Check
4 11004 ON LIBRS VALIDATION
the List of Available Data Element Values for the available values and their definitions
TABLE
Type of Property Loss (DE 14) should only be entered for Offenses with a NIBRS Code that is one of the
following:
100, 120
200, 210, 220, 240, 250, 270, 280, 290
23A, 23B, 23C, 23D, 23E, 23F, 23G, 23H DATA CAN ONLY BE
5 26A, 26B, 26C, 26D, 26E 13019 ENTERED FOR SPECIFIC
35A, 35B OFFENSES
39A, 39B, 39C, 39D
510
90A, 90Z
When Type of Property Loss (DE 14) is None (1) or Unknown (8), then Data Elements 15 through 22 must be
DATA ELEMENTS 15 - 22
left blank for all Offenses except for NIBRS 35A .
MUST BE BLANK WHEN
6 13052
PROPERTY LOSS CODE = 1
When the associated NIBRS Offense Code is 35A, and the Property Loss Type (DE 14) is ‘1 - None’, then
OR 8
Suspected Drug Type (DE 20) must have a valid entry.
Details:
Type of Property Loss (14) describes the various type(s) of property loss that can occur during an incident, such as Recovery, Seizure, etc.
Every different type of property loss that occurs during an incident must be submitted in a separate Property Description Segment (31), when the incident involved one or more
of the Offenses listed above. For instance if a Property is stolen and then recovered, there should be two Property Description Segments (Segment 31) that have a Property Loss
Type of 7 for Stolen and 5 for Recovered.
Allowed Entries:
Enter only one (1) code for each Property Description Segment. However, as many property segments as applicable can be submitted per incident:
Types of Property Loss
Types of Property Loss
1 - None
2 - Burned
3 - Counterfeited or Forged
4 - Destroyed, Damaged or Vandalized
5 - Recovered
6 - Seized
7 - Stolen, Etc.
8 - Unknown
Available Property Loss Types by NIBRS Code
To see a list of which Property Loss Types are available for each NIBRS Code based on their Attempted/Completed Status, you can find it here: List of Available DE 14 NIBRS Values
Property Description (15)
Description: Property Description is a value that corresponds to a list of the kinds of Properties that can be reported to the State and FBI.
Data Characteristics: 2 Character Numeric between 01 and 99 that corresponds to a value of the List of Available Data Element Values. Required field when Property Loss Type is not 1
or 8.
Requirements :
Error
Requirement Requirement Description Error Message
Number
Property Description (DE 15) must be a two-digit, numeric value greater than or equal to 01. Check INVALID DATA VALUE–NOT ON LIBRS
1 11004
the List of Available Data Element Values for the available values and their definitions VALIDATION TABLE
Property Description is a required Data Element for all Property Description Segments (Segment MISSING PROPERTY DESCRIPTION (DE
2 13072
31) that do not contain a Property Loss Type (DE 14) of 1 or 8. 15)
A Property Description (DE 15) code must be entered when the value entered in Type of Property
Loss/Etc. (DE 14) contains the following:
2 - Burned
3 - Counterfeited or Forged PROPERTY DESCRIPTION (DE 15) IS
3 4 - Destroyed, Damaged or Vandalized 13075 REQUIRED FOR THIS PROPERTY LOSS
5 - Recovered TYPE
6 - Seized
7 - Stolen/Etc.
WITH PROPERTY LOSS = 6 & ONLY
For NIBRS 35A Offenses (Drug/Narcotic Violations), Property Description (DE 15) can only have a
DRUG OFFENSE, CANNOT HAVE A
value of ‘10 - Drugs or Narcotics’. Similarly for NIBRS 35B Offenses (Drug Equipment Violations),
4 13087 DESCRIPTION 11;OR PROPERTY LOSS =
Property Description (DE 15) can only have a value of ‘11 - Drug Narcotic Equipment. This rule is,
6 & ONLY DRUG EQUIP OFNSE
however, bypassed if the property is involved in another Crime Against Property.
CANNOT HAVE DESCRIPTION 10
Based on the Offenses that are present in the Incident, there has been an illogical assignment of
one or more Property Descriptions to one or more Offenses. Please check that your Segment 33 ILLOGICAL PROPERTY DESCRIPTION
5 13090
(Propery/Offense Relationship) Segment is both present and properly linking the Properties to the FOR THE OFFENSE(S) SUBMITTED
appropriate Offenses.
DE 18 MUST BE BLANK (NOT 00)
While you can submit a Property that has a Loss Type of ‘7 - Stolen’ and a Description of a Vehicle UNLESS INCIDENT CONTAINS A NIBRS
6 with NIBRS 120 and 26A Offenses, you should not include them in the count of Stolen Vehicles (DE 13101 240 OFFENSE WITH PROPERTY THAT
18); it should be left blank (Not 00, but two blank spaces). HAS A LOSS TYPE OF ‘7 - STOLEN’ AND
DESCRIPTION OF 03, 05, 24, 28, OR 37
Details:
Property Description (DE 15) is to be used to enter descriptions of the property that was burned, counterfeited, destroyed/damaged/vandalized, etc., during, or as a result of, the
incident.
Allowed Entries:
Enter only one Property Description (DE 15) code per Property Description (31) Segment, entering multiple Property Description (31) Segments for multiple Properties.
This also applies to multiples of Property Descriptions. You should submit a Segment 31 for each Property Involved in the Incident, even if it is the same as another
Property.
EG: Three TV’s are stolen from Best Buy. Being the same Make and Model, they all will have the same Description and Value, however you should submit three
Property Description Segments to LIBRS.
Do NOT enter duplicate Property Sequence Numbers (DE P1) within an incident unless a different Type of Property Loss (DE 14) is used.
EG: Just because those three TV’s in the previous example are all the same make, model, and value, doesn’t mean they should have the same Property Sequence Number.
LIBRS will aggregate the counts of Property Descriptions and the Total Values associated with them for NIBRS Extraction. Therefore the FBI will not receieve this granular of data,
however the State of Louisiana Will.
Property Descriptions
01 - Aircraft
02 - Alcohol
03 - Automobiles
04 - Bicycles
05 - Buses
06 - Clothes or Furs
07 - Computer Hardware or Software
08 - Consumable Goods
09 - Credit or Debit Cards
10 - Drugs or Narcotics
11 - Drug Narcotic Equipment
12 - Farm Equipment
Property Descriptions
13 - Firearms
14 - Gambling Equipment
15 - Heavy Construction or Industrial Equipment
16 - Household Goods
17 - Jewelry, Precious Metals
18 - Livestock
19 - Merchandise
20 - Money
21 - Negotiable Instruments
22 - Non-negotiable Instruments
23 - Office-type Equipment
24 - Other Motor Vehicles
25 - Purses, Handbags or Wallets
26 - Radios, TVs, VCRs or Cameras
27 - Recordings: Audio or Visual
28 - Recreational Vehicles
29 - Structures: Single Occupancy Dwellings
30 - Structures: Other Dwellings
31 - Structures: Other Commercial/Business
32 - Structures :Industrial/Manufacturing
33 - Structures: Public/Community
34 - Structures: Storage
35 - Structures: Other
36 - Tools
37 - Trucks
38 - Vehicle Parts or Accessories
39 - Watercraft
41 - Aircraft Parts/Accessories
42 - Artistic Supplies/Accessories
43 - Building Materials
44 - Camping/Hunting/Fishing Equipment/Supplies
45 - Chemicals
46 - Collections/Collectibles
47 - Crops
48 - Documents/Personal or Business
49 - Explosives
59 - Firearm Accessories
64 - Fuel
65 - Identity Documents
66 - Identity–Intangible
67 - Law Enforcement Equipment
68 - Lawn/Yard/Garden Equipment
69 - Logging Equipment
70 - Medical/Medical Lab Equipment
71 - Metals, Non-Precious
72 - Musical Instruments
73 - Pets
74 - Photographic/Optical Equipment
75 - Portable Electronic Communications
76 - Recreational/Sports Equipment
77 - Other
78 - Trailers
79 - Watercraft Equipment/Parts/Accessories
80 - Weapons–Other
88 - Pending Inventory
99 - Special category used by the National UCR program to compile statistics.
Value of Property (16)
Description: Value of Property is the a 9-digit number that references the whole-dollar value of the Property that is described in Segment 31. For example, a property with a value of
$1000 would have a Property Value of ‘000001000’.
Data Characteristics: 9 Character Numeric. Must be front-padded with Zero’s (0) to make a nine-digit number. Cannot contain any blank spaces or periods (.) to act as Decimals. All
Property Values should be rounded up to the nearest whole dollar value.
Requirements :
Error
Requirement Requirement Description Error Message
Number
When a Property has been Recovered, the Property Value (DE 16) in the Property Description Segment
RECOVERED PROPERTY VALUE
(Segment 31) that notes it as recovered cannot have a greater value than the Property Value in the
1 10084 CANNOT BE GREATER THAN THE
Property Description Segment that lists it as stolen. In short: A recovered property cannot be more
VALUE WHEN STOLEN
valuable than when it was stolen.
CONTAINS NON NUMERIC
2 Must be numeric entry with zero left-fill. if entered. 13002
ENTRY
When Value of Property (DE 16) contains a value that exceeds a LIBRS assigned threshold amount, a
‘Warning’ message is created. The agency is asked to check if the value entered was a data entry error, or WARNING - PROPERTY
if it was an intended entry. DESCRIPTION (DATA ELEMENT
3 13042 15) HAD A VALUE (DATA
Also, a Warning message is always produced when the value is $1,000,000 or greater. For example, if the ELEMENT 16) THAT EXCEEDED
value of a property was $12,000.99 but was inadvertently entered as $1,200,099 in LIBRS submission file, THRESHOLD OF [$ VALUE]
a ‘Warning’ message will be generated. In this case, the cents were entered as whole dollars.
A value of ‘000000000’ for Property Value (DE 15) is not permitted for this Property Description (DE 15). PROPERTY VALUE OF ZERO IS
4 13051
To designate that the value is unknown, use ‘000000001’ for $1, instead. NOT ALLOWED
When Pending Inventory (‘88’) is entered, then Value of Property (DE 16) must be Unknown (‘1’,
PENDING INVENTORY MUST
5 representing $1.00). One dollar is used as a quality assurance edit check that instructs LIBRS to accept the 13053
HAVE PROPERTY VALUE OF ‘1’
Pending Inventory (‘88’) entry.
DATA ELEMENT 15 WAS NOT
6 If a Value of Property (DE 16) has a code entered, then Property Description (DE 15) must be entered. 13054
ENTERED, BUT VALUE ($) WAS
PROPERTY VALUE (DE 16) IS
Property Value (DE 16) is a required Data Element for any Property Description (DE 15) that is not ‘10 -
7 13073 REQUIRED FOR THIS PROPERTY
Drugs/Narcotics’
LOSS TYPE
When one of the following Property Descriptions (DE 15) are used, the Property Value (DE 16) must be
None (‘000000000’ or 9 Blank Spaces):
09 Credit/Debit Cards
22 Nonnegotiable Instruments
48 Documents/Personal or Business PROPERTY VALUE MUST BE
8 65 Identity Documents 13091 ZERO FOR SELECTED PROPERTY
66 Identity-Intangible DESCRIPTION
Note that in addition to those listed, 77 - Other can also have a Property Value of Zero, however unlike
the others listed, it is not mandatory that it is always Zero. It can be Zero, Unkonwn (1), or an actual
value.
Details:
Value of Property (16) is to be used to enter the total dollar value of property that was burned (includes damage caused in fighting the fire), counterfeited, destroyed/damaged/
vandalized, recovered, seized, stolen, etc., as a result of the incident.
DO NOT INCLUDE partial dollar amounts (cents). Round values to the nearest whole dollar amounts. If the value is unknown, enter one dollar ($1.00), that is, “000000001”.
If value is known and it is between $1.00 and $2.00 the reporting agency should enter $2.00, that is, “000000002”. This is the minimum dollar value that can be entered in Value
of Property (16), as “1” (or “000000001”) is used for Unknown.
Examples:
Example
Description
Number
A man purchases a new power saw from the hardware store. Later that same day someone breaks into his truck and steals the saw. The saw was purchased for
1
$95.73. The value of the property would be rounded to the nearest whole dollar and reported as ‘000000096’- $96.00.
Date Recovered (17)
Description: Date Recovered is the date in with a Property that was previously stolen was recovered. Any Segment 31 that has a Property Loss Type os ‘5 - Recovered’ needs to have a
Date Recovered. Otherwise, the Data Element should be Blank Spaces.
Data Characteristics: 8 Character Date in MMDDYYYY Format. Required if Property is recovered, Blank Spaces if not.
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for Date Recovered (DE 17) is not valid. Please ensure that the
1 11005 DATE ENTERED MUST BE A VALID CALENDAR DATE
supplied date is in the MMDDYYY Format.
RECOVERY DATE MUST EXIST WHEN SEGMENT 50
If there are any Property Description Segments (Segment 31) that indicated that a
2 13001 CONTAINS A PROPERTY LOSS TYPE (DE 14) OF ‘5 -
property has been recovered, then Date Recovered (DE 17) must have a value.
RECOVERED’
The Date Recovered (DE 17) cannot be a date and time that is earlier than when the
3 13007 CANNOT BE EARLIER THAN INCIDENT DATE/HOUR.
incident occurred.
Unless Property Loss Type (DE 14) is ‘5 - Recovered’, then Date Recovered (DE 17) PROPERTY LOSS CODE (14) MUST = 5 (RECOVERED)
4 13055
must not be entered. FOR DATA TO BE ENTERED
If Date Recovered (DE 17) has a value, then both Property Description (DE 15) and PROPERTY DESCRIPTION (15) AND VALUE (16)
5 13056
Value of Property (DE 16) must be entered. MUST BOTH EXIST IF DATA IS PRESENT
Recovered Date (DE 17) cannot have a date that’s later that the Period being
DATE RECOVERED CANNOT BE GREATER THAN
6 Reported. EG: A Recovery Date of 06/01/2020 would be invalid for the 052020 23235
REPORT MONTH AND YEAR
Reporting Period.
Details:
If previously stolen property is recovered, the month, day, and year (MMDDYYYY) of its recovery should be entered into this data element.
If there is more than one Date Recovered (DE 17) for the same Property Description (DE 15), enter the earliest date.
If the Date Recovered is unknown, enter the date of the report.
Number of Stolen Vehicles (18)
Description: Number of Stolen Vehicles is the sum of the Segment 31’s that have a Property Description containing a Vehicle and a Property Loss Type of ‘7 - Stolen’. For it to appear in
Segment 30 with any value other than Zero (0), there must be Segment 31’s present in the Incident that meet those conditions.
Data Characteristics: 2 Characters Numeric. If less than 10, a Zero (0) should be in the first character (EG: 01, 02, 03, etc…). Should always have a value when Segment 30 is present,
using ‘00’ if no stolen vehicle are present in the Incident. Update 07/2021 - This should only have a value if there is a Completed 240 - MV Theft Offense in the Incident. 00 does not
represent 0 stolen vehicles, rather ‘Unknown’.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 Must be numeric entry with zero left-fill, if entered. EG: 1 stolen vehicle would be ‘01’. 13002 CONTAINS NON NUMERIC ENTRY
In order for Number of Stolen Vehicles (DE 18) to contain a value other than ‘0’ (Zero),
the following conditions must be true:
The Incident contains an Offense with a NIBRS Offense Code of 240
Offense Attempted/Completed (DE 7) is Completed ('C')
PROPERTY LOSS (14) MUST BE 7 WITH A MOTOR
Further, when these conditions are met, it is also required that Property Loss Type (DE
VEHICLE THEFT OFFENSE CODE WITH PROPERTY
2 14) is ‘7 - Stolen’, and the Property Description for the stolen property is either: 13057
DESCRIPTION CODES OF ‘03’, ‘05’, ‘24’ ,’28’ , OR
03 - Automobiles
‘37’ FOR DATA TO BE ENTERED
05 - Buses
24 - Other Motor Vehicles
28 - Recreational Vehicles
37 - Trucks
When Number of Stolen Vehicles (DE 18) is a non-zero value, then there must be
Property Description Segment(s) (Segment 31) that list a Property with a Property Loss
Type (DE 14) of ‘7 - Stolen’ and one of the following Property Descriptions (DE 15) as :
DATA MUST EXIST WITH A MOTOR VEHICLE
03 - Automobiles
THEFT OFFENSE WITH PROPERTY DESCRIPTION
3 05 - Buses 13058
CODES OF ‘03’, ‘05’, ‘24’, ‘28’, OR ‘37’ AND A
24 - Other Motor Vehicles
PROPERTY LOSS OF 7
28 - Recreational Vehicles
37 - Trucks
In order to supply a value for Number of Stolen Vehicles or Number of Recovered NUMBER OF STOLEN AND NUMBER OF
Vehicles, the Incident must contain at least one 240 (MV Theft) Offense that is RECOVERED VEHICLES MUST BE LEFT BLANK
4 13050
completed, and a Segment 31 that contains a Property Description of Vehicle, and a BASED ON THE OFFENSES AND PROPERTIES
Loss Type of 7 - Stolen. SUPPLIED
Details:
Number of Stolen Vehicles (18) indicates how many motor vehicles were stolen in an incident reported as a Motor Vehicle Theft.
Number of Recovered Motor Vehicles (19)
Description: The Number of Recovered Motor Vehicles, similar to DE 18, is the number of Property Description Segments (Segment 31) that have a Property Description (DE 15) that
contains a Vehicle, and a Property Loss Type (DE 14) of ‘5 - Recovered’.
Data Characteristics: 2 Characters Numeric. If less than 10, a Zero (0) should be in the first character (EG: 01, 02, 03, etc…). Should always have a value when Segment 30 is present,
using ‘00’ if no recovered vehicle are present in the Incident. Update 07/2021 - This should only have a value if there is a Completed 280 - Illegal Property Offense in the Incident. 00
does not represent 0 recovered vehicles, rather ‘Unknown’.
Requirements:
Error
Requirement Requirement Description Error Message
Number
If number between 01 and 99 is entered, it must be equal to or less than the number NUMBER OF RECOVERED VEHICLES CANNOT BE
1 10073
reported Stolen in Number of Stolen Motor Vehicles (18). GREATER THAN THE NUMBER STOLEN
Must be numeric entry with zero left-fill, if entered. EG: 1 recovered vehicle would be
2 13002 CONTAINS NON NUMERIC ENTRY
‘01’.
When Number of Recovered Vehicles (DE 19) is a non-zero value, there must be
Property Description Segment(s) (Segment 31) that have a Property Loss Type (DE 14)
of ‘5 - Recovered’ for one of the following Property Descriptions (DE 15) as :
DATA MUST EXIST WITH A MOTOR VECHICLE
03 - Automobiles
THEFT OFFENSE WITH PROPERTY DESCRIPTION
3 05 - Buses 13061
CODES OF ‘03’, ‘05’, ‘24’, ‘28’ OR ‘37’ AND A
24 - Other Motor Vehicles
PROPERTY LOSS OF 5
28 - Recreational Vehicles
37 - Trucks
NUMBER OF STOLEN AND NUMBER OF
RECOVERED VEHICLES MUST BE LEFT BLANK
4 13050
BASED ON THE OFFENSES AND PROPERTIES
SUPPLIED
INCORRECT COUNT FOR NUMBER OF RECOVERED
While counterintuitive, vehicles that are associated with a NIBRS 280 Offense should VEHICLES - YOU SHOULD NOT INCLUDE
4 10079
not counted towards DE 19, Number of Recovered Vehicles. RECOVERED VEHICLES ASSOCIATED WITH A NIBRS
280 IN THIS COUNT
Details:
Number of Recovered Motor Vehicles (19) indicates how many motor vehicles were recovered in an incident that reported Motor Vehicle Thefts.
Suspected Drug Type (20)
Description: Suspected Drug Type is a short code that is used to identify the type of Drug(s) that were found for NIBRS 35A Offenses. Should only be included when there’s a 35A
Offense Involved that is Completed, and has a Property Loss Type of ‘1 - None’ or ‘6 - Seized’. Otherwise it should remain Blank Spaces.
Data Characteristics: 2 Character Alpha. Should be left as Blank Spaces (G) if the conditions for usage listed in the requirements is not met.
Requirements:
Error
Requirement Requirement Description Error Message
Number
The reported Suspected Drug Type (DE 20) was not recognized.
1 Check the List of Available Data Element Values for the available 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
values and their definitions
You should not include values for Suspected Drug Type (DE 20)
unless:
UNLESS PROPERTY LOSS TYPE (DE 14) IS 1 OR 6, AND NIBRS IS 35A,
The Offense is a NIBRS 35A Offense
2 13064 SUSPECTED DRUG TYPE (DE 20), DRUG QUANTITY (DE 21) AND DRUG
Attempted/Compelted (DE 7) is 'C - Completed'
MEASUREMENT TYPE (DE 22) CANNOT HAVE A VALUE
the Property Loss Type is '1 - None' or '6 - Seized'
If the following conditions are met, then you should include
Suspected Drug Type (20):
NIBRS Offense Code of 35A
Attempted/Completed (DE 7) of 'C - Completed
DATA ELEMENT MUST EXIST WHEN OFFENSE = DRUG OFFENSE & PROP
3 Type of Property Loss (DE 14) is Seized ('6') 13065
LOSS = 6 AND DESCRIPTION = 10
Property Description (DE 15) is Drugs/Narcotics ('10')
If there are multiple 35A Offenses, only include Suspected Drug
Type (DE 20) for those who satisfy the listed conditions above.
Suspected Drug Type (DE 20) should be entered when:
The only Offense(s) that is/are reported are NIBRS 35A
35A OFFENSE ENTERED AND ‘1 - NONE’ ENTERED; MISSING SUSPECTED
4 Any of the Offenses have a Property Loss Type (DE 14) of 13092
DRUG TYPE (DE 20)
'1 - None'
The second character of Suspected Drug Type (DE 20) can only
5 23201 SECOND CHARACTER MUST BE ‘X’ OR BLANK
be ‘X - Counterfeit’ or a Blank Space (G).
Details:
Suspected Drug Type (20) identifies the type of drugs or narcotics Seized in a drug case.
If the Suspected Drug Type (20)is a Counterfeit, append an “X” to the drug code, otherwise leave the second character Blank (G).
Suspected Drug Type (20) is not to be used when drugs or narcotics were Burned, Stolen, etc., in connection with other offenses, such as Arson, Larceny/Theft, etc.
List of Allowed Entries for DE 20 is on the following page:
Allowed Entries:
Enter one per Segment 31 that has a Property Description of ‘10 - Drugs/Narcotics’. There are no restrictions on multiple Segment 31’s having the same Suspected Drug type (EG: You
can report 1 lb of Marijuana, as well as 10 Marijuana Plants as two different Segment 31’s, or if two people are found in possession of the same drug type on their person, you can
report both of those containers as separate properties).
Suspected Drug Types
A - 'Crack' Cocaine
B - Cocaine
C - Hashish
1 - Hash Oil (LIBRS Only). Sent to NIBRS as “C”
D - Heroin
E - Marijuana
F - Morphine
G - Opium
H - Other Narcotics:
Codeine
Demerol
Dihydromorphinone or Dilaudid
Hydrocodone or Percodan
Methadone
I - LSD
J - PCP
K - Other Hallucinogens:
BMDA or 'White Acid'
MT, MDA, or MDMA
Mescaline or Peyote
Psilocybin
STP
L - Amphetamines / Methamphetamines
M - Other Stimulants:
Adipex, Fastine, and Ionamin (Derivatives of Phentermine)
Benzedrine
Didrex
Methylphenidate or Ritalin
Phenmetrazine or Preludin
Tenuate
N - Barbiturates
O - Other Depressants:
Glutethimide or Doriden
Methaqualone or Quaalude
Pentazocine or Talwin
P - Other Drugs:
Antidepressants (Elavil, Triavil, Tofranil, Etc.)
Aromatic Hydrocarbons
Propoxyphene or Darvon
Tranquilizers (Chlordiazepoxide or Librium, Diazepam or Valium, Etc.)
U - Unknown Type Drug
Estimated Drug Quantity (21)
Description: Estimated Drug Quantity is the amount of a Drug or Narcotic that was involved in a Completed, NIBRS 35A Offense that has a Property Loss Type of ‘1 - None’ or ‘6 -
Seized’. Note that there is a decimal in the Format. This decimal should only be included if the Data Element is supposed to be included (EG: You’re not supposed to enter
‘GGGGGGGGG.GGG’ (Where G is a Blank Space) if this Data Element shouldn’t have a value; instead enter all blanks).
Data Characteristics: 13 Character Alpha/Numeric. The only Alpha Character is supposed to be the Decimal that occurrs in position 10 of the Data Element. Otherwise everything is
expected to be Numeric. Should also be front-padded with zeros as needed. Significant Figures don’t matter here, and you should always include the decimals after the whole number.
(EG: Even though 100.000 and 100 are the same thing, you should still include the decimal places and submit ‘000000100.000’)
Format: #########.###
Requirements:
Error
Requirement Requirement Description Error Message
Number
Must be numeric entry with Zero ('0') or Blank (G)
left-fill and right-fill (EG: '000000100.000' to
represent '100')
The decimal fractional quantity must be
1 13002 CONTAINS NON NUMERIC ENTRY
expressed in thousandths as three digits
The decimal point must be the tenth character of
the field
You should not include values for Drug Quantity (DE 21)
unless:
UNLESS PROPERTY LOSS TYPE (DE 14) IS 1 OR 6, AND NIBRS IS 35A, SUSPECTED
The Offense is a NIBRS 35A Offense
2 13064 DRUG TYPE (DE 20), DRUG QUANTITY (DE 21) AND DRUG MEASUREMENT TYPE
Attempted/Compelted (DE 7) is 'C - Completed'
(DE 22) CANNOT HAVE A VALUE
the Property Loss Type is '1 - None' or '6 - Seized'
If the following conditions are met, then you should
include Estimated Drug Quantity (21):
NIBRS Offense Code of 35A
Attempted/Completed (DE 7) of 'C - Completed
Type of Property Loss (DE 14) is Seized ('6')
DATA ELEMENT MUST EXIST WHEN OFFENSE = DRUG OFFENSE & PROP LOSS =
3 Property Description (DE 15) is Drugs/Narcotics 13065
6 AND DESCRIPTION = 10
('10')
If there are multiple 35A Offenses, only include
Estimated Drug Quantity (21) for those who satisfy the
listed conditions above.
When Estimated Drug Quantity (21) is entered,
WITH DATA ENTERED, SUSPECTED DRUG TYPE (DE 20) AND MEASUREMENT (DE
4 Suspected Drug Type (20) and Type Drug Measurement 13066
22) MUST BE PRESENT
(22) must also be entered.
Details:
Estimated Drug Quantity (21) indicates the quantity of drugs or narcotics seized in a drug case, it is not to be used when drugs or narcotics were Burned, Stolen, etc. in
connection with other Offenses, such as Arson, Burglary, Breaking and Entering, Larceny, Theft, etc.
Nine (9) characters are available to enter the number of WHOLE pounds, ounces, grams, etc., and three (3) more characters are available to enter the DECIMAL amount. A
DECIMAL POINT must be entered to separate the whole and decimal amounts. Zero (‘0’) or space fill (G) should be added to the right or left of the value to preserve the
decimal’s position as the tenth character in the field.
When Estimated Drug Quantity (21) is Unknown enter ‘000000001.000’, a value of ‘1’, to signify that the value is not known or not reported. Also, Type Drug Measurement (22)
MUST be entered as Not Reported/Unknown (‘XX’) and Value of Property (16) MUST be entered as Unknown (000000001).
If LRS Offense (6) is not reportable as a drug violation (35A), this data element MUST BE LEFT BLANK (G).
Type Drug Measurement (22)
Description: Drug Type Measurement is a shortcode that indicates the units for the Estimated Drug Quantity (DE 21). Not all units can be used with all Suspected Drug Types (DE 20).
For instance ‘NP - Number of Plants’ shouldn’t be used with something liek Amphetamines. However for the most part drugs these days come in many forms, so use whichever
Measurement Type makes the most sense (Volume for Liquids, Weight for loose Solids, Units for Pills, etc…)
Data Characteristics: 2 Character Alpha. Must be included if Estimated Drug Quantity (DE 21) has a value.
Requirements:
Error
Requirement Requirement Description Error Message
Number
The reported Drug Measurement Type (DE 22) was not recognized. Check the List of INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
Available Data Element Values for the available values and their definitions TABLE
You should not include values for Suspected Drug Type (DE 22) unless: UNLESS PROPERTY LOSS TYPE (DE 14) IS 1 OR 6,
The Offense is a NIBRS 35A Offense AND NIBRS IS 35A, SUSPECTED DRUG TYPE (DE 20),
2 Attempted/Compelted (DE 7) is 'C - Completed' 13064 DRUG QUANTITY (DE 21) AND DRUG
the Property Loss Type is '1 - None' or '6 - Seized' MEASUREMENT TYPE (DE 22) CANNOT HAVE A
VALUE
If the following conditions are met, then you should include Type Drug Measurement
(22):
NIBRS Offense Code of 35A
Attempted/Completed (DE 7) of 'C - Completed DATA ELEMENT MUST EXIST WHEN OFFENSE =
3 Type of Property Loss (DE 14) is Seized ('6') 13065 DRUG OFFENSE & PROP LOSS = 6 AND
Property Description (DE 15) is Drugs Narcotics ('10') DESCRIPTION = 10
If there are multiple 35A Offenses, only include Type Drug Measurement (22) for
those who satisfy the listed conditions above.
In order to use a Drug Measurement Type (DE 22) Value of ‘NP’, Suspected Drug Type DRUG TYPE MUST BE ‘E’, ‘G’, OR ‘K’ FOR A VALUE
4 13067
(DE 20) must have a value of either ‘E’, ‘G’, or ‘K’. OF ‘NP’
Estimated Drug Quantity (DE 21) must have a value of ‘000000001.000’ when Drug
Measurement Type (DE 22) is Not Reported (‘XX’). Note that the Incident will need to WITH A MEASUREMENT OF ‘XX’(NOT REPORTED)
5 13084
be resubmitted with the correct Drug Measurement Type (DE 22) and Drug Quantity DRUG QTY MUST = 00000001.000
(DE 20) at a later date.
Details:
Type Drug Measurement (22) indicates how Seized drugs and narcotics are quantified in a drug case.
Allowed Entries:
Type Drug Measurements
Weight Category
GM - Gram
KG - Kilogram
OZ - Ounce
LB - Pound
Volume Category
ML - Milliliter
LT - Liter
FO - Fluid Ounce
GL - Gallon
Units Category
DU - Dosage Units, Items (Number of Capsules, Pills, Tablets, Etc.)
NP - Number of Plants (e.g., Marijuana Plants (Bushes), Etc.)
Other
XX - Not Reported or Unknown
Victim Sequence Number (23)
Description: Victim Sequence Number is the uniquely identifying ID for each Victim in an Incident. This number cannot repeat in the same incident, and must be unique for each
Segment 50 that is present. This data Element can never be ommitted and must always have a value between 001 and 999.
Data Characteristics: 3 Character Numeric. Should be front-padded with Zero’s (0) to make a three digit number. (EG: 1 would be 001).
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 This is a required Data Element, and it cannot be left blank. 10001
MANDATORY FIELD
Victim Sequence Number (DE 23) should be a numeric entry, front-padded with zeros to make a three-digit number CONTAINS NON
2 15002
between 001 and 999. EG: 001, 002, 010 for Sequence Numbers 1, 2, and 10. NUMERIC ENTRY
VICTIM NUMBER
3 Victim Sequence Number (DE 23) must be a unique value for all Victims in the Incident. 15051
ALREADY EXISTS
Details:
Each victim in an incident MUST be assigned a unique Victim Sequence Number (23) from ‘001’ to ‘999’.
Offense Connected to Victim Sequence Number (24)
Description: Offense Connected to Victim Sequence Number is only used in Offense Segments Segmetn 20). Each Offense can only be related to a single Victim, so if there are multiple
Victims of the same Offense, or Multiple Offenses for the same Victim, you’ll need multiple Segment 20’s to reference that. This Data Element is important because it’s what’s used to
link the Offenders to their Offenses.
Data Characteristics: 3 Character Numeric. Should be front-padded with Zero’s (0) to make a three digit number. (EG: 1 would be 001). Needs to match a Victim Sequence Number (DE
23) that’s present in a Segment 50 of the Incident.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Offense Connected to Victim Sequence Number (DE 24) is a required Data Element and cannot be left MUST BE PRESENT–
1 10001
blank. Without a Victim to connect to an Offense, no crime has actually occurred. MANDATORY FIELD
Offense Connected to Victim Sequence Number (DE 24) contains a value that does not match up with the OFFENSE CONNECTED TO A
2 12090
Victim Sequence Numbers (DE 23) present in the Victim Segments (Segment 50) of the Incident. NON-EXISTENT VICTIM
Victim cannot be connected to Mutually Exclusive or Lesser Included Offenses.
Offenses are Mutually Exclusive when they cannot occur to the same victim in an incident by NIBRS
VICTIM CONNECTED TO AN
definitions. (Refer to the 'Offenses That Cannot Occur to the Same Victim' Table below)
3 15078 INVALID COMBINATION OF
Offenses are Lesser Included when, in the same incident, one Offense is an element of a second
OFFENSES
Offense, and should not both be reported as having happened to the Victim.
Details:
This data element is to be used to link each offense to each victim. That is, the offense which was perpetrated against the victim during the incident.
If this data element does not match one of the values submitted in Data Element # 23 (Victim Segment Number), the submission will be returned with errors.
Offenses That Cannot Occur to the Same Victim
The following chart shows Offenses that CANNOT occur to the same victim in the same incident. Each ‘X’ on the chart where offenses intersect denotes that those two offenses
CANNOT occur to the same victim in an incident.
Offenses That Cannot Occur to the Same Victim
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 Parts 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
23G - Theft of Motor Vehicle Parts
23F - Theft from Motor Vehicle
23E - Theft from Coin Machine
11C - Sexual Assault w/ Object
09B - Negligent Manslaughter
23D - Theft from Building
240 - Motor Vehicle Theft
13A - Aggravated Assault
11D - Forcible Fondling
23H - All Other Larceny
11B - Forcible Sodomy
23B - Purse Snatching
Space
23A - Pocket-Picking
36B - Statutory Rape
13B - Simple Assault
11A - Forcible Rape
13C - Intimidation
23C - Shoplifting
120 - Robbery
09A - Murder
36A - Incest
Examples:
Example
Description
Number
Two victims, Victim 001 and Victim 002, were robbed, and Victim 001 was also taken hostage by the Offender with a hand gun in a parking lot. The incident’s
Offense Segments could be submitted as follows:
Offense 001 -- Aggravated Robbery (14:64) would be connected to Victim 001.
1
Offense 002 -- Aggravated Robbery (14:64) would be connected to Victim 002.
Offense 003 -- Second Degree Kidnaping (14:44.1) would be connected to Victim 001.
Type of Victim (25)
Description: Type of Victim dicates the classification of the Victim of an Offense. The descriptors that are available for selection are based on the NIBRS Code of the Offense. All Victim
Types except for ‘S - Society’ are applicable to Crimes Against Property, while only Victim Types of ‘I - Individual’ and ‘L - Law Enforcement’ are applicable to Crimes Against Persons. On
the contrary, Crimes Against Society can only have a Victim Type of ‘S - Society’.
Data Characteristics: 1 Character Alpha. Must always be present and cannot be left blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Type of Victim (DE 25) is a required Data Element, and cannot be left
1 10001 MUST BE PRESENT–MANDATORY FIELD
blank.
No matter the number of Crimes Against Society that are present in an
Incident, there should only be a single Victim of Victim Type ‘S -
2 10080 CRIMES AGAINST SOCIETY CAN ONLY HAVE ONE VICTIM
Society’. All Crimes Against Society present in the incident should point
to this single victim.
Supplied Value not recognized. Must conform to a value on the List of
3 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
Available Data Element Values.
For Offenses that are Crimes Against Property, the associated Victim
cannot have a Type of Victim (DE 25) of ‘S - Society’. Type of Victim (DE
25) can only be:
I - Individual
B - Business
ENTRY FOR TYPE OF VICTIM CANNOT BE ‘S’ WHEN THIS OFFENSE
4 F - Financial Institution 15067
CODE IS CONNECTED TO THIS VICTIM
G - Government
R - Religious Organization
O - Other
U - Unknown
Type of Victim (DE 25) can only be ‘L - Law Enforcement Officer’ when VICTIM TYPE CANNOT BE ‘L’ = LAW ENFORCEMENT OFFICER
5 22110
the Offense Associated is 09A, 13A, 13B, or 13C. WHEN USING THIS LRS CODE
DE 31 (AGGRAVATED ASSAULT CIRCUMSTANCE) MUST BE ‘02 -
If Victim Type (DE 25) is ‘L - Law Enforcement Officer’, then Aggravated
ASSAULT ON LAW ENFORCEMENT OFFICER(S)’ IF DE 25 (VICTIM
6 Assault Circumstance (DE 31) must be ‘02 - Assault on Law Enforcement 90001
TYPE) IS ‘L’. SIMILARLY, IF DE 25 (VICTIM TYPE) IS ‘L’ FOR LAW
Officer(s)’.
ENFORCEMENT OFFICER, DE 31 MUST BE ‘02’.
Notes:
NO ERROR NUMBER For Human Trafficking Offenses (NIBRS Codes 64A, 64B and 40C), the data value for Type of Victim (25) must be Individual (‘I’).
One Type of Victim (25) code MUST be entered for each victim.
Definition of Law Enforcement Officer/Peace Officer: Deputy sheriffs, municipal police officers, probation and enforcement parole officers, wildlife enforcement agents, city
marshals and deputies would be considered a Law Enforcement Officer if a Victim and should have a Type of Victim (25) code of “L”.
The Officer should be “In-the-Line-of-Duty” when victimized in order to report Type of Victim (25) as Law Enforcement Officer (“L”). The same rules that apply to the LEOKA form
in UCR Summary also apply to this Type of Victim (25).
This Type of Victim (25) can ONLY be used for simple assaults, aggravated assaults, negligent manslaughter, murders and non-negligent homicide offenses to a Law Enforcement
Officer, that took place when the Officer was On Duty as a Law Enforcement Officer.
List of Allowed Entries for DE 25 is on the following page:
Allowed Entries:
Enter only one (1) code per Type of Victim Segment (25):
Type of Victim
I - Individual
B - Business
F - Financial Institution
G - Government
L - Law Enforcement Officer (LIBRS Only). Sent to NIBRS as “L” starting with 2.5
R - Religious Organization
S - Society/Public
O - Other
U - Unknown
Example:
Example
Description
Number
During a bank robbery (Crime Against Property), the Offender pointed a gun at a teller and demanded and received money. The robber also pistol-whipped a
customer who stood in his way as he made his getaway from the bank.
Assuming the facts above, there were 3 victims:
1
Victim 001 was the bank which would be coded as a Financial Institution ('F')
Victim 002 was the teller which would be coded as Individual ('I')
Victim 003 was the customer who was pistol whipped which would be coded as an Individual ('I')
Type of Officer Activity/Circumstance (25A)
Description: Type of Officer Activity/Circumstance is used in LEOKA Circumstances only, and it indicates the activity in which the Law Enforcement Officer was engaged at the time the
officer was either killed or assaulted in the line of duty.
Data Characteristics: 2 Character Alpha. Should only be used if Victim Type is ‘L - Law Enforcement’ and Offense is an 09A, 13A, 13B, or 13C.
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Type of Victim (25) is Law Enforcement Officer (‘L’), then Type of Officer
1 10001 MUST BE PRESENT–MANDATORY FIELD
Activity/Circumstance (25A) cannot be blank.
Supplied Value not recognized. Must conform to a value on the List of Available
2 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
Data Element Values.
Type of Officer Activity/Circumnstance (DE 25A) can only have a value if the WARNING - VICTIM TYPE MUST BE ‘L - LAW
3 15082
Victim Type (DE 25) is ‘L - Law Enforcement’ ENFORCEMENT’ FOR DATA TO BE ENTERED
Allowed Entries:
Enter only one (1) code for each Victim Segment:
Type of Officer Activity/Circumstance
01 - Responding to Disturbance Calls
02 - Burglaries in Progress or Pursuing Burglary Suspects
03 - Robberies in Progress or Pursuing Robbery Suspects
04 - Attempting Other Arrests
05 - Civil Disorder
06 - Handling, Transporting, Custody of Prisoners
07 - Investigating Suspicious Persons or Circumstance
08 - Ambush - No Warning
09 - Handling Persons with Mental Illness
10 - Traffic Pursuits and Stops
11 - All Other
Officer Assignment Type (25B)
Description: Officer Assignment Type is used to report the victim Officer’s Type of Assignment when a LEOKA Offense occurred of which they were the Victim.
Data Characteristics: 1 Character Alpha. Should only be used if Victim Type is ‘L - Law Enforcement’ and Offense is an 09A, 13A, 13B, or 13C.
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Type of Victim (25) is Law Enforcement Officer (‘L’), then Officer
1 10001 MUST BE PRESENT–MANDATORY FIELD
Assignment Type (25B) cannot be blank.
Supplied Value not recognized. Must conform to a value on the List of
2 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
Available Data Element Values.
Officer Assignment Type (DE 25B) can only have a value if the Victim Type WARNING - VICTIM TYPE MUST BE ‘L - LAW ENFORCEMENT’
3 15082
(DE 25) is ‘L - Law Enforcement’ FOR DATA TO BE ENTERED
Allowed Entries:
Enter only one (1) code for each Victim Segment:
Officer Assignment Types
F - Two-Officer Vehicle
G - One-Officer Vehicle (Alone)
H - One-Officer Vehicle (Assisted)
I - Detective or Special Assignment (Alone)
J - Detective or Special Assignment (Assisted)
K - Other (Alone)
L - Other (Assisted)
Officer ORI, Other Jurisdiction (25C)
Description: Officer ORI, Other Jurisdiction is used to report the ORI Number of a Law Enforcement Officer’s Agency when an officer from another jurisdiction is killed or assaulted in
the line of duty in the reporting Agency’s jurisdiction. No entry is required for LEOKA Offenses that occur in the Officer’s own Agency jurisdiction.
Data Characteristics: 9 Character Alpha
Requirements:
Should be a Nine-Digit, valid ORI Number, or Blank Spaces (G) if Not requried
Error
Requirement Requirement Description Error Message
Number
Officer ORI (Other Jurisdiction) (DE 25C) can only have a value if the Victim WARNING - VICTIM TYPE MUST BE ‘L - LAW ENFORCEMENT’
1 15082
Type (DE 25) is ‘L - Law Enforcement’ FOR DATA TO BE ENTERED
Details:
This is the 9-character NCIC Agency Identifier (ORI) assigned to every law enforcement agency in Louisiana. This ORI is used to record the ORI of a victim who is an officer
involved in a multijurisdictional incident.
Allowed Entries:
Enter only (1) code for each Victim Segment:
Acceptable Data Values:
A thru Z (Uppercase letter only), or 0 thru 9
Age of Victim [At Time Incident Occurred] (26)
Description: For Offenses in which a Person (I - Individual or L - Law Enforcement) are the Victim Type (DE 25), Age of Victim should be the two-digit age of the Victim when the
Incident Occurred. Ages can be appended with an ‘E’ to represent an Estimated Age of the Victim if that actual Age is not known, otherwise the third character should remain a Blank
Space. For ages that are less that one year, check the List of Available Values below.
Data Characteristics: 3 Character Alpha/Numeric. Cannot be Blank and must always have a value. Use ‘00’ if Age is Unknown.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Age of Victim (DE 26) is a required Data Element when Victim Type (DE 25) is ‘I - Individual’ or
1 ‘L- Law Enforcement’, and cannot be left blank. If Age is Unknown, then use ‘00’ to denote an 10001 MUST BE PRESENT–MANDATORY FIELD
Unknown Age, rather than leaving it blank.
If Age is not a numeric value, then it must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
Age of Victim (DE 26) is only to use the Estimated Age Modifier ‘E’ if the Age is actually being ESTIMATED AGE CANNOT BE ‘00’
3 14022
Estimated. ‘00’ for an Unknown Age is not an estimate, and therefore not a valid input. UNKNOWN AND HAVE A TRAILING ‘E’
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be VICTIM TYPE (25) MUST BE ‘I’ OR ‘L’ FOR
4 15058
entered, and should not be entered if the Victim Type (DE 25) is not. DATA TO BE ENTERED
STATUTORY RAPE OFFENSES REQUIRE A
5 Statutory Rape Victim’s Age (DE 26) must be >= 13 and <= 17. 15081 VICTIM WHO IS AT LEAST 13 YEARS OF
AGE BUT NO OLDER THAN 17 YEARS OLD
Details:
If the Type of Victim (25) is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’)), his/her age is to be entered into Age of Victim (26) either as an Exact Age, an
Estimated Age, or as Unknown.
If the Type of Victim (25) is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’)), then Age of Victim (26) is required to be entered. If Type of Victim (25) is not a
person, then Age of Victim (26) MUST be left Blank (G).
If the Victim’s Exact Age is not known, estimate the victim’s age. Use one of the codes in the above table, and append an ‘E’,for Estimated. If it is impossible to determine even an
Estimated Age of the victim, then enter Unknown (‘00’).
Allowed Entries:
Enter only (1) code for each Victim Segment:
Valid Ages of Victims
NN - Under 24 hours (Neonate)
NB - 1-6 Days Old (New Born)
BB - 7-364 Days Old (Baby)
01 to 98 - Years Old (Age in Years)
99 - Over 98 Years Old
00 - Unknown
Example:
Example Number Description
1 If the victim was 18 years old, enter ‘18’.
2 If the victim appeared 25 to 30 years old, average the age range to get 27.5, then round down and enter ‘27E’.
Date of Birth of Victim (L26)
Description: DOB of Victim is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then you shouldn’t be
using an Estimated age in Data Element 26 (Age of Victim), however we don’t stop that because it’s possible the exact Incident Date is Unknown, and instead the Reporting Date is
being used. For that reason we allow Estimated Ages to also have a Date of Birth present.
Data Characteristics: 8 Character Date. Optional, if not entered should be all Blank Spaces (Not Zeros)
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for the Date of Birth of Offender (DE L37) is not valid. Please ensure that the DATE ENTERED MUST BE A VALID
1 11005
supplied date is in the MMDDYYY Format. CALENDAR DATE
Details:
If Type of Victim (25) is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’)), then his/her date of birth, if available, is to be indicated in Date of Birth of Victim (L26).
Sex of Victim (27)
Description: Sex of Victim is used to indicate the sex of an Victim that is a Person (I - Individual or L - Law Enforcement).
Data Characteristics: 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
LIBRS VALIDATION TABLE
When the Offense Code is 11A, at least one of the Offenders must be a different sex than the Victim(s). If VICTIM’S SEX CANNOT BE
2 all Victims and Offenders are the same sex, 11B, 11C, or 11D may be the offense code you actually want 14060 SAME AS ALL OFFENDERS FOR
to use. OFFENSES OF ‘11A’
VICTIM TYPE (25) MUST BE ‘I’
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be entered, and
3 15058 OR ‘L’ FOR DATA TO BE
should not be entered if the Victim Type (DE 25) is not.
ENTERED
Details:
If Type of Victim (25) is a person [(that is, Individual (‘I’) or Law Enforcement Officer (‘L’), then his/her sex is to be indicated in Sex of Victim (27).
Allowed Entries:
Enter only (1) code for each Victim Segment:
Sex of Victim
M - Male
F - Female
U - Unknown
Race of Victim (28)
Description: Race of Victim is used to indicate the race of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar physical
characteristics. Ethinicity is defined as persons that share similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON LIBRS
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
VALIDATION TABLE
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be VICTIM TYPE (25) MUST BE ‘I’ OR ‘L’
2 15058
entered, and should not be entered if the Victim Type (DE 25) is not. FOR DATA TO BE ENTERED
Details:
If Type of Victim (25) is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’)), then, his/her race is to be indicated in Race of Victim (28).
Allowed Entries:
Enter only (1) code for each Victim Segment:
Race of Victim
W - White
B - Black
I - American Indian / Alaskan Native
A - Asian
P - Native Hawiian or Other Pacific Islander
U - Unknown
Ethnicity of Victim (29)
Description: Ethnicity of Victim is used to indicate the ethnicity of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar physical
characteristics. Ethinicity is defined as persons that share similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON LIBRS
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
VALIDATION TABLE
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be VICTIM TYPE (25) MUST BE ‘I’ OR ‘L’
2 15058
entered, and should not be entered if the Victim Type (DE 25) is not. FOR DATA TO BE ENTERED
Details:
If Victim is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’)) is entered into Type of Victim (25), then his/her ethnic origin is to be indicated in Ethnicity of Victim
(29).
Allowed Entries:
Enter only (1) code for each Victim Segment:
Ethnicity of Victim
H - Hispanic Origin
N - Not of Hispanic Origin
U - Unknown
Resident Status of Victim (30)
Description: Resident Status of Victim is used to indicate if the victim was a resident in the reporting agency’s jurisdiction at the time of the incident. It is NOT an indicator of whether
or not the Victim is a US Citizen.
Data Characteristics: 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON LIBRS
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
VALIDATION TABLE
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be VICTIM TYPE (25) MUST BE ‘I’ OR ‘L’
2 15058
entered, and should not be entered if the Victim Type (DE 25) is not. FOR DATA TO BE ENTERED
Details:
If Type of Victim (25) is a person (that is, Individual (‘I’) or Law Enforcement Officer (‘L’), then, whether he/she was a resident or nonresident, the Resident Status of Victim (30) is
to be entered.)
A ‘Resident’ is a person who maintains his/her permanent home for legal purposes in the locality (i.e., town, city, or community) where the crime took place.
Allowed Entries:
Enter only (1) code for each Victim Segment:
Resident Status of Victim
R - Resident
N - Nonresident
U - Unknown
Aggravated Assault/Homicide Circumstance Nos. 1 and 2 (31)
Description: Aggravated Assault/Homicide Circumstances is used to describe the circumstances of either an aggravated assault or a homicide. It’s must be used with NIBRS 09A, 09B,
09C, and 13A, and should not be used with any other Offense (left Blank). Additionally the availablility of the codes DE 31 uses is subject the Victim Type (DE 25) and NIBRS Code of the
Offense; not all codes are available for all conditions.
Data Characteristics: Up to 2x, 2 Character Numeric. You may enter 2 Codes for Victims associated with NIBRS 13A and 09A Offenses, and one code for Victims associated with NIBRS
09B and 09C Offenses. Exceeding this limit for Victims associated with 09B and 09C Offenses will throw an error, rather than ignoring the value.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the
1 11004 INVALID DATA VALUE–NOT ON LIBRS VALIDATION TABLE
List of Available Data Element Values.
When more than one code is entered within Aggravated
2 Assault/Murder category, the same value is not allowed to be 12006 ERROR - DUPLICATE VALUE
repeated.
Aggravated Assault/Homicide Circumstance (DE 31) is only
allowed to be present if Offense Connected to Victim Sequence
Number (DE 24) relates to one of the follwing Offense Codes:
3 15019 DATA CAN ONLY BE ENTERED FOR SPECIFIC OFFENSES
13A
09A, 09B or 09C
Aggravated Assault/Homicide Circumstance (DE 31) must be
present if Offense Connected to Victim Sequence Number (DE
24) relates to one of the follwing Offense Codes:
4 15020 DATA MUST BE ENTERED FOR SPECIFIC OFFENSES
13A
09A, 09B or 09C
Unknown Circumstances (‘10’) is mutually exclusive with all
5 other codes, that is, no other code can be entered. Enter 15056 ONLY ONE VALUE GREATER OR EQUAL TO ‘10’ CAN BE ENTERED
Unknown (‘10’) ONLY if no other code applies.
When Assault/Homicide Circumstances (DE 31) is ‘08 - Other
WHEN HOMICIDE/ASSAULT CIRCUMSTANCE (DE 31) IS ‘08’, INCIDENT
6 Felony Involved’, then the Incident must contain two or more 15080
MUST HAVE 2 OR MORE OFFENSES
Offenses.
DE 31 (AGGRAVATED ASSAULT CIRCUMSTANCE) MUST BE ‘02 - ASSAULT
If Victim Type (DE 25) is ‘L - Law Enforcement Officer’, then
ON LAW ENFORCEMENT OFFICER(S)’ IF DE 25 (VICTIM TYPE) IS ‘L’.
7 Aggravated Assault Circumstance (DE 31) must be ‘02 - Assault 90001
SIMILARLY, IF DE 25 (VICTIM TYPE) IS ‘L’ FOR LAW ENFORCEMENT
on Law Enforcement Officer(s)’.
OFFICER, DE 31 MUST BE ‘02’.
For 09B and 09C Offenses, only one Aggravated
8 90004 ONLY ONE CODE ARE ALLOWED IN DE 31
Assault/Homicide Circumstance can be used.
Aggravated Assault and Non-Negligent Manslaughter Circumstances
Error
Requirement Requirement Description Error Message
Number
The chosen Aggravated Assault/Homicide Circumstance that was used for this Offense is
9 not valid for the NIBRS Code. Please refer to the List of Available Data Element Values to 90005 INVALID DE 31 CODE FOR THIS OFFENSE.
find an appropriate selection to use.
WARNING: FOR DE 31, AT MOST TWO ASSAULT
The third Aggravated Assault/Homicide Circumstance has been deprecated and will not
10 90014 CIRCUMSTANCE ARE ALLOWED. THE 3RD
be included in your submission.
ASSAULT CIRCUMSTANCE WILL BE IGNORED.
Negligent Manslaughter Circumstances
Error
Requirement Requirement Description Error Message
Number
If Non-Negligent Circumstances (DE 31) is Child Abuse (‘40’), then the Victim that is
Connected to this Offense must have an age that equals
AGE DOES NOT INDICATE CHILD IS THE VICTIM
11 NN, NB, BB 22120
CONNECTED TO THIS OFFENSE
01-16, or 01-16 with a trailing 'E'
Justifiable Homicide Circumstances
Error
Requirement Requirement Description Error Message
Number
When Justifiable Homicide (NIBRS 09C) is reported, no other offense may NO OTHER OFFENSE CAN BE SUBMITTED WITH AN 09C
12 12066
be reported in the Incident Report. (JUSTIFIABLE HOMICIDE) OFFENSE
Details:
DEFINITION: A Justifiable Homicide is the killing of a perpetrator of a serious criminal offense by a peace officer in the line of duty; or the killing, during the commission of a
serious criminal offense, of the perpetrator by a private individual.
At MOST, TWO Assault Circumstances (31) are allowed. Beginning with LIBRS 2.5 Specifications, the third Assault Circumstance is ignored. New Warning Message in LIBRS 2.5
Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (InLine of Duty (31) describes the circumstances of either an Aggravated Assault or
Homicide.
Assault on Law Enforcement Officer is a new Aggravated Assault and Non-Negligent Manslaughter Circumstance,beginning with LIBRS Spec 2.5.
The crime being committed when the Justifiable Homicide took place MUST BE REPORTED AS A SEPARATE INCIDENT. These instructions are based on the definition of an
“incident”. Therefore, Justifiable Homicide cases involve two incidents rather than one.
For the Justifiable Homicide incident, code the police officer or the civilian who killed the criminal as the “Offender” and the criminal who was killed as the “Victim”.
The Justifiable Homicide incident IS NOT CLEARED EXCEPTIONALLY, as no crime has occurred in reality.
In the second incident, report the Offense(s) that were being committed when the Justifiable Homicide occurred.
Allowed Entries:
Aggravated Assault/Homicide Circumstances
Aggravated Assault and Non-Negligent Manslaughter Circumstances
01 - Argument 13A, 09A
02 - Assault on Law enforcement Officer(s) 13A, 09A (Must be entered if Victim Type = 'L')
03 - Drug Dealing 13A, 09A
04 - Gangland 13A, 09A
05 - Juvenile Gang 13A, 09A
06 - Domestic Violence 13A, 09A
07 - Mercy Killing (Not applicable to aggravated assault) 09A
08 - Other Felony Involved 13A, 09A
09 - Other Circumstances 13A, 09A
10 - Unknown Circumstances 13A, 09A
40 - Child Abuse (LIBRS Only) to NIBRS as code '09' 13A, 09A
Negligent Manslaughter Circumstances
30 - Child Playing with Weapon 09B
31 - Gun-Cleaning Accident 09B
32 - Hunting Accident 09B
33 - Other Negligent Weapon Handling 09B
34 - Other Negligent Killing 09B
40 - Child Abuse (LIBRS Only) to NIBRS as code '09' 09B
Justifiable Homicide Circumstances
20 - Criminal Killed by Private Citizen 09C
21 - Criminal Killed by Police Office 09C
Examples:
Example
Description
Number
Two rival juvenile street gangs rumble over ‘turf’ rights to sell drugs and one of the gang members is killed. Possible entries are:
01 - Argument
03 - Drug Dealing
1 05 - Juvenile Gang
While all three would apply, there is a limit of two entries. Therefore, the two most descriptive codes (as determined by the reporting agency) should be used. In
this case, the reporting agency entered ‘03’ and ‘05’.
Additional Justifiable Homicide Circumstance (32)
Description: Additional Justifiable Homicide Circumstances is used to describe the circumstances of a NIBRS 09C Offenses (Justifiable Homicide) only. It is not to be used with Victims
of any Offense Code other than 09C. When more than one data value applies, enter the one that is most descriptive.
Data Characteristics: 1 Character Alpha
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
LIBRS VALIDATION TABLE
ADDITIONAL JUSTIFIABLE
For any 09C Offense, Additional Justifiable Homicide Circumstance (DE 32) is required to be either ‘20
2 15055 HOMICIDE IS MANDATORY WITH A
- Criminal Killed by Private Citizen’, or ‘21 - Criminal Killed by Police Officer
‘20’ OR ‘21’ ENTERED
When this Data Element (32) is entered and Type of Victim (25) is Individual (‘I’), Aggravated
Assault/Homicide Circumstance (31) MUST show one of the following Justifiable Homicide (09C)
WHEN DATA ELEMENT 32 IS
Circumstances:
3 15057 ENTERED, DATA ELEMENT 31 MUST
20 Criminal Killed by Private Citizen
EQUAL ‘20’ OR ‘21’
21 Criminal Killed by Police Officer
Allowed Entries for Justifiable Homicide:
Enter only (1) code for Justifiable Homicide (NIBRS 09C):
Justifiable Homicide Circumstance
A - Criminal Attacked Police Officer and That Officer Killed Criminal
B - Criminal Attacked Police Officer and Criminal Killed by Another Police Officer
C - Criminal Attacked by Civilian
D - Criminal Attempted Flight from a Crime
E - Criminal Killed in the Commission of a Crime
F - Criminal Resisted Arrest
G - Unable to Determine / Not Enough Information
Examples:
Example
Description
Number
In resisting arrest, a fugitive pulled a gun and fired two times in the direction of two police officers who were attempting to take him into custody. Neither officer
was hit, but both drew their weapons and returned fire, killing the fugitive. As this was a Justifiable Homicide (NIBRS 09C), Criminal Killed by Police Officer (‘21’)
should be entered into Data Element 31.
Assuming the facts above, the possible entries for Data Element 32 are:
1 A - Criminal Attacked Police Officer and That Officer Killed Criminal
B - Criminal Attacked Police Officer and Criminal Killed by Another Police Officer
F - Criminal Resisted Arrest
As only one code can be entered into this Data Element (32), the most descriptive code (as determined by the reporting agency) should be used. In this case, the
reporting agency entered Criminal Attached Police Officer and That Officer Killed Criminal(‘A’).
Type of Injury (33)
Description: Type of Injury is used to describe the condition of a Victims of a Crime Against Person after the Offense has been committed. Certain Injury Types are not applicable for
certain NIBRS Codes.
Data Characteristics: 1 Character Alpha. Must be included for each Victim Injury Segment (Segment 51) that is present in the Incident, and cannot be left Blank.
Requirements:
Error
Requirment Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON
1 Supplied Value not recognized. Must conform to a value on the List of Available Data Element Values. 11004
LIBRS VALIDATION TABLE
Victim Injury Type (DE 33) is only allowed to be present if the associated Victim Type (DE 25) is ‘I - Individual’
or ‘L - Law Enforcement’, and Offense Connected to Victim Sequence Number (DE 24) relates to one of the
follwing Offense Codes:
100, 120
11A, 11B, 11C, 11D DATA CAN ONLY BE ENTERED
2 15019
210 FOR SPECIFIC OFFENSES
13A, 13B
64A, 64B
90Z
Victim Injury Type (DE 33) must be present if the associated Victim Type (DE 25) is ‘I - Individual’ or ‘L - Law
Enforcement’, and Offense Connected to Victim Sequence Number (DE 24) relates to one of the follwing
Offense Codes:
100, 120
11A, 11B, 11C, 11D DATA MUST BE ENTERED FOR
3 15020
210 SPECIFIC OFFENSES
13A, 13B
64A, 64B
90Z
When Offense Connected to Victim Sequence Number (DE 24) relates to a NIBRS 13B Offense (Simple SIMPLE ASSAULT (13B)
4 Assault), any Injury Types other than ‘M - Apparent Minor Injury’ and ‘N - None’ are not permitted. Use 15079 CANNOT HAVE ‘MAJOR
NIBRS 13A (Aggravated Assault) if Injury Type is more severe. INJURIES’
Type of the Injury cannot be ‘M - Apparent Minor Injury’ or ‘N - None’ When:
INVALID TYPE OF INJURY (DE
The Offense Connected to Victim Sequence Number (DE 24) is a NIBRS 13A
33) WITH SELECTED TYPE OF
5 AND 90029
WEAPON/FORCE INVOLVED
The Type of Weapon/Force Involved = '40 - Personal Weapon'
(DE 13)
Important Note:
13A, 13B, and 13C Offenses are all Mutually Exclusive to the same Victim in the same Incident. Meaning, LIBRS (and NIBRS, for that matter) will not allow you to submit a Victim who
received Major Injuries from one Offender committing a 13A - Aggravated Assault Offenses, and Minor Injuries from another Offender committing a 13B - Simple Assault Offense.
If you have a case where a Victim applies to Mutually Exclusive Offenses, then you will need to submit those Offenses in Separate Incidents. You can see the chart here for which
Offenses are Mutually Exclusive.
Details:
Notes: This Data Element (32) describes the type(s) of bodily injury suffered by a person.
Minor injury is described as an injury not requiring immediate medical attention.
Major injury is described as an injury requiring immediate medical attention.
Allowed Entries:
Enter only (1) code for each Victim Injury Segment; however, can submit as many Victim Injury Segments (51) as applicable:
Type of Injury
N - None
B - Apparent Broken Bones
I - Possible Internal Injury
L - Severe Laceration
M - Apparent Minor Injury
O - Other Major Injury
T - Loss of Teeth
U - Unconsciousness
Offender Number to be Related (34)
Description: Offender Number to Be Related is only used in Segment 52, Victim/Offender Relationship, which should only be present with the Victim is associated with a Crime Against
Person, or a Robbery.
Data Characteristics: 3 Character Numeric. Should always be supplied in Segment 52 (when that segment is present). Value should be front-padded with Zeros (0) to make a three-
digit number. EG: 1 would be 001.
Requirements:
Error
Requirment Requirement Description Error Message
Number
Offender Number to be Related (DE 34) must match one of the Offender Sequence Numbers (DE THE CORRESPONDING OFFENDER
1 10070
36) present in the Offender Segment(s) (Segment 40). RECORD MUST BE PRESENT
Type of Victim (DE 25) must be ‘I - Individual’ or ‘L - Law Enforcement’ in order for data to be VICTIM TYPE (25) MUST BE ‘I’ OR ‘L’ FOR
2 15058
entered, and should not be entered if the Victim Type (DE 25) is not. DATA TO BE ENTERED
In order for Offender Number to be Related to have a value, the offense must either be a
Robbery (NIBRS 120), or a Crime Against Person:
09A, 09B, 09C
100, 120
11A, 11B, 11C, 11D
NEED A CRIME AGAINST PERSON OR
3 13A, 13B, 13C 15059
ROBBERY FOR DATA TO BE ENTERED
36A, 36B
90Z (If a Crime Against Person)
Additionally this value should be supplied when the NIBRS Code Associated with it is a 64A, 64B,
or 40C.
Details:
If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are known, then data value for Offender Number to be Related (Data Element 34) MUST be supplied
as well.
If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are unknown, then data value for Offender Number to be Related (Data Element 34) MUST be ‘000’
(UNKNOWN)
Notes: Offender Number to be Related (34) along with Relationship of Victim to Offender (35) describe the relationship of each Victim to each Offender who has perpetrated a
Crime Against Person or a Robbery against the Victim. If the Victim is related to the offender in more than one way, use the closest relationship.
Enter Offender Sequence Number (36) of the Offenders for whom Victim-to-Offender relationships are going to be reported in Relationship of Victim to Offender (35).
The Reporting Agency MUST report each Victim’s relationship to EVERY Offender when the Offense is a Crime Against Person or a Robbery against the Victim.
Examples:
Example Number Description
1 If Victim 001’s relationship to Offender 004 is to be reported, enter ‘004’.
Relationship of Victim to Offender (35)
Description Victim/Offender Relationship describes how the Victim and the Offender of an Offense are associated with one another, if at all. It is common for this Data Element to be
used for statistics for Offenses like Domestic Violence. If should only be used when the Victim is associated with a Crime Against a Person.
Data Characteristics: 2 Character Alpha. Should only have a value if the Victim is associated with a Crime Against a Person.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the List of Available Data Element INVALID DATA VALUE–NOT ON LIBRS
1 11004
Values. VALIDATION TABLE
The Victim/Offender Relationship of ‘SE - Spouse’ was used, however the age of either the Victim or OFFENDER IS SPOUSE, BUT AGE IS
2 14050
the Offender was less than 10. This is not a valid age based on the relationship between the two. LESS THAN 10
SEX OF VICTIM AND OFFENDER
If Victim/Offender Relationship (DE 35) is ‘VO - Victim was Offender’, then Sex of Victim (DE 27) and
3 14053 DOES NOT REFLECT THE
Sex of Offender (DE 38) should match.
RELATIONSHIP
The Age of Victim and Age of Offender must reflect the implied relationship. The following
relationships imply that the Age of Victim (DE 26) that is Younger than the Age of Offender (DE 37):
CH - Victim was Child
GC - Victim was Grandchild
BE - Victim was Babysitee (the Baby)
The following relationships imply that the Age of Victim (DE 26) that is Older than the Age of
Offender (DE 37):
PA - Victim was Parent
GP - Victim was Grandparent
AGE OF VICTIM AND OFFENDER
4 The following Implied Age Difference Between Victims and Offenders where victim must be Same 14054 DOES NOT REFLECT THE
Age: RELATIONSHIP
VO - Victim was Offender
The following Implied Age Difference Between Victims and Offenders where victim must be At Least
10 Yrs Old:
SE - Victim was Spouse
ES - Victim was Estranged Spouse
CS - Victim was Common-Law Spouse
XS - Victim was Ex-Spouse
NM - Victim was Non-Married Live-In
Victim/Offender Relationship (DE 34) must be present for each Victim Sequence Number (DE 23) that MISSING VICTIM/OFFENDER
5 has a Victim Type (DE 25) of ‘I - Individual’ or ‘L - Law Enforcement’ that is a victim of a Crime 15005 SEGMENT OR RELATIONSHIP
Against Person or a Robbery. (SEGMENT 52 OR DE L6)
Victim/Offender Relationship (DE 34) must be present for any Victim of a Crime Against Person
09A, 09B
100 DATA MUST BE ENTERED FOR
6 15020
11A, 11B, 11C, 11D SPECIFIC OFFENSES
13A, 13B, 13C
If Victim/Offender Relationship (DE 35) is one of the following, then Offender Number to be Related
(DE 34) cannot be Unknown (‘000’). This field must be Blank (G) in instances where ‘000’ is entered.
OF - Victim Was Other Family Member
CS - Victim Was Common-Law Spouse
SB - Victim Was Sibling
SP - Victim Was Stepparent
SC - Victim Was Stepchild
SS - Victim Was Step-Sibling
IL - Victim Was In-Law RELATIONSHIP MUST BE ENTERED
7 CF - Victim Was Child of Boyfriend or Girlfriend 15060 WHEN AN OFFENDER NUMBER (34)
NE - Victim Was Neighbor EXISTS
FR - Victim Was Friend
AQ - Victim Was Acquaintance
EE - Victim Was Employee
ER - Victim Was Employer
OK - Victim Was Otherwise Known
RU - Relationship Unknown
ST - Victim Was Stranger
RELATIONSHIP CANNOT BE ENTERED
If Offender Number to be Related (DE 34) is ‘000 - Unknown’, then Victim/Offender Relationship
8 15068 WHEN RELATED TO OFFENDER
cannot have a value, and should be blank spaces.
NUMBER ‘000’
Error
Requirement Requirement Description Error Message
Number
WHEN OFFENDER AGE / SEX / RACE
When the attributes of an Offender (Age, Sex, and Race - DE’s 37, 38, and 39) are all Unknown, then
9 15072 ARE UNKNOWN, RELATIONSHIP
the Victim/Offender Relationship (DE 35) has to be ‘RU - Relationship Unknown’.
MUST BE ‘RU’ = UNKNOWN
A Victim cannot have multiple Victim/Offender Relationships (DE 35) of ‘SE - Spouse’ with more than ONLY ONE ‘SE’ RELATIONSHP PER
10 15075
one Offender. VICTIM
Details:
Notes: If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are known, then data value for Relationship of Victim to Offender (Data Element 34) MUST be
supplied as well.
Relationship of Victim to Offender (35) is used ONLY with Offender Number to be Related (34), to report the relationship of a Victim to Offenders who have perpetrated a Crime
Against Person, or a Robbery against the Victim.
Relationship of Victim to Offender (35) indicates the Victim’s relationship with each Offender involved in the incident.
Relationship of Victim to Offender (35) is NOT required if Type of Victim (25) is equal to Society/Public (‘S’). ___
List of Allowed Entries for DE 35 is on the following page:
Allowed Entries:
MUST enter ONE code for each Victim Segment (50). MUST enter relationship of each Victim to each Offender when Offense is a Crime Against Person or a Robbery against a Victim:
Relationships of Victims to Offenders
Within Family
SE - Victim Was Spouse
CS - Victim Was Common-Law Spouse
PA - Victim Was Parent
SB - Victim Was Sibling
CH - Victim Was Child
GP - Victim Was Grandparent
GC - Victim Was Grandchild
IL - Victim Was In-Law
SP - Victim Was Stepparent
SC - Victim Was Stepchild
SS - Victim Was Step-Sibling (stepbrother or stepsister)
OF - Victim Was Other Family Member
NM - Non-Married Live-in (LIBRS Only) Sent to NIBRS as 'CS'
Outside Family, But Known to Victim
VO - Victim Was Offender
AQ - Victim Was Acquaintance
FR - Victim Was Friend
NE - Victim Was Neighbor
BE - Victim Was Babysittee (the baby)
BG - Victim Was Boyfriend/Girlfriend
XB - Victim Was Ex-Boyfriend/Girlfriend (LIBRS Only). Now Maps to 'XR'; Sent to NIBRS as 'BG'
CF - Victim Was Child of Boyfriend or Girlfriend
HR - Homosexual Relationship *no longer used*
XS - Victim Was Ex-Spouse
EE - Victim Was Employee
ER - Victim Was Employer
OK - Victim Was Otherwise Known
ES - Victim Was Estranged Spouse (LIBRS Only) Sent to NIBRS as 'SE'
XR - Victim was from an Ex Relationship
Not Know By Victim
RU - Relationship Unknown
ST - Victim Was Stranger
Other
VO - Victim Was Offender
Examples:
Example
Description
Number
1 An employee assaulted his employer (a person) with his fists. Victim was Employer (ER) should be entered.
Two unknown subjects rob a male and a female couple. Victim was Stranger (‘ST’) should be entered to indicate the relationship of each Victim to each
2
Offender.
Offender Sequence Number (36)
Description: Offender Sequence Number is the unique identifier for each Offender that is present in an Incident. Each Offender Segment (Segment 40) should have a unique value to
identify them. Values for Offenders that aren’t unknown should be between 001 and 999. If an Offender is unknown, then there should be a single Segment 40 with an Offender
Sequence Number of ‘000’.
An Unknown Offender Sequence Number ‘000’ is different than an Unknown Age, Race, or Sex (‘00’ for Age, or ‘U’ for Race and Sex) of an Offender. Take the following examples:
1. A vehicle is stolen, and there are no witnesses or camera footage of the crime.
2. A crime that was caught on camera, but the resolution wasn’t good enough to make out any identifying features of the Suspects.
Case 1 would be a case where you use ‘000’ for an Offender Sequence Number. When ‘000’ is used as the Offender Sequence Number, it basically means “We have no idea who, or even
how many people were involved in this crime”. Because of that, there are two circumstances that should be accounted for with it:
1. If ‘000’ is used as an Offender Sequence Number, then no other Offender Sequence Numbers can be entered. You either have an idea of how many people were invovled, or you
don’t. If you know something about any of the Offenders, or even just how many Offenders were involved, ‘000’ should not be used.
2. ‘000’ is not allowed for 09C Offenses because inherently you need to know who was involved in that Offense to deem it a Justifiable Homicide; if you don’t know who was
involved, then what evidence do you have that the homicide was justifiable?
Case 2 is a case where ‘000’ Offender Sequence Number shouldn’t be confused for not knowing anything about the attributes (Age, Sex, and Race) of the Offenders involved. In this
case you may not be able to describe anything about the Offenders, but you have clear-cut evidence about the number of Offenders that were involved. Therefore you should use
Offender Sequence Numbers other than ‘000’ for them.
Just to note, you will get a Warning about those attributes being Unknown, but that’s only there to warn the User in case that data was mistakenly forgotten, which is the most common
occurance when all of those Data Elements are Unknown.
Data Characteristics: 3 Character Numeric. Should never be left blank and should be front-padded to make a three-digit number. EG: 1 would be 001. If unknown use ‘000’ - If ‘000’ is
used then no other Offender Segments can be present.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Offender Sequence Number (DE 36) cannot be blank, and must be front-padded with zeros to make a MUST BE PRESENT–MANDATORY
1 10001
3-digit number. (EG ‘001’, ‘002’, ‘011’, etc…) FIELD
Offender Sequence Number (DE 36) cannot be repeated across multiple Segment 40’s (Offender
2 12006 ERROR - DUPLICATE VALUE
Segment) in an Incident.
Using Offender Sequence Number (DE 36) ‘000’ implies that nothing is known about the Offender(s), OFFENDER ‘000’ EXISTS–CANNOT
4 14055
and therefore only one Offender Segment can be used whenever this value is present. SUBMIT MORE OFFENDERS
If an incident is Exceptionally Cleared (DE 4), then Offender Sequence Number (DE 36) cannot be
Unknown ‘000’. OFFENDER SEQUENCE NUMBER
CANNOT BE UNKNOWN IF
5 14057
Unknown (‘000’) indicates that nothing is known about the Offender(s) regarding number and any INCIDENT CLEARED
identifying information. One of the criteria for Exceptionally Clearing (DE 4) an incident is that at least EXCEPTIONALLY
one of the Offenders be known.
For NIBRS 09C Offenses (Justifiable Homicide) at least one of the Offenders must have known OFFENDER DATA MUST BE
6 information for Age, Sex, and Race. Unknown (‘000’) is not valid as an Offender Sequence Number (DE 14059 PRESENT IF OFFENSE CODE IS
36) for these Offenses. JUSTIFIABLE HOMICIDE/09C
Details:
Notes: Each Offender in an incident is assigned a UNIQUE Offender Sequence Number (36) from ‘001’ to ‘999’.
If nothing is known about the Offender(s), enter ‘000’ into this data element and LEAVE DATA ELEMENTS 37 THROUGH 39 BLANK (G). Also, Offender Suspected of Using (8)
MUST be Not Applicable (‘N’) and Bias Motivation/Bias Crime Type (8A) MUST be None (‘88’).
Examples:
Example
Description
Number
A corpse with five bullet holes in it was found in an abandoned warehouse. There were no witnesses to the crime, or suspects.
A single Offender Segment (40) should be submitted with '000' entered into Offender Sequence Number (36) and with no entries in Data Elements
1 37 through 39.
Offender Suspected of Using (8) must be Not Applicable ('N') and Bias Motivation/Bias Crime Type (8A) must be None '88'
Two Offenders were seen fleeing the scene of a burglary, but because they were wearing ski masks, their Age, Sex, and Race could not be determined.
Two Offender Segments (40) should be submitted: the first with Offender Sequence Number '001' and the second with '002'.
2 Applicable Unknown codes should be entered into Data Elements 37, 38 and 39.
Offender Suspected of Using (8) MUST be Not Applicable ('N') and Bias Motivation/Bias Crime Type (8A) MUST be None ('88')
Age of Offender [At Time of Incident] (37)
Description: Age of Offender is the age the Offender was on the Date of the Incident. Ages can be appended with an ‘E’ to represent an Estimated Age of the Offender if that actual
Age is not known, otherwise the third character should remain a Blank Space.
Data Characteristics: 3 Digits Alpha/Numeric. Cannot be Blank and must always have a value. Use ‘00’ if Age is Unknown.
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 If Offender Sequence Number (36) is other than Unknown (‘000’), Age of Offender (DE 37) cannot be blank. 10001
MANDATORY FIELD
EXACT AGE MUST BE
For Exact Ages the first two characters in Age of Offender (DE 37) need to be a two digit number (front-padded with
2 14008 IN FIRST TWO
a zero if less than 10 - EG: 07, 09), with the third character as a Blank Space (G).
POSITIONS
ESTIMATED AGE
For Estimated Ages the first two characters in Age of Offender (DE 37) need to be a two digit number (front-padded MUST BE 2 NUMERIC
3 14009
with a zero if less than 10 - EG: 07, 09), with the third character as an ‘E’ to represent the estimation. DIGITS, AND HAVE A
TRAILING ‘E’
ESTIMATED AGE
Age of Offender (DE 37) is only to use the Estimated Age Modifier ‘E’ if the Age is actually being Estimated. ‘00’ for CANNOT BE ‘00’
4 14022
an Unknown Age is not an estimate, and therefore not a valid input. UNKNOWN AND
HAVE A TRAILING ‘E’
CANNOT BE PRESENT
When Offender Sequence Number (DE 36) is ‘000’ to denote an Unknown Offender, then Age of Offender (DE 37)
WHEN OFFENDER
5 cannot have a known value. In order for a value to be reported for this Data Element, the Offender Sequence 14052
NUMBER IS ‘000’
Number (DE 36) should be something other than ‘000’
UNKNOWN
Details:
Age of the Offender (37) is entered either as an exact number of years, an estimated age or as unknown.
If the Offender’s Age is NOT KNOWN, estimate the Offender’s Age and append an ‘E’ (Estimated).
If a range is given for the Offender’s Age, enter the median (average) age of the range (rounded down).
If it is impossible to determine even an Estimated Age of the Offender, then enter Unknown (‘00’).
Allowed Entries
Enter only one code per Offender Segment (40):
Age of Offender
01-98 - Age in years
99 - Over 98 Years Old
00 - Unknown
Examples:
Example
Description
Number
If the Victim, or a witness, reported the Offender’s Age as between 25 and 30 years old, enter ‘27E’ (the average of 25 and 30 is 27.5, round down to get an
1
estimated age of 27).
Date of Birth of Offender (L37)
Description: DOB of Offender is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then you shouldn’t
be using an Estimated age in Data Element 37 (Age of Offender), however we don’t stop that because it’s possible the exact Incident Date is Unknown, and instead the Reporting Date is
being used. For that reason we allow Estimated Ages to also have a Date of Birth present.
Data Characteristics: 8 Character Date. Optional, if not entered should be all Blank Spaces (Not Zeros)
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for the Date of Birth of Offender (DE L37) is not valid. Please ensure that the DATE ENTERED MUST BE A VALID
1 11005
supplied date is in the MMDDYYY Format. CALENDAR DATE
Details:
If the Date of Birth of the Offender is known, it is to be indicated in this data element.
Sex of Offender (38)
Description: The Sex of an Offender involved in the Incident.
Data Characteristics: 1 Character Alpha. Must always have a value; use U if Unknown or Offender Sequence Number is ‘000’, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 If Offender Sequence Number (36) is other than Unknown (‘000’), Sex of Offender (DE 38) cannot be blank. 10001
MANDATORY FIELD
INVALID DATA VALUE–
2 Must be a valid code that is found on the List of Available Data Element Values. 11004 NOT ON LIBRS
VALIDATION TABLE
CANNOT BE PRESENT
When Offender Sequence Number (DE 36) is ‘000’ to denote an Unknown Offender, then Sex of Offender (DE 38)
WHEN OFFENDER
3 cannot have a known value. In order for a value to be reported for this Data Element, the Offender Sequence 14052
NUMBER IS ‘000’
Number (DE 36) should be something other than ‘000’
UNKNOWN
VICTIM’S SEX CANNOT
When the Offense Code is 11A, at least one of the Offenders must be a different sex than the Victim(s). If all BE SAME AS ALL
3 14060
Victims and Offenders are the same sex, 11B, 11C, or 11D may be the offense code you actually want to use. OFFENDERS FOR
OFFENSES OF ‘11A’
Details:
This Data Element (38) indicates Sex of the Offender.
Allowed Entries:
Enter only (1) code per Offender Segment (40):
Sex of Offender
M - Male
F - Female
U - Unknown
Examples:
Example Number Description
1 The witness caught only a fleeting glance of the Offender and, therefore, was unable to report the Offender’s Sex. The entry should be Unknown (‘U’).
Race of Offender (39)
Description: Race of Offender is used to indicate the race of an Offender involved in an Incident. Race is defined as persons that share similar physical characteristics. Ethinicity is
defined as persons that share similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Must always have a value; use U if Unknown or Offender Sequence Number is ‘000’, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 If Offender Sequence Number (36) is other than Unknown (‘000’), Race of Offender (DE 39) cannot be blank. 10001
MANDATORY FIELD
INVALID DATA
VALUE–NOT ON
2 Must be a valid code that is found on the List of Available Data Element Values. 11004
LIBRS VALIDATION
TABLE
CANNOT BE
When Offender Sequence Number (DE 36) is ‘000’ to denote an Unknown Offender, then Race of Offender (DE 39)
PRESENT WHEN
3 cannot have a known value. In order for a value to be reported for this Data Element, the Offender Sequence 14052
OFFENDER NUMBER
Number (DE 36) should be something other than ‘000’
IS ‘000’ UNKNOWN
Details:
Race of an Offender is indicated in this Data Element (39).
Allowed Entries:
Enter only (1) code per Offender Segment (40):
Race of Offender
W - White
B - Black
I - American Indian / Alaskan Native
A - Asian/Pacific Islander
U - Unknown
Ethnicity of Offender (39A)
Description: Ethnicity of Offender is used to indicate the ethnicity of an Offender involved in an Incident. Race is defined as persons that share similar physical characteristics. Ethinicity
is defined as persons that share similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Must always have a value; use U if Unknown or Offender Sequence Number is ‘000’, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
If entered, must conform to a value on the List of Available Data Element INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
Values. TABLE
Details:
This Data Element indicates the ethnic origin of the Arrestee.
Allowed Entries
Enter only (1) code per Offense Segment (40):
Ethnicity of Arrestee
Ethnicity of Arrestee
H - Hispanic Origin
N - Not of Hispanic Origin
U - Unknown
Arrestee Sequence Number (40)
Description: The Arrestee Sequence Number is a Uniquely Identifying Value between 001 and 999 that is used throughout the LIBRS Data Segments to identify which particular
Arrestee is being referenced for validation purposes. Each Arrestee Segment (Segment 60) in an Incident should contain a unique Sequence Number. There is no Unknown Value for this
Sequence Number like there is for Offender Sequence Number.
Data Characteristics: 3 Character Numeric. Must be front-padded with Zeros to make a three-digit number. EG: 1 would be 001.
Requirements:
Requirement Requirement Description Error Number Error Message
1 The Arrestee Sequence Number (DE 40) needs to be unique across the Incident. 16061 DUPLICATE ARRESTEE SEGMENT
Details:
Each Arrestee reported is assigned a UNIQUE Sequence Number from ‘001’ to ‘999’.
Examples:
Example
Description
Number
If two persons were arrested in connection with a previously submitted incident, two Arrestee Segments should be submitted: one with Arrestee Sequence
1
Number ‘001’ and the other with ‘002’.
Arrestee Name (L40)
Description: Arrestee Name is the name of the individual being Arrested in connection with one of the Offenses present in the Incident. This field is purely optional, we do literally no
validation on it and it doesn’t go to the FBI for NIBRS Reporting.
Data Characteristics: 20 Character Alpha
Format: [Last Name][Suffix],[First Name][Middle Name]
Suffix includes standard suffixes used to distinguish between generations (for example, Sr, Jr, III, II). Do not include titles (for example, MD, M.E., Ph.D., Esq., etc.)
Requirements:
None
Details:
If Arrestee’s full name will not fit in the field, then enter as much as possible. DO NOT put periods behind suffix abbreviations or middle initial.
Arrest Number/Local Booking Number for Arrest (41)
Description: Arrest Number/Local Booking Number for Arrest is the unique identifier that the Agency has for the particular Arrest Record in their RMS. This is actually quite an
important Data Element, as when we submit changes to NIBRS to arrests this is the value that is used to make modifications.
Data Characteristics: 12 Character Alpha. Cannot be completely blank, and must be unique for every Arrestee across all Incidents (IE: Number cannot be the same in two different
Incidents). Cannot contain spaces in between any of the characters in this data element, but leading or trailing spaces are fine.
Requirements:
Error
Requirement Requirement Description Error Message
Number
1 When more than one value is present, the same value is not allowed to be repeated. 12006 ERROR - DUPLICATE VALUE
Arrest Number/Local Booking Number for Arrest (DE 41) should not contain any blank spaces CANNOT HAVE EMBEDDED ‘BLANKS’
2 between the first and last characters that aren’t spaces. EG: ‘123456789 10’ is not allowed, but 16015 BETWEEN FIRST AND LAST NON -
‘12345678910 ‘ is fine. BLANK CHARACTERS
Details:
This Data Element (41) is a UNIQUE, IDENTIFYING number assigned by an agency to an Arrest Report. It may be the Incident Number of a reported incident relating to the Arrest,
or it may be a separate Booking Number.
Arrest Date (42)
Description: Arrest Date is the actual date that an Arrestee was brought into the LEA’s custody. Since Incident Dates and Arrest Dates can be different, if there is a case where an Arrest
is made for an Incident that occurred before the Agency’s Base Date (Date where the agency began reporting either LIBRS or UCR data to the State), then the Arrest should not be sent
to us.
Data Characteristics: 8 Character Date. Must be included and cannot be Blank or all Zeros.
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for Arrest Date (DE 42) is not valid. Please ensure that the supplied date
DATE ENTERED MUST BE A VALID CALENDAR
1 is in the MMDDYYY Format. Additionally this value cannot be all zeros, it must be a real 11005
DATE
date.
When Date of Arrest (DE 42) is present, it cannot be earlier than the Incident Date/Hour (DE ARREST DATE CANNOT BE BEFORE THE
2 16065
3). INCIDENT START DATE
When Date of Arrest (DE 42) is present, it cannot be later than the Submission Date (DE C3) ARREST DATE CANNOT BE AFTER TAPE
3 16066
present in the Header Segment (Segment 00) of the LIBRS Flat File. SUBMIT DATE MONTH AND YEAR
ARREST DATE CANNOT BE AFTER THE
All reported Arrests need to occur either during or before the period that is being reported.
4 16082 REPORTING PERIOD THE SUBMISSION
EG: You cannot report an arrest that occurred on 11/15/2020 on the 10/2020 Flat File.
DOCUMENT REPRESENTS
Details:
Arrest Date (42) is used to enter the month, day and year when the actual arrest took place.
Type of Arrest (43)
Description: Type of Arrest details how the arrest was initiated by the Officer, and if the individual was brought into custody or not.
Data Characteristics: 1 Character Alpha. This field is required for each Segment 60 present in the Incident.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
1 11004
Element Values. VALIDATION TABLE
Details:
Type of Arrest (43) indicates the type of apprehension.
Allowed Entries:
Enter only one code per Arrest Segment:
Type of Arrest
O - On-View Arrest (taken into custody without a warrant or previous incident report.)
S - Summoned / Cited (not taken into custody)
T - Taken Into Custody (based on warrant and/or previously submitted incident report.)
Multiple Arrestee Segment Indicator (44)
Description: The Multiple Arrestee Indicator is used to Identify if arresting an Offender for One Incident has cleared another Incident by arrest. In cases where an individual that is
arrested is a suspect in more than one Incident, the Multiple Arrestee Indicator allows the agency to denote that one or more Incidents involving the Offender have been cleared by an
Arrest, however the individual was not arrested multiple times.
For instance, if an Suspect already has a warrant out for their arrest, and they are then arrested for another Offense in a different Incident, the Incident that caused the warrant to be
issued is now cleared by arrest, as well. However, the Suspect was only arrested one time. So the Multiple Arrestee Indicator allows the Agency to specify that both incidents have been
cleared, but only one arrest was made.
Data Characteristics: 1 Character Alpha. Required for Each Segment 60 (Arrest Segment) that is present in the Incident.
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element is a
1 10001 MUST BE PRESENT–MANDATORY FIELD
mandatory field.
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
Details:
Multiple Arrestee Segment Indicator (44) ensures that an Arrestee is counted (scored) only once when the Arrestee’s apprehension causes the Arresting Agency to submit two or
more Arrestee Segments (60) concerning separate Incident Reports. That is, the Arrestee was involved in more than one crime incident and his/her arrest data are duplicated in
each Incident Report.`
In such a situation, Count Arrestee (“C”) is to be entered into one of the Arrestee Segments (60), and Multiple (M) is to be entered into all of the remaining Arrestee
Segments (60).
If the Arrestee’s apprehension DOES NOT cause the Arresting Agency to submit multiple Arrestee Segments (60), enter Not Applicable (“N”).
Count Arrestee (“C”) and Multiple (“M”) codes are to be used in this Data Element (44) ONLYwhen the same agency submits two or more Arrestee Segments (for different
incidents) relating to the same Arrestee.
Allowed Entries:
Enter only one (1) code per Arrestee Segment:
Multiple Arrestee Segment Indicator
M - Multiple
C - Count Arrestee
N - Not Applicable
Examples:
Example Number Description
After a suspect’s apprehension for robbery, it was learned that he was also responsible for five additional robberies within the jurisdiction.
One Arrestee Segment (60) was keyed into the local computer, along with the Incident Numbers of the six incidents
The local computer then generated six Arrestee Segments (60) which were duplicates except for their Incident Numbers
1
Five of the Arrestee Segments (60) had Multiple ("M") and one had Count Arrestee ("C") entered into Multiple Arrestee Segment Indicator (44)
Each of the six robberies is cleared.
2 If the suspect’s arrest did not clear additional incidents, the entry should be Not Applicable (“N”).
Louisiana Revised Statute Number of Arrest (45)
Description: The LRS Number of Arrest is the Statute in which the Offender was Arrested For. It needs to match one of the Statutes that are present in the Offense Segments (Segment
20). NIBRS Doesn’t have this restriction, and allows you to submit an Arrest for an Offense not related to the Incident, but LIBRS does not have this leniency.
Data Characteristics: 12 Character Alpha. Cannot be left blank and can only contain one (1) Hyphen (-).
Format: TT:SSSS.S/P-I
Louisiana Revised Statute Format
TT Title
SSSS.S Section
Subpart, or
Subpart with Qualifier, or
PPP/I Qualifier, or
Juvenile Qualifier, and An Inchoate Modifier, if applicable, would be indicated
by a dash with a data value behind the LRS Code that defines the offense.**
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA
VALUE–NOT ON
1 Must be a valid code on Master LIBRS/LRS Code Table. Check the Master LRS List for available codes to use. 11004
LIBRS VALIDATION
TABLE
NO ARRESTEE
An Incident cannot have any Arrests when there is only one Offense Segment (Segment 20) present, and it has an
RECORDS ALLOWED
2 Offense Code of 09C (Justifiable Homicide). A Justifiable Homicide never involves an arrest of the Offender (The 16069
FOR A JUSTIFIABLE
person who committed the Justifiable Homicide).
HOMICIDE
Details:
This Data Element records the Louisiana Revised Statute that the Arrestee was charged with.
The structure of a Louisiana Revised Statute (LRS) is: Title (TT), followed by a colon, then a Section Number (SSSS.S), followed by optional Subparts, Qualifiers and Modifiers.
Section and Subpart/Subpart with Qualifier/Qualifier/Juvenile Qualifier/Inchoate Modifier, should NOT be preceded by spaces or zeroes.
If there are no places after the decimal, then both the place after the decimal and the decimal point should be omitted.
For example, the LRS for Murder is 14:30 – two spaces for the Title (14), a colon, two spaces for the Section (30) before the decimal, not four spaces - 14:GG30 - and
dropping the space after the decimal.
The field should be LEFT JUSTIFIED WITH NO INCLUDED SPACES. Spaces are interpreted as the End-of-Data in this data element.
Subparts, Qualifiers, etc. are sometimes included for more specificity regarding those LRS codes requiring these identifiers. These parts of the field can be expanded or
contracted as necessary to fill in the data.
All local ordinances must be reported with the appropriate state statute as the base offense, with any Subparts, Qualifiers, etc. added when applicable.
When a parish statute does not correspond to a state LRS, the parish statute must be reported with a “P:” for the title and the parish statute following the colon.
If a city ordinance does not correspond to a state LRS, it must be reported by the police department with a “C:” substituted for the title portion of the data field, and the
city ordinance following the colon.
When it is a Sheriff’s Office, or any other law enforcement agency who has jurisdiction in more than one city, reporting the city ordinance, it should be reported
with a “C#:” substituted for the title portion of the data field, and the city ordinance following the colon, where the “#” is replaced with a unique number for each
city as decided by the agency and agreed upon by the state.
Agency Supplied NIBRS Code For Arrest (N45)
Description: The Agency Supplied NIBRS Code For Arrest is the NIBRS Code with which the Agency would like to submit to the FBI as the Offense for the Arrest.
This Data Element was created before NIBRS Codes were mandatory, and we’ve since written code to use the NIBRS Code that’s supplied in the Offense Segment if it’s missing. However
we would encourage you to include it as an extra measure to make certain the Arrest is being reported as desired.
Data Characteristics: 3 Character AlphaNumeric. Optional. If Inlcuded must be a NIBRS Code that’s a Valid Mapping for the LRS Code for Arrest (DE 45). Refer to the Master LRS List for
more details.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Error
Requirement Requirement Description Error Message
Number
he LRS Code that you have submitted doesn’t have a mapping to a NIBRS Code in our system. Please use a valid NIBRS
LRS-TO-NIBRS
Mapping for this LRS Code, and if you think the LRS Code you submitted should be valid let us know and we’ll see if we
PAIR MUST HAVE
1 can add it in. 90017
A VALID
MAPPING
This Error also triggers when Louisiana Revised Statute Number of Arrest (DE 45) is left blank.
Arrest Connection to Offense (L45)
Description: Arrest Connected to Offense is how an Arrestee gets linked to the Offense they were arrested for. It isn’t just the Sequence Number. This Data Element allows you to link
an Offense from Other Incidents, as well, to the Arrest performed in this one. Because of that the Incident Number in which the Offense was reported also needs to be included.
The format is simply the Offense Sequence Number (DE ) followed by the Incident Number (DE 3) that contains the Offense the Offender is being arrested for. EG If it’s Offense
Sequence Number 2, and the Incident Number is 20-000100-01, then this value would be ‘00220-000100-01’
Data Characteristics: 15 Character Alpha
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element is a mandatory
1 10001 MUST BE PRESENT–MANDATORY FIELD
field.
DE L45 IS REQUIRED AND SHOULD BE A
Arrest Connection to Offense (DE L45) should be 15 characters long, and combine a valid Offense
15 CHARACTER STRING THAT
Sequence Number and Incident Number together. EG: If an Offender is Arrested for Offense
2 90043 COMBINES A VALID OFFENSE
Sequence Number 001 from Incident Number 20-000001-01, the DE L45 should be ‘00120-
SEQUENCE NUMBER AND INCIDENT
000001-01’.
NUMBER
MUST be a valid Offense Sequence Number (L6). The Offense Segment (20) referred to by this Data Element (L45) MUST exist.
Details:
Arrest Connection to Offense (L45) relates an Arrest with the Offense giving rise to the Arrest. Indirectly, it also relates an Offender to his Victim. All Offenses should be included
if a charge was added for the particular Offense, even those from different previous incidents.
The first three characters are the Offense Sequence Number (L6) of the Offense (6).
The next twelve characters are the Incident Number (2) of the Offense.
If Multiple Arrestee Segment Indicator (44) is anything except Not Applicable (“N”) then this field will be connecting an Arrest to Offenses in two or more separate
incidents.
The Incident Number (2) is appended to distinguish between Offense 001 in this incident and Offense 001 in a different incident.
The combined Offense Sequence Number (L6) and the Incident Number (2) add together to give a unique identifier (15 characters) indicating which Offense gave
rise to the Arrest.
The Incident Number (2) can be omitted if Multiple Arrestee Segment Indicator (44) is Not Applicable (“N”), because all Offenses will be in the same incident. And
therefore, the Incident Number (2) can be assumed to be that of the incident with which the Arrestee Segment (60) was submitted.
Arrestee was Armed With [At Time of Arrest] (46)
Description: Arrestee was Armed With is used to report what, if anything, an Arrestee had on their person that was a Weapon whenever they were brought into custody. This Data
Element is not as descriptive as Weapon/Type of Force Used (DE 13), but that’s because it’s limited to items that the Arrestee was in possession of.
Data Characteristics: 3 Character Alpha. Can’t be blank, must have a selection. Third Character is reserved for the ‘A - Automatic’ designation, which is only to be used with Firearms.
Otherwise, the third character is to be a Blank Space (G).
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element
1 10001 MUST BE PRESENT–MANDATORY FIELD
is a mandatory field.
Supplied Value not recognized. Must conform to a value on the List of Available INVALID DATA VALUE–NOT ON LIBRS VALIDATION
2 11004
Data Element Values. TABLE
Only the following values are allowed to use the ‘A - Automatic Weapon’ indicator
in Type of Weapon/Force Involved (DE 13):
11 Firearm (Type not Stated)
12 Handgun WEAPON TYPE MUST = 11, 12, 13, 14, OR 15 FOR AN
3 12058
13 Rifle ‘A’ IN THE AUTO INDICATOR
14 Shotgun
15 Other Firearm
Details:
If the Arrestee was in possession of a toy or play weapon this would be reported as being Unarmed (“01”).
Arrestee was Armed With (46) indicates if the Arrestee was armed with a commonly known weapon at the time of his/her apprehension.
If the weapon was an “automatic” firearm, an Automatic (‘A’) designation is added as a suffix code, (for example, Rifle Automatic (‘13A’).
An “Automatic Firearm” is defined as any firearm that shoots, or is designed to shoot, more than one shot at a time by a single pull of the trigger without manual
reloading.
Allowed Entries:
Enter only one of the following codes:
Arrestee was Armed With
01 - Unarmed
11 - Firearm (Type Not Stated)
12 - Handgun
13 - Rifle
14 - Shotgun
15 - Other Firearm
16 - Lethal Cutting Instrument (switchblade knife, martial arts 'stars', Etc.)
17 - Club, Blackjack or Brass Knuckles
Examples:
Example
Description
Number
When a man was arrested, he had in his possession a .357-Magnum handgun and a penknife. The entry should be Handgun (‘12’). Because a small pocket knife is
1
not generally considered to be a ‘weapon’, it does not qualify for reporting to LIBRS.
A female resisted arrest using a liquor bottle and a chair as a weapon before being subdued. The entry for LIBRS should be Unarmed (‘01’). Although the subject
2
used items as weapons, they were not commonly known weapons.
Age of Arrestee [At Time of Arrest] (47)
Description: Age of Arrestee is the age the Arrestee was on the Date of their Arrest. Ages can be appended with an ‘E’ to represent an Estimated Age of the Arrestee if that actual Age
is not known, otherwise the third character should remain a Blank Space.
Data Characteristics: 3 Digits Alpha/Numeric. Cannot be Blank and must always have a value. Use ‘00’ if Age is Unknown.
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element is a mandatory field. 10001
MANDATORY FIELD
For Exact Ages the first two characters in Age of Arrestee (DE 47) need to be a two digit number (front- EXACT AGE MUST BE IN FIRST
2 14008
padded with a zero if less than 10 - EG: 07, 09), with the third character as a Blank Space (G). TWO POSITIONS
ESTIMATED AGE MUST BE 2
For Estimated Ages the first two characters in Age of Arrestee (DE 47) need to be a two digit number (front-
3 14009 NUMERIC DIGITS, AND HAVE
padded with a zero if less than 10 - EG: 07, 09), with the third character as an ‘E’ to represent the estimation.
A TRAILING ‘E’
ESTIMATED AGE CANNOT BE
Age of Arrest (DE 47) is only to use the Estimated Age Modifier ‘E’ if the Age is actually being Estimated. ‘00’
4 14022 ‘00’ UNKNOWN AND HAVE A
for an Unknown Age is not an estimate, and therefore not a valid input.
TRAILING ‘E’
When Age of Arrestee (DE 47) is an exact value (IE Not Estimated), then it must contain numeric entry of 00- ARRESTEE AGE MUST BE
5 16064
99. NUMERIC DIGITS
When Juvenile Qualifiers are used, Age of Arrestee (DE 47) must be ‘01’ thru ‘17’ (this includes 17) for the
following Juvenile Qualifiers:
(JU:RUN) Runaway Offense (90I)
(JU:UNG) Ungovernable (90C) AGE MUST BE ‘01’ - ‘17’ FOR
6 22100
(JU:CUR) Curfew (90B) JUVENILE OFFENSES
(JU:TRU) Truancy (90Z)
Note: As of January 1st, 2020, all offenders under the age of 18 are considered juveniles.
Details:
Age of the Arrestee (47) can be entered either as an exact number of years, an estimated age, or as unknown.
Note: Age at time of Arrest.
Note: (00) Unknown CANNOT have ‘E’ with this data value
Note: When Arrestee’s Age is not known, estimate the Arrestee’s Age and append an ‘E’ (Estimated).
Allowed Entries
Enter only one code per Arrest Segment (60):
Age of Arrestee
01-98 - Age in years
99 - Over 98 Years Old
00 - Unknown
Examples:
Example
Description
Number
An Arrestee refused to give his Date of Birth, but he appeared to be 35 to 40 years old. Possible entries would be Unknown (‘00’) or an estimated 37 years old
1
(‘37E’). Use the latter when possible.
Date of Birth of Arrestee (L47)
Description: DOB of Arrestee is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then it’s required
that the Age of Arrestee have an Exact, not Estimated Value.
Data Characteristics: Data Characteristics: 8 Character Date. Optional, if not entered should be all Blank Spaces (Not Zeros).
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for Date of Birth of Arrestaee (DE L47) is not valid. Please ensure that the supplied date is in DATE ENTERED MUST BE A
1 11005
the MMDDYYY Format. Additionally this value cannot be all zeros, it must be a real date. VALID CALENDAR DATE
AGE CANNOT BE
2 Age of Arrestee (DE 47) cannot be Unknown if Date of Birth of Arrestee (DE L47) is Known. 22105 UNKNOWN IF DATE OF
BIRTH IS KNOWN
Details:
If Date of Birth of the Arrestee is Known, it should be entered into this Data Element.
Sex of Arrestee (48)
Description: The Sex of the Arrestee.
Data Characteristics: 1 Character Alpha. Must always have a value.
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element is a
1 10001 MUST BE PRESENT–MANDATORY FIELD
mandatory field.
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
Details:
This Data Element (48) indicates the sex of the Arrestee.
Allowed Entries
Enter only (1) code per Arrest Segment:
Age of Arrestee
M - Male
F - Female
Race of Arrestee (49)
Description: Race of Arrestee is used to indicate the race of the Arrestee. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons that share
similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Must always have a value; use U if Unknown, don’t leave the field blank.
Requirements:
Error
Requirement Requirement Description Error Message
Number
When Arrestee Segments (Segments 60, 61, and 62) are present, this Data Element is a
1 10001 MUST BE PRESENT–MANDATORY FIELD
mandatory field.
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
2 11004
Element Values. VALIDATION TABLE
Details:
Notes: Race of Arrestee (49) is indicated by this Data Element.
Allowed Entries
Enter only (1) code per Arrest Segment (60):
Race of Arrestee
W - White
B - Black
I - American Indian/Alaskan Native
A - Asian or Pacific Islander
U - Unknown
Ethnicity of Arrestee (50)
Description: Ethnicity of Arrestee is used to indicate the Ethnicity of the Arrestee. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons
that share similar cultural characteristics.
Data Characteristics: 1 Character Alpha. Optional Value, but if supplied must conform to the List of Available Values.
Requirements:
Error
Requirement Requirement Description Error Message
Number
If entered, must conform to a value on the List of Available Data Element INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
Values. TABLE
Details:
This Data Element indicates the ethnic origin of the Arrestee.
Allowed Entries
Enter only (1) code per Arrest Segment (60):
Ethnicity of Arrestee
H - Hispanic Origin
N - Not of Hispanic Origin
U - Unknown
Resident Status of Arrestee (51)
Description: Resident Status of Arrestee is used to indicate whether or not the Arrestee is a resident of the justidiction of the Arresting Agency. It is not meant to indicate whether or
not the Arrestee is a US Citizen or Permanent Resident.
Data Characteristics: 1 Character Alpha. Optional Value, but if supplied must conform to the List of Available Values.
Requirements:
Error
Requirement Requirement Description Error Message
Number
If entered, must conform to a value on the List of Available Data Element INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
Values. TABLE
Details:
The Arrestee’s Residency Status, whether Resident (‘R’) or Nonresident (‘N’), is entered into this Data Element.
A ‘Resident’ is a person who maintains his/her permanent home for legal purposes in the locality (i.e., town, city, or community) where the crime took place.
Allowed Entries
Enter only (1) code per Arrest Segment (60):
Resident Status of Arrestee
R - Resident
N - Nonresident
U - Unknown
Disposition of Arrestee Under 18 (52)
Description: Disposition of Arrestee Under 18 denotes how Juvenile Arrestees are handled. It is a mandatory field for ANY Arrestee that is 17 AND Younger (Under 18, not including 18).
Data Characteristics: 1 Character Alpha. Required for Arrestees 17 and Younger. Should be left Blank for Arrestees that are not.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Supplied Value not recognized. Must conform to a value on the List of Available Data INVALID DATA VALUE–NOT ON LIBRS
1 11004
Element Values. VALIDATION TABLE
If Age of Arrestee (DE 47) is under 18 (17 and younger), then Disposition of Arrestee
Under 18 (DE 52) must be entered. DISPOSITION MUST BE ENTERED WHEN AGE IS
2 16052
17 AND YOUNGER
Note: As of January 1st, 2020, all offenders under the age of 18 are considered juveniles.
If Age of Arrestee (DE 47) is 18 or older, then Disposition of Arrestee Under 18 (DE 52) FOR AGE 18 AND OLDER DISPOSITION SHOULD
3 16053
should not be entered. NOT BE ENTERED
Details:
Disposition of Arrestee Under 18 (52) is to be used ONLY if the Arrestee was 16 years of age or younger at the time of arrest.
This will change to Arrestee under 18 on 01/01/2020
Allowed Entries
Enter only (1) code per Arrest Segment (60) for Juveniles only:
Disposition of Arrestee Under 18
D - Handled Within Department and Released.
J - Referred to Juvenile Court or Probation Department
W - Referred to Welfare Agency
P - Referred to Other Police Agency
A - Referred to Criminal or Adult Court
Examples:
Example
Description
Number
The Arrestee, age 13, was apprehended for vandalizing a school, then released to his parents with a warning. The entry should be Handled Within the
1
Department and Released (‘D’).
The Arrestee, age 16, was arrested for rape, and turned over to the Adult Court to be tried as an adult. The entry would be Referred to Criminal or Adult
2
Court (‘A’).
Location of Incident (Geographical Coordinates) (L53)
Description: Location of Incident is a purely Optional field that contains the Longitude and LAtitude of and Incident’s Location. It is used for more advanced Analytics purposes, but at
this time is not required and can be left blank.
Data Characteristics: 12 Character Numeric.
Format: DDMMSSDDMMSS
First Six (6) Characters in Longitude First Six (6) Characters in Latitude
DD Degress DD Degress
MM Minutes MM Minutes
SS Seconds SS Seconds
Requirements:
None. Value is taken on faith; we have no way to validate it.
Details:
Location of Incident (52) reports the geographical location of the incident. This field is not required and should be left blank if the agency does not track incidents with the use of
geographical coordinates.
Optional: This field is not validated nor submitted to the FBI.
Allowed Entries
Not required for LIBRS Releases 1.0/1.1. or 2.0, unless agency uses geographical coordinates to track incidents. Entry should either be valid geographical coordinates, or Blank (G). If
agencies submit zeroes, program will produce errors because zeroes are numeric.
Station/Division/Precinct Identifier (L54)
Description: Station/Division/Precinct Identifier is a short code to identify which Precinct the Incident Report is coming from. It is not required, but may be useful for Analytics for the
Agency down the line. At this time it is not being valudated or used, only stored.
Data Characteristics: 6 Character Alpha. Optional with no restrictions on Alpha/Numeric Characters, Spaces, or Hyphens.
Requirements:
None. Value is taken on faith; we have no way to validate it. It can be used for an Agency to perform Analytics on their Incident reports, though, so if it’s included it’s recommended to
be consistent for each Precinct.
Details:
This field is optional and is for the reporting agency’s use in locating incidents.
Arrest Transaction Number (ATN) for Louisiana (L55)
Description: ATN for Louisiana is the Unique Identifier of an Arrestee in AIFIS.
Data Characteristics: 15 Character Alpha/Numeric
Requirements:
MUST be present if fingerprints are submitted to the Bureau of Identification of the Louisiana State Police.
Error
Requirement Requirement Description Error Message
Number
Arrest Transaction Number (DE L55) may only contain [A - Z], [0 - 9], ‘-‘, and ‘ ‘ INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 11004
(Spaces). TABLE
Details:
Arrest Transaction Number (L55) is generated by the live scan when fingerprinting an Arrestee or is a pre-assigned number generated and assigned at the time of the
fingerprinting. This ATN number is defined as:
Characters 1-4 4th, 5th, 6th, and 7th characters of the ORI number of the agency that made the arrest, or where the live scan device is housed.
Character 5 live scan device number assigned to the device being used to generate this Arrestee’s fingerprints.
Characters 6-7 indicates the year this Arrestee’s fingerprints are being scanned into this device.
Characters 8-12 Arrest Sequence Number for this arrest event. This is a number counter that sequentially assigns a number to each arrest event
Characters 13-15 indicates the number of charges being assigned to this Arrestee at the time these fingerprints are being scanned. For instance, if an Arrestee is being
charged with five counts of Aggravated Battery for this arrest, the numbers generated would be “001” through “005.”
The Arrest Transaction Number (L55) is used to facilitate crime analysis. Arrest Transaction Number (L55) is the number assigned when an Arrestee is fingerprinted on the
Automatic Finger Print Information System (AFIS). This data element can be sent on every Arrestee, but is only mandated if the Louisiana Revised Statute is a felony arrest
or charges required fingerprints.
Inchoates (70)
Description: The Inchoate Modifier is to be added to the end of the LRS Code (DE 6) present in Offense and Arrestee Offense Segments (Segments 20 and 41). It’s used to add context
to the charges laid against an Offender. EG: Hiring a person to commit a murder should be charged with Attempted Murder, however the Addition of the Inchoate Modifier of ‘-I’ for
‘Inciting a Felony’ gives us extra context about exactly what happened.
If you don’t have an Inchoate Modifier to add, leave this Data Element Blank. If present, the Inchoate Modifier should appear in either/both the Offense and Arrestee Statute Segments
(as appropriate).
Data Characteristics: 2 Character Alpha, Fist Character is “-“
Requirements:
Error
Requirement Requirement Description Error Message
Number
Inchoate Modifiers have a limited number of options that can be chosen from. Please refer VALID CHOICES FOR INCHOATE MODIFIER ARE
1 22085
to the List of Available Data Element Values. ‘-A’, ‘-C’, ‘-I’, ‘-S’, OR ‘-H’
Control Data Elements
Segment Descriptor (C1)
Description: The Segment Deescriptor is what tells LIBRS what data to expect in each line of the Flat File. It absolutely MUST be included in each line.
Data Characteristics: 2 Character Numeric. First two characters of each line in a LIBRS Flat File.
Requirements:
Error
Requirement Requirement Description Error Message
Number
Unrecognized Segment Descriptor. Please verify that the Segment Markers in the Flat File conform to the LIBRS INVALID RECORD
1 10051
Specifications. SEGMENT ON TAPE
Segment Descriptor (DE C1) is a mandatory Data Element, and cannot be left blank. It should be included in every MUST BE PRESENT–
2 20001
segment of the Flat File to denote the context of the data present in that line. MANDATORY FIELD
Details:
This two-digit identifier is used by LIBRS to determine the type of segment being processed.
Allowed Entries for Data Element C1:
Value Segment Descriptors Value Segment Descriptors
00 Submission Header 41 Offender Using
01 Zero Records 50 Victim
10 Administration 51 Victim Injury
11 Administration Modification 52 Victim/Offender Relation
20 Offense 60 Arrestee
30 Property 61 Arrestee Armed
31 Property Description 62 Arrestee Statute
32 Property Modification 63 Arrestee Modification
33 Property/Offense 99 Submission Trailer
40 Offender
Submitting Agency (C2)
Description: The Submitting Agency is the Name of the Agency (EG: East Baton Rouge Parish Sheriff’s Office rather than EBRSO) that is Submitting the LIBRS Flat File. It’s not Validated,
but is useful for back-end purposes to keep consistent.
Data Characteristics: 20 Character Alpha. Only used in Header Segment (Segment 00)
Requirements:
Error Error
Requirement Requirement Description
Number Message
This error is thrown when a LIBRS Flat File is submitted to the Full Application (not the Validator Website) and we have not been MUST BE
1 made aware of the Agency’s desire to begin submitting LIBRS Data. If you get this error, please contact us and let us know your 20010 A VALID
ORI Number and contact details so we can enable your Agency for Testing mode. AGENCY
Details:
The name of the Submitting Agency is spelled out, and often abbreviated. This data field is found in the Header Segment, which is the first segment in all data submission files.
Submission Date (C3)
Description: Submission Date is the MMDDYYYY Format Date that the LIBRS Flat File was generated. Ideally it’s the same day that it was Submitted to LIBRS, but we use it as a way to
keep which files came in when to figure out which one to trust.
Data Characteristics: 8 Character Date. Only used in Header Segment (Segment 00)
Format: MMDDYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
The date supplied for the Submission Date (DE C3) is not valid. Please ensure that the supplied DATE ENTERED MUST BE A VALID
1 11005
date is in the MMDDYYY Format. CALENDAR DATE
MUST BE PRESENT–MANDATORY
2 Submission Date (DE C3) is a mandatory Data Element, and cannot be left blank. 20001
FIELD
Details:
This data element provides LIBRS with the date that this data submission file was generated for submission.
Reporting Period (C4)
Description: Reporting Period is the MMYYYY Format Date of the LIBRS Reporting Period (Month) that the Flat File represents. It is used to test for Out of Sequence Errors, so it’s very
important to keep straight as submissions move forward.
Data Characteristics: 6 Character Date. Only used in Header Segment (Segment 00)
Format: MMYYYY
Requirements:
Error
Requirement Requirement Description Error Message
Number
MUST BE PRESENT–
1 Reporting Period (DE C4) is a mandatory Data Element, and cannot be left blank. 20001
MANDATORY FIELD
Reporting Period (DE C4) cannot be In or After the Date of Submission (DE C3). EG: If today’s date is 06/01/2020, REPORTING PERIOD
3 then you cannot report and Reporting Periods of 062020 or later because those months have not occured or 20026 CANNOT EXCEED THE
completed yet. DATE OF SUBMISSION
Details:
Reporting Period identifies the month and year that the Incident-Based data in a data submission file is being reported. All data in the data submission does not have to
correspond to this date (i.e., Modifications and Time-Window Submissions will be from preceding months).
Action Type (C5)
Description: Action Type designates what LIBRS should do with the Line of data that it’s about to read. For modern implementations we would recommend only using ‘I - Insert’ and ‘D
- Delete’, however in order to maintain support for older systems, we do still allow all Five (5) Action Types to be submitted.
The Types Available are:
I - Insert
By far the most common Action Type you will use.
Used to tell us that the data you’re sending us is new and we need to save it in the database.
Available for use on all Segments except for Header and Footer (Those don’t have an Action Type).
D - Delete
The next most common Action type used.
Used to tell us that we need to delete an Incident from the Database.
Is only used with Segment 10. Do delete an Incident you just send us the Segment 10 of the Incident, but change the I to a D in the third Character.
W - Time Window Submission (Legacy)
Used to submit data to the FBI for Incidents that occurred before the Agency’s Base Date
Really uncommon to be used.
A - Add Arrest (Legacy)
You can use this to add an Arrest to an already reported Incident.
We would recommend just passing us a Delete and then resubmitting the whole Incident as an Insert, though. It’s less code for everyone to manage.
M - Arrest Modification (Legacy)
This can be used to change details about an Arrestee that’s already been submitted to LIBRS.
Again, we recommend not using this in favor of deleting the Incident and re-inserting it.
Data Characteristics: 1 Character Alpha. Used on every segment in the Flat File Except for the Header and Footer Segments.
Requirements:
Error
Requirement Requirement Description Error Message
Number
ARRESTEE SEQUENCE NUMBER (DE 40)
If a LIBRS Flat File contains the duplicate Arrestee Sequence Numbers (DE 40) for the same
CANNOT REPEAT FOR THE SAME INCIDENT
1 Incident Number (DE 2), the at least one of the Action Types of the the Arrestee Segments 16161
NUMBER (DE 2) THE FLAT FILE UNLESS THERE
associated with the Sequence Number must have an Action Type (DE C5) or ‘D - Delete’.
IS AN ACTION TYPE OF DELETE
Action Type (DE C5) is a mandatory Data Element, and cannot be left blank. It should be
2 included in every Segment of the Flat File aside from the Header Segment (Segment 00) 20001 MUST BE PRESENT–MANDATORY FIELD
and Footer Segment (Segment 99)
The Action Type Specified in Segments 20, 40, 41, and 50 need to match the Action Type in VALUE MUST MATCH THE VALUE SUPPLIED IN
2 90042
Segment 10. ADMINISTRATIVE SEGMENT (SEGMENT 10)
Details:
Action Type (C5) informs LIBRS of the type of action that LIBRS and NIBRS are required to take with incident data contained by the segment.
Allowed Entries for Data Element C5:
Action
Action Performed by LIBRS/NIBRS
Type
Incident Report
I
Incident Reports submitted with an Action Type of “I” are new incidents that are being reported to the LIBRS/NIBRS databases for the first time)
Add Arrest
Action Type “A” submissions are used to add an arrest to an incident that has previously been reported with an Action Type of “I”. Action Type “A” can only be used if
A
incident has already been submitted and there are no changes in other segments of the incident, that is, the agency is simply adding an arrest segment to the already
submitted incident
Modify
M Action Type “M” segments are used for Time-Window Submission correction for an Exceptional Clearance, Recovered Property or Arrests). It can alsobe used to
modify exceptional clearance indicator and/or exceptional clearance date when incident has already been submitted.
Delete Action
D Type “D” segments are used to delete previously submitted incidents. It is often used when updates or changes are reported to a previously submitted incident. An
Action Type “D” segment will delete all existing incident data, allowing the reporting agency to re-submit the incident containing the updated information
Time-Window Submission
Action Type “W” is used only when reporting an incident that occurred prior to the reporting agency’s “base date” as defined in the Guidelines. An agency’s base date
is usually the date when the agency first started reporting incident-based data to LIBRS/NIBRS. The Time-Window Submission can report one of the following:
W - Exceptional Clearance
- Exceptional Clearance Date
- Recovered Property
- An Arrest
Clearance Indicator (C6)
For Time Window Submissions, ONLY
Description: Clearance Indication is a Y/N Value that’s used exclusively in Time Window Submissions to state whether or not the Incident has been cleared by an Arrest or not.
Data Characteristics: 1 Character Alpha.
Requirements:
Error
Requirement Requirement Description Error Message
Number
INVALID DATA VALUE–NOT ON LIBRS VALIDATION
1 Supplied Value not recognized. Must be either ‘Y’ or ‘N’ for Yes or No. 11004
TABLE
Clearance Indicator (DE C6) must be Blank (G) when Action Type is not ‘W’ (Time- MUST BE BLANK WHEN ACTION TYPE IS NOT ‘W’
2 16058
Window). (WINDOW)
If Action Type (DE C5) is ‘W’ (Time-Window), then Clearance Indicator (DE C6)
3 20001 MUST BE PRESENT–MANDATORY FIELD
cannot be left blank.
Details:
Clearance Indicator (C6) is used in the Arrestee Segment (60) to indicate whether this arrest produced a clearance, or is an additional arrest on a previously cleared incident that
is outside the agency’s base date.
Allowed Entries for Data Element C6:
Clearance Indicator
Yes - Submit “Y”, if this is the first Arrestee Segment (60) submitted for an Incident. By submitting a “Y”, the Arrest clears an Incident that happened prior to the date the
Y
agency began submitting Incident-Based Data to the LIBRS/NIBRS system (that is, a Time-Window case that is not on the LIBRS/NIBRS database).
No - Submit ‘N’, if a previous Arrest Segment (60) was already submitted for an Incident. (That is, the case has already been cleared for an Incident that occurred since the
N
agency’s base data, and is in the LIBRS/NIBRS database).
Number of Segments Transferred (C7)
Description: Number of Segments Transferred is quite literally the number of lines that are present in a LIBRS Flat File, including the Header and the Footer Segments. Effectively it is
just the line number of the Footer Segment.
Data Characteristics: 6 Character Numeric, Front-Padded with zeros (EG: 525 should be 000525).. Only used in Footer Segment (Segment 99)
Requirements:
Error
Requirement Requirement Description Error Message
Number
Number of Segments Transferred (DE C7) is a mandatory Data Element, and cannot be left
1 20001 MUST BE PRESENT–MANDATORY FIELD
blank. It should appear one time in the Footer Segment (Segment 99)
MUST BE EQUAL TO THE TOTAL NUMBER
3 DE C7 must be equal to the total number of segments within the data submission file 20031
OF SEGMENTS WRITTEN TO THE TAPE.
Details:
This field provides LIBRS with a count of segments submitted by the agency within the data submission file, including the header and trailer segments. This number is used as
part of the data submission validation process.
Allowed Entries: Any integer greater than or equal to 000003.
End of Segment Marker (C8)
Description: The End of Segment Marker us used to tell LIBRS where the data in a line ends, and if anything else is in the line to ignore it. It is an older data element that was brought
forward for backwards compatibilty, however it is important that it is placed in the correct location and is the correct characters (‘ZZ’).
Data Characteristics: 2 Character Alpha. Only in every Segment.
Requirements:
Error Error
Requirement Requirement Description
Number Message
End of Segment Marker (DE C8) is a mandatory Data Element, and cannot be left blank. It should be used in every segment
MUST BE
of the LIBRS Flat File to denote the end of the line.
PRESENT–
1 20001
MANDATORY
Note: All lines should still be 150 characters long. Any different in length between the position of the End of Segment
FIELD
Marker (DE C8) and 150 characters should be filled with Blank Spaces (G).
END OF
SEGMENT
End of Segment Marker (DE C8) is required for all segments, and must be ‘ZZ’. The End of Segment Marker does not mark
MARKER,
2 the end of the line, but rather the end of the Segment, so each line should still be filled to the full 150 characters with Blank 20029
MUST BE
Spaces (G) after the End of Segment Marker is present.
EQUAL TO
‘ZZ’
Details:
This field is used to provide LIBRS with a way to determine where an end of record occurs. In the event of an error in record length this will allow the LIBRS system to find the start of
the next record and possibly recover from the error. The “End of Segment” marker is the same for all segments, two capitol Z’s.
Allowed Entries: “ZZ” only.
Padding (C9)
Description: Padding is used to fill out unused area in a LIBRS Flat File to keep consistent formatting across each Segment.
Data Characteristics: Character Alpha/Numeric. Used in every Segment.
Requirements:
Requirement Requirement Description
1 Must be Blank (G) if fixed length records are submitted. MUST be one newline character (ASCII 13; CR, LF, or CRLF) if variable length records are submitted.
2 If Fixed-Length records are used, add padding from the End of Segment Marker (C8) to exactly column 150.
3 Segment 00 MUST have both Padding to column 150 and a new line charachter (ASCII 13; CR, LF, or CRLF)
Details:
This field is used to pad unused fields for systems that are unable to write variable length records. This padding will lengthen all segments to 150 characters. Padding can be
replaced with a newline character for those systems that can write variable length records. The newline character will mark the true End-of-Record. Variable length records are
preferred by LIBRS because of the space savings they allow.
Allowed Entries: Blank spaces or the newline character (ASCII 13).
Software ID (C10)
Description: Software ID is used to tell LIBRS the RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that’s being caused by something
invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved.
Data Characteristics: 5 Characters Alpha/Numeric. Only used in Header Segment (Segment 00)
Requirements:
Requirement Requirement Description
1 Contains Identification of software used to generate the LIBRS data submission
Software Version (C11)
Description: Software Version is used to tell LIBRS the Version RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that’s being caused
by something invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved.
Data Characteristics: 10 Characters Alpha/Numeric. Only used in Header Segment (Segment 00)
Requirements:
Requirement Requirement Description
1 Contains Version of software used to generate the LIBRS data submission
LIBRS Spec Indicator (C12)
Description: As of 2019, the LIBRS Spec must be present in the Header Segment, and it must be equal to ‘2.5’
Data Characteristics: 3 Characters Alpha/Numeric. Only used in Header Segment (Segment 00)
Requirements:
Requirement Requirement Description
1 Indicates the LIBRS Spec is to be used by WinLIBRS when validating a data submission
LIBRS/NIBRS Mandatories
Error Messages
Structure for Numbering of Mandatory Error Messages
1st Character 2nd Character 3rd Character 4th and 5th Characters
8 1 0 00: Overall Data Element Edits all Sections (Except Section 4)
01 - 21
Denotes Mandatory Error Message Section with Mandatory Error Message Number within Section
Data Elemeber Specific Edits Within Section 4
Section (1) Error Message for: Initial Incident Reports
Each incident MUST have the following data elements, or the ENTIRE incident will be REJECTED:
Requirements:
Error
Requirement Requirement Description Error Message
Number
0 Incident missing a mandatory data element required for all incident submissions. 81000
EXCEPTIONAL CLEARANCE DATE IS REQUIRED
Exceptional Clearance Date (5) is required if this incident has any code, except None (N), in
1 81100 IF THIS INCIDENT HAS ANY CODE EXCEP T ‘N’
Cleared Exceptionally (4).
IN DE 4 ‘
WHEN TYPE OF VICTIM(DE 25) IS ‘I’ OR ‘L’ THE
When Type of Victim (25) is Individual (I) or Law Enforcement (L) the following data
2 81200 FOLLOWING DATA ELEMENT(S) MUST HAVE A
element(s) MUST have a valid code.
VALID CODE
WHEN TYPE OF VICTIM(DE 25) IS ‘I’ OR ‘L’ THE
When Offender Sequence Number (36) is NOT ‘000’, the following data elements MUST
3 81200 FOLLOWING DATA ELEMENT(S) MUST HAVE A
have a valid code.
VALID CODE
When Offender Sequence Number (36) is ‘000’, then Offender Suspected of Using/Gaming
WHEN DE 36 = 000 ‘, THEN DE 8 MUST BE ‘ N
4 Motivation (8) MUST be None (‘N’) and Bias Motivation/Bias Crime Type (8A) MUST be 81400
‘ AND DE 8A MUST BE ‘ 88 ‘.’
None (‘88’).
Details:
For Error Message 81000:
This edit should identify the missing data element, so the agency can determine which exact data element is missing. This edit applies to the following Data Elements:
ORI Number (1)
Incident Number (2)
Incident Date/Hour (3)
Cleared Exceptionally (4)
Offense Sequence Number (L6)
Louisiana Revised Statute (6)
Agency Supplied NIBRS Code (N6)*
Offense Attempted/Completed (7)
Offender Suspected of Using/Gaming Motivation (8)
Bias Motivation/Bias Crime Type (8A)
Location Type (9)
Victim Sequence Number (23)
Offense Connected to Victim Sequence Number (24)
Type of Victim (25).
* New data element not in previous LIBRS Specifications.
For Error Message 81200a:
This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to the following Data Elements:
Age of Victim [At Time Incident Occurred] (26)
Sex of Victim (27)
Race of Victim (28)
Ethnicity of Victim (29)
Resident Status of Victim (30)
Offender Sequence Number (36)
For Error Message 81200b:
This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to Data Elements:
Age of Offender [At Time Incident Occurred] (37)
Sex of Offender (38)
Race of Offender (39)
Section (2) Error Message for: Initial Incident Reports Containing Arrestee Segments
Requirements:
Error
Requirement Requirement Description Error Message
Number
ARREST SEGMENT IS MISSING A MANDATORY
0 Arrest Segment is missing a mandatory data element. 82000
DATA ELEMENT.
When Age of Arrestee (47) is LESS THAN ‘17’, then MUST have a valid code in WHEN DE 47 IS LESS THAN 17, MUST HAVE A
1 82100
Disposition of Arrestee Under 18 (52). VALID CODE IN DE 52.’
Details:
For Error Message 82000:
This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements:
Arrestee Sequence Number (40)
Arrest Number/Local Booking Number for Arrest (41)
Arrest Date (42)
Type of Arrest (43)
Multiple Arrestee Segment Indicator (44)
Louisiana Revised Statute of Arrest (45)
Arrestee Armed With [At Time of Arrest] (46)
Age of Arrestee [At Time of Arrest] (47)
Sex of Arrestee (48)
Race of Arrestee (49)
Ethnicity of Arrestee (50)
Resident Status of Arrestee (51)
Section (3) Error Message for: Subsequent Updates (ADD ARRESTs, MODIFYs, and DELETEs) to
Previously Submitted Incidents
Requirements:
Error
Requirement Requirement Description Error Message
Number
WHEN SUBMITTING AN ARRESTEE SEGMENT A
0 An Arrestee segment is missing a mandatory data element. 83100
MANDATORY DATA ELEMENT IS MISSING.
When Age of Arrestee (47) is LESS THAN ‘17’, then MUST have a valid code in WHEN DE 47 IS LESS THAN 17 ‘, MUST HAVE A VALID CODE
1 83200
Disposition of Arrestee Under 18 (52). IN DE 52.’
This segment must have valid data in ORI Number (1) and Incident Number THIS SEGMENT MUST HAVE A VALID CODE IN DE 1 AND DE
2 83000
(2). 2.
Details:
For Error Message 83100 and 83200:
Are for Updates (ADD ARREST/MODIFY/DELETE) of Arrestee Segments to the Initial Submission of Incident Data.
For Error Message 83100:
This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements:
Arrestee Sequence Number (40)
Arrest Number/Local Booking Number for Arrest (41)
Arrest Date (42)
Type of Arrest (43)
Multiple Arrestee Segment Indicator (44)
Louisiana Revised Statute of Arrest (45)
Arrestee Armed With [At Time of Arrest] (46)
Age of Arrestee [At Time of Arrest] (47)
Sex of Arrestee (48)
Race of Arrestee (49)
Ethnicity of Arrestee (50)
Resident Status of Arrestee (51)
NIBRS Mandatories
Subsection 01: ARSON (200)
Requirements:
Incidents submitted with an ARSON (Crime Against Property) offense (NIBRS Code “200”) should receive one of the following two error messages, as appropriate.
Error
Requirement Requirement Description Error Message
Number
When an Incident contains an offense of ARSON (NIBRS Code ‘200’) and Offense Attempted/Completed WHEN LRS = 200 AND DE 7 =
0 (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST contain a value of None (‘1’) or 84001 ‘A’, THEN DE 14 MUST BE A
Unknown (‘8’). CODE OF ‘1’ OR ‘8’
WHEN LRS = 200 AND DE 7 =
When an Incident contains an offense of ARSON (NIBRS Code ‘200’) and Offense Attempted/Completed
‘C’, THEN DE 14 MUST BE A
1 (DE 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST contain a value of Burned (‘2’), Property 84101
CODE OF ‘2’ AND DE 15 AND
Description (DE 15) MUST contain a valid code, and Value of Property (DE 16) MUST contain a valid value.
16 MUST HAVE A VALID CODE.
Subsection 02: AGGRAVATED ASSAULT, SIMPLE ASSAULT OR INTIMIDATION (13A, 13B and 13C)
Requirements:
Incidents submitted with an AGGRAVATED ASSAULT, SIMPLE ASSAULT OR INTIMIDATION (Crime Against Person) offense (NIBRS Code 13A, 13B or 13C) should receive one of the
following six error messages, as appropriate.
Error
Requirement Requirement Description Error Message
Number
When an Incident contains an offense of AGGRAVATED ASSAULT, SIMIPLE ASSAULT OR
WHEN LRS = 13A, 13B, OR 13C,
INTIMIDATION (NIBRS Code 13A, 13B or 13C), then Offense Attempted/Completed (DE 7)
0 84002 ATTEMTPED/COMPLETED (DE 7) MUST EQUAL
MUST contain a value of Completed (‘C’), and Type of Victim (DE 25) MUST contain a
‘C’, AND DE 25 MUST BE A CODE OF ‘I’ OR ‘L’
value of Individual (‘I’) or Law Enforcement Officer (‘L’).
When an Incident contains an offense of AGGRAVATED ASSAULT, SIMIPLE ASSAULT OR
WHEN LRS = 13A, 13B OR 13C AND DE 36 NOT
INTIMIDATION (NIBRS Code 13A, 13B or 13C), and Offender Sequence Number (DE 36) IS
1 84102 EQUAL TO 000, THEN DE 34 AND 35 MU ST
NOT EQUAL to ‘000’, then Offender Number to be Related (DE 34) and Relationship of
HAVE A VALID CODE.’
Victim to Offender (DE 35) MUST have valid codes.
When an Incident contains an offense of AGGRAVATED ASSAULT (NIBRS Code 13A) then
WHEN LRS = 13 A, DE 13, 31 & 33 MUST HAVE
2 Type of Weapon Involved (DE 13), Aggravated Assault/Homicide Circumstances (DE 31) 84202
A VALID CODE.
and Injury Type (DE 33) MUST have valid codes.
WHEN LRS = 13 A AND DE 25 = ‘L’ MUST HAVE
When an Incident contains an offense of AGGRAVATED ASSAULT (NIBRS Code 13A) and
THREE VALID CODES, ONE OF ‘02’ AND
Type of Victim (DE 25) is Law Enforcement Officer (‘L’), then Type of Officer
3 84302 ANOTHER VALID CODE OF ‘01’ OR ‘03-10’ AND
Activity/Circumstance (DE 25A) and Officer Assignment Type (DE 25B) MUST contain valid
ONE CODE OF ‘12-18’ IN DE 31 AND A CODE OF
values.
‘K-U’ IN DE 32
When an Incident contains an offense of SIMPLE ASSAULT (NIBRS Code 13B) then Type of WHEN LRS = 13 B, DE 13 MUST HAVE A VALID
4 Weapon/Force Involved (DE 13) MUST contain a valid value, and Type of Injury (DE 33) 84402 CODE AND DE 33 MUST HAVE A CODE OF ‘M’
MUST have a value of Apparent Minor Injury (‘M’) or None (‘N’). OR ‘N’.
WHEN LRS = 13 B AND DE 25 = ‘L’ MUST HAVE
When an Incident contains an offense of SIMPLE ASSAULT (NIBRS Code 13B) and Type of THREE VALID CODES, ONE OF ‘02’ AND
5 Victim (DE 25) is Law Enforcement Officer (‘L’), then Type of Officer Activity/Circumstance 84502 ANOTHER VALID CODE OF ‘01’ OR ‘03-10’ AND
(DE 25A) and Officer Assignment Type (DE 25B) MUST contain valid values. ONE CODE OF ‘12-18’ IN DE 31 AND A VALID
CODE OF ‘K-U’ IN DE 32
Subsection 03: BRIBERY (510)
Requirements:
Incidents submitted with an offense of BRIBERY (Crime Against Property) offense (NIBRS Code “510”) should receive the following five error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains an offense of BRIBERY (NIBRS Code 510), and Offense
WHEN LRS = 510 AND DE 7 = ‘A’, THEN DE 14
0 Attempted/Completed (DE 7) contains a value of Attempted (‘A’), then Type of Property 84003
MUST HAVE A CODE OF ‘1’ OR ‘8’.
Loss (DE 14) MUST contain a value of None (‘1’) or Unknown (‘8’).
When an Incident contains an offense of BRIBERY (NIBRS Code 510), and Offense
Attempted/Completed (DE 7) contains a value of Completed (‘C’), then Type of Property WHEN LRS = 510 AND DE 7 = C ‘, THEN DE 14
1 84103
Loss (DE 14) MUST contain a value of None (‘1’), Seized (‘5’), Stolen (‘7’) or Unknown MUST HAVE A CODE OF ‘ 1 ‘, ‘ 5 ‘, ‘ 7 ‘ OR ‘ 8 ‘.’
(‘8’).
When there is only one completed ‘Crime Against Property’ Offense in an incident, any
Property Description Segments (31) reported with the incident can contain ONLY values
of EITHER: WHEN THERE IS ONLY ONE COMPLETED
Stolen Property ('7') PROPERTY OFFENSE IN AN INCIDENT, A PROPER
2 84203
Unknown ('8') TY SEGMENT CAN CONTAIN A ‘7’ = STOLEN
PROPERTY OR AN ‘8’ = UNKNOWN.
The incident will be rejected if an agency sends both Stolen Property (‘7’) and Unknown
(‘8’) for Type of Property Loss/Etc. within the same incident.
When an Incident contains an offense of BRIBERY (NIBRS Code 510), and Type of
WHEN LRS = 510 AND DE 14 = ‘5’ OR ‘7’, THEN
3 Property Loss (DE 14) contains a value of Recovered (‘5’) or Stolen (‘7’), then Property 84303
DE 15 AND 16 MUST HAVE A VALID CODE.
Description (DE 15) and Value of Property (16) MUST contain valid data values.
When an Incident contains an offense of BRIBERY (NIBRS Code 510), and Type of
WHEN LRS = 510 AND DE 14 = ‘5’, THEN DE 17
4 Property Loss (DE 14) contains a value of Recovered (‘5’), then Date Recovered (DE 17) 84403
MUST HAVE A VALID DATE.
MUST contain a valid date.
Subsection 04: BURGLARY/BREAKING AND ENTERING (220)
Requirements:
Incidents submitted with a BURGLARY/BREAKING AND ENTERING (Crime Against Property) offense (NIBRS Code 220) should receive the following six error messages:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains an offense of BURGLARY/BREAKING AND ENTERING (NIBRS Code
WHEN LRS = 220 AND DE 9 = ‘14’ OR
220), and Location Type (DE 9) contains a value of Hotel/Motel (‘14’) or Rental Storage Facility
0 84004 ‘19’, THEN DE 10 AND 11 MUST HAVE A
(‘19’), then Number of Premises Entered (DE 10) and Method of Entry (DE 11) MUST contain valid
VALID CODE.
values.
When an Incident contains an offense of BURGLARY/BREAKING AND ENTERING (NIBRS Code
WHEN LRS = 220 AND DE 7 = ‘A’, THEN
1 220), and Offense Attempted/Completed (DE 7) = ‘A’, then Type of Property Loss (DE 14) MUST 84104
DE 14 MUST HAVE A CODE OF ‘1’ OR ‘8’.
have a value of None (‘1’) or Unknown (‘8’).
When an Incident contains an offense of BURGLARY/BREAKING AND ENTERING (NIBRS Code
WHEN LRS = 220 AND DE 7 = ‘C’, THEN
220), and Offense Attempted/Completed (DE 7) contains a value of Completed (‘C’), then Type of
2 84204 DE 14 MUST HAVE A CODE OF ‘1’, ‘5’, ‘7’
Property Loss (DE 14) MUST contain a value of None (‘1’), Seized (‘5’), Stolen (‘7’) or Unknown
OR ‘8’.
(‘8’).
WHEN THERE IS ONLY ONE COMPLETED
When there is ONLY ONE Crime Against Property offense with an Offense Attempted/Completed
PROPERTY OFFENSE IN AN INCIDENT, A
(DE 7) value of Completed (‘C’) within an incident, a Property Description Segment (DE 31) can
PROPER TY SEGMENT CAN CONTAIN A
contain either a Type of Property Loss (DE 14) value of Stolen (‘7’) or Unknown (‘8’), but NOT
3 84304 ‘7’ = STOLEN PROPERTY OR AN ‘8’ =
both. The incident MUST be rejected if an agency sends a Property Description Segment (DE 31)
UNKNOWN.THE IN CIDENT WILL REJECT
with both a Type of Property Loss (DE 14) of Stolen (‘7’) and Unknown (‘8’) within the same
IF AN AGENCY SENDS A ‘7’ AND ALSO
incident.
AN ‘8’ WITHIN THE SAM
When an Incident contains an offense of BURGLARY/BREAKING AND ENTERING (NIBRS Code WHEN LRS = 220 AND DE 14 = ‘5’ OR ‘7’,
4 220), and Type of Property Loss (DE 14) contains a value of Recovered (‘5’) or Stolen (‘7’), then 84404 THEN DE 15 & 16 MUST HAVE A VALID
Property Description (DE 15) and Value of Property (DE 16) MUST contain valid data values. CODE.
When an Incident contains an offense of BURGLARY/BREAKING AND ENTERING (NIBRS Code
WHEN LRS = 220 AND DE 14 = ‘5’, THEN
5 220), and Type of Property Loss (DE 14) contains a value of Recovered (‘5’), then Date Recovered 84504
DE 17 MUST HAVE A VALID DATE.
(DE 17) MUST contain a valid date.
Subsection 05: COUNTERFEITING/FORGERY (250)
Requirements:
Incidents submitted with a COUNTERFEITING/FORGERY (Crime Against Property) offense (NIBRS Code 250) should receive the following four error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
WHEN LRS = 250, DE 12
When an Incident contains an offense of COUNTERFEITING/FORGERY (NIBRS Code 250), then Type of Criminal
0 84005 MUST HAVE A VALID
Activity/Gang Information (12) MUST contain a valid value.
CODE.
WHEN LRS = 250 AND DE
When an Incident contains an offense of COUNTERFEITING/FORGERY (NIBRS Code 250) and Offense
7 = A ‘, THEN DE 14 MUST
1 Attempted/Completed (DE 7) = ‘A’, then Type of Property Loss (DE 14) MUST have a value of None (‘1’) or 84105
HAVE A CODE OF ‘ 1 ‘ OR ‘
Unknown (‘8’).
8 ‘.’
WHEN LRS = 250 AND DE
When an Incident contains an offense of COUNTERFEITING/FORGERY (NIBRS Code 250), and Offense
7 = ‘C’, THEN DE 14 MUST
Attempted/Completed (DE 7) contains a value of Completed (‘C’), then Type of Property Loss (DE 14) MUST
2 84205 HAVE A CODE OF ‘3’, ‘5’ OR
contain a value of Counterfeited/ Forged (‘3’), Recovered (‘5’) or Seized (‘6’), and Property Description (DE 15)
‘6’ AND DE 15 & 16 MUST
and Value of Property (DE 16) MUST contain valid values.
HAVE A VALID CODE.
WHEN LRS = 250 AND DE
When an Incident contains an offense of COUNTERFEITING/FORGERY (NIBRS Code 250), and Type of Property
3 84305 14 = ‘5’, THEN DE 17 MUST
Loss (DE 14) contains a value of Recovered (‘5’), then Date Recovered (DE 17) MUST have a valid date.
HAVE A VALID DATE.
Subsection 06: DESTRUCTION/DAMAGE/VANDALISM (290)
Requirements:
Incidents submitted with a DESTRUCTION/DAMAGE/VANDALISM (Crime Against Property) offense (NIBRS Code 290) should receive one of the following two error messages, as
appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains an offense of DESTRUCTION/DAMAGE/VANDALISM (NIBRS Code 290) and WHEN LRS = 290 AND DE 7
0 Offense Attempted/Completed (DE 7) = ‘A’, then Type of Property Loss (DE 14) MUST have a value of None 84006 = ‘A’, AND DE 14 MUST
(‘1’) or Unknown (‘8’). HAVE A CODE OF ‘1’ OR ‘8’.
WHEN LRS = 290 AND DE 7
When an Incident contains an offense of DESTRUCTION/DAMAGE/VANDALISM (NIBRS Code 290) and
= ‘C’ , THEN DE 14 MUST
Offense Attempted/Completed (DE 7) = ‘C’, then Type of Property Loss (DE 14) MUST have a value of
1 84106 HAVE A CODE OF ‘4’ AND DE
Destroyed/Damaged/Vandalized (‘4’) and Property Description (DE 15) and Value of Property (DE 16) MUST
15 & 16 MUST HAVE A VALID
contain valid values.
CODE.
Subsection 07: DRUG/NARCOTIC VIOLATION (35A) or DRUG EQUIPMENT VIOLATION (35B)
Requirements:
Incidents submitted with a DRUG/NARCOTIC VIOLATION (Crime Against Society) offense (NIBRS Code 35A) or DRUG EQUIPMENT VIOLATION (Crime Against Society) offense (NIBRS
Code 35B) should receive one of the following four error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
Incidents submitted with a DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) or DRUG EQUIPMENT
WHEN LRS = 35A OR 35B, DE
0 VIOLATION (NIBRS Code 35B), MUST contain a valid value in Type of Criminal Activity/Gang Information 84007
12 MUST HAVE A VALID CODE.
(DE 12).
WHEN LRS = 35 A OR 35 B
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) or DRUG
AND DE 7 =’A’, THEN DE 14
1 EQUIPMENT VIOLATION (NIBRS Code 35B) and Offense Attempted/Completed (DE 7) is Attempted (‘A’), 84107
MUST HAVE A CODE OF ‘1’ OR
then Type of Property Loss (DE 14) MUST have a value of None (‘1’) or Unknown (‘8’).
‘8’.
WHEN NIBRS = 35A OR 35B
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) or DRUG AND DE 7 = ‘C’, THEN OFFENSE
2 EQUIPMENT VIOLATION (NIBRS Code 35B) and Offense Attempted/Completed (DE 7) is Completed (‘C’), 84207 MUST RELATE TO SEGMENT
then Type of Property Loss (DE 14) MUST have a value of None ‘1’ or Seized ‘6’. 31’S WHOSE DE 14 HAS A
CODE OF ‘1’ OR ‘6’.
WHEN LRS = 35 A OR 35 B, DE
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) or DRUG
16 MUST HAVE A VALID CODE
EQUIPMENT VIOLATION (NIBRS Code 35B), then Type of Victim (DE 25) MUST be Society (‘S’). Also, Value
3 84307 ** * (OR MUST BE BLANK IF DE
of Property (DE 16) MUST contain a valid value; or MUST be BLANK (G) if Type of Property Loss (DE 14)
14 = ‘1 OR ‘8’) AND DE 25
contains None (‘1’) or Unknown (‘8’).
MUST BE ‘S’.
Incidents submitted with a DRUG/NARCOTIC VIOLATION (Crime Against Society) offense (NIBRS Code 35A) should receive the following three error messages:
Error
Requirement Requirement Description Error Message
Number
WHEN LRS = 35 A AND
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) and Type of Property DE 14 = ‘6’, THEN DE 15
0 84407
Loss (DE 14) is Seized ‘6’, then Property Description (DE 15) CANNOT BE EQUAL to Drug Narcotic Equipment ‘11’. CANNOT BE EQUAL TO
‘11’.
WHEN LRS = 35 A AND
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) and Type of Property DE 14 = ‘1’, THEN DE 20
1 84507
Loss (DE 14) is None ‘1’, then Suspected Drug Type (DE 20) MUST contain a valid value. MUST HAVE A VALID
CODE.
WHEN LRS = 35 A, DE 14
When an Incident contains an offense of DRUG/NARCOTIC VIOLATION (NIBRS Code 35A) and Type of Property = ‘6’ AND DE 15 = ‘10’,
2 Loss (DE 14) is Seized ‘6’, and Property Description (DE 15) is Drugs/Narcotics ‘10’, then Suspected Drug Type (DE 84607 THEN DE 20, 21 AND 22
20), Estimated Drug Quantity (DE 21) and Type Drug Measurement (DE 22) MUST all contain valid values. MUST HAVE A VALID
CODE.
WHEN LRS = 35 B AND
Incidents submitted with a DRUG EQUIPMENT VIOLATION (Crime Against Society) offense (NIBRS Code 35B) and
DE 14 = ‘6’, THEN DE 15
3 have a Type of Property Loss (DE 14) of Seized ‘6’, CANNOT contain a Property Description (DE 15) of 84707
CANNOT BE EQUAL TO
Drugs/Narcotics ‘10’.
‘10’.
Subsection 08: EXTORTION/BLACKMAIL (210)
Requirements:
Incidents submitted with a EXTORTION/BLACKMAIL (Crime Against Property) offense (NIBRS Code 210) should receive the following five error messages:
Error
Requirement Requirement Description Error Message
Number
Incidents submitted with an EXTORTION/BLACKMAIL (NIBRS Code 210) offense, MUST contain a valid value WHEN LRS = 210, DE 13 MUST
0 84008
in Type of Weapon/Force Involved (DE 13). HAVE A VALID CODE.
When an Incident contains an offense of EXTORTION/BLACKMAIL (NIBRS Code 210) and Offense WHEN LRS = 210 AND DE 7 =
1 Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a value of 84108 ‘A’, THEN DE 14 MUST HAVE A
None (‘1’) or Unknown (‘8’). CODE OF ‘1’ OR ‘8’.
WHEN LRS = 210 AND DE 7 =
When an Incident contains an offense of EXTORTION/BLACKMAIL (NIBRS Code 210) and Offense
‘C’, THEN DE 14 MUST HAVE A
Attempted/Completed (DE 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST have a value of
2 84208 CODE OF ‘5’ OR ‘7’ AND DE 15
Recovered (‘5’) or Stolen (‘7’) and Property Description (DE 15) and Value of Property (DE 16) MUST both
& 16 MUST HAVE A VALID
contain valid values.
CODE.
WHEN LRS = 210 AND DE 14 =
When an Incident contains an offense of EXTORTION/BLACKMAIL (NIBRS Code 210) and Type of Property
3 84308 ‘5’, THEN DE 17 MUST HAVE A
Loss (DE 14) is Recovered (‘5’), then Date Recovered (DE 17) MUST contain a valid date.
VALID DATE.
WHEN LRS = 210 AND DE 25 =
When an Incident contains an offense of EXTORTION/BLACKMAIL (NIBRS Code 210) and Type of Victim (DE
4 84408 ‘I’ OR ‘L’, THEN DE 33 MUST
25) is Individual (‘I’) or Law Enforcement Officer (‘L’), then Type of Injury (DE 33) MUST contain a valid value.
HAVE A VALID CODE.
Subsection 09: FRAUD OFFENSES (26A-E)
Requirements:
Incidents submitted with FRAUD OFFENSES (Crimes Against Property) (NIBRS Codes 26A-E) should receive the following three error messages:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains FRAUD OFFENSES (NIBRS Code 26A-E) and Offense Attempted/Completed WHEN LRS = 26A - E AND DE 7 =
0 (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a value of None (‘1’) or 84009 ‘A’, THEN DE 14 MUST HAVE A
Unknown (‘8’). CODE OF ‘1’ OR ‘8’.
When an Incident contains FRAUD OFFENSES (NIBRS Code 26A-E) and Offense Attempted/Completed WHEN LRS = 26 A - E AND DE 7 =
(DE 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST have a value of Recovered (‘5’) or C ‘, THEN DE 14 MUST HAVE A
1 84109
Stolen (‘7’) and Property Description (DE 15) and Value of Property (DE 16) MUST both contain valid CODE OF ‘ 5 ‘ OR ‘ 7 ‘ AND DE 15
values. & 16 MUST HAVE A VALID CODE.’
WHEN LRS = 26 A - E AND DE 14
When an Incident contains FRAUD OFFENSES (NIBRS Code 26A-E) and Type of Property Loss (DE 14) is
2 84209 = ‘5’, THEN DE 17 MUST HAVE A
Recovered (‘5’), then Date Recovered (‘17’) MUST contain a valid date.
VALID DATE.
Subsection 10: GAMBLING OFFENSES (39A-D)
Requirements:
Incidents submitted with GAMBLING OFFENSES (Crimes Against Society) (NIBRS Codes 39A-D) should receive one of the following two error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains GAMBLING OFFENSES (NIBRS Code 39A-D) and Offense WHEN LRS = 39 A - D AND DE 7 =
0 Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a value 84010 ‘A’, THEN DE 14 MUST HAVE A
of None (‘1’) or Unknown (‘8’). CODE OF ‘1’ OR ‘8’.
WHEN LRS = 39A - D AND DE 7 =
When an Incident contains GAMBLING OFFENSES (NIBRS Code 39A-D) and Offense
‘C’, THEN DE 14 MUST HAVE A
Attempted/Completed (DE 7) is Completed (‘C’), then Type of Property Loss (1DE 4) MUST contain a
1 84110 CODE OF ‘ 6 ‘, DE 15 & 16 MUST
value of Seized (‘6’), Property Description (DE 15) and Value of Property (DE 16) MUST contain valid
HAVE A VALID CODE, AND DE 25
values, and Type of Victim (DE 25) MUST be Society (‘S’).
MUST BE ‘ S ‘.’
Type of Criminal Activity/Gang Information (DE 12) MUST have a valid code when NIBRS Offense Code WHEN LRS = 39 C, DE 12 MUST
2 84210
is 39C. HAVE A VALID CODE.
Subsection 11: HOMICIDE OFFENSES (09A, 09B or 09C)
Requirements:
Incidents submitted with HOMICIDE OFFENSES (Crimes Against Persons) (NIBRS Codes 09A, 09B and 09C) should receive one of the following five error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains HOMICIDE OFFENSES (NIBRS Code 09A, 09B and 09C), then Offense WHEN LRS = 09A, 09B OR 09C, DE 7
Attempted/Completed (DE 7) MUST contain Completed (‘C’), Type of Weapon/Force Involved MUST EQUAL ‘C’, DE 13 & 31 MUST HAVE
0 84011
(DE 13) and Aggravated Assault/Homicide Circumstance (DE 31) MUST contain valid values, and A VALID CODE, AND DE 25 MUST EQUAL
Type of Victim (DE 25) MUST be an Individual (‘I’) . ‘I’ OR ‘L’.
When an Incident contains HOMICIDE OFFENSES (NIBRS Code 09A, 09B and 09C) and Offender WHEN LRS = 09 A, 09 B OR 09 C, IF DE 36
1 Sequence Number (DE 36) is NOT EQUAL to ‘000’, then Offender Number to be Related (DE 34) 84111 NOT EQUAL TO 000 ‘, THEN DE 34 AND
and Relationship of Victim to Offender (DE 35) MUST have valid values. 35 MUST HAVE A VALID CODE.’
Incidents submitted with a JUSTIFIABLE HOMICIDE (NIBRS Codes 09C) offense MUST contain an
Aggravated Assault/Homicide Circumstance (DE 31) value of Criminal Killed by Private Citizen
(‘20’) or Criminal Killed by Police Officer (‘21’), and Additional Justifiable Homicide
Circumstances (DE 32) MUST contain one of the following values:
'A' (Criminal Attacked Police Officer and That Officer Killed Criminal)
WHEN LRS = 09 C, DE 31 MUST HAVE ‘20’
'B' (Criminal Attacked Police Officer and Criminal Killed by Another Police Officer)
2 84211 OR ‘21’ AND DE 32 MUST HAVE A VALID
'C' (Criminal Attacked by Civilian)
CODE OF ‘A-G’.
'D' (Criminal Attempted Flight from a Crime)
'E' (Criminal Killed in the Commission of a Crime)
'F' (Criminal Resisted Arrest)
'G' (Unable to Determine/Not Enough Informatioin.
WHEN LRS = 09 A AND DE 25 = ‘L’, MUST
Incidents submitted with a MURDER OR NONNEGLIGENT MANSLAUGHTER (NIBRS Codes 09A)
HAVE TWO VALID CODES;ONE CODE ‘01’
offense and where Type of Victim (DE 25) contains Law Enforcement Officer (‘L’), then Type of
3 84311 OR ‘03-10’ AND ONE CODE OF ‘12-18’ IN
Officer Activity/Circumstance (DE 25A) and Officer Assignment Type (DE 25B) MUST contain
DE 31 AND A VALID CODE OF ‘K-U’ IN
valid values.
DATA ELEMENT 32.
WHEN LRS = 09 B AND DE 25 = ‘L’, MUST
Incidents submitted with a NEGLIGENT MANSLAUGHTER (NIBRS Codes 09B) offense and where
HAVE TWO VALID CODES;ONE CODE OF
Type of Victim (DE 25) contains Law Enforcement Officer (‘L’), then Type of Officer
4 84411 ‘30-34’ AND ONE CODE OF ‘12-18’ IN DE
Activity/Circumstance (DE 25A) and Officer Assignment Type (DE 25B) MUST contain valid
31 AND A VALID CODE OF ‘K-U’ IN DATA
values.
ELEMENT 32
Subsection 12: KIDNAPPING/ABDUCTION (100)
Requirements:
Incidents submitted with KIDNAPPING/ABDUCTION (Crimes Against Person) (NIBRS Code 100) should receive one of the following eight error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100), THEN
0 84012 WHEN LRS = 100, DE 13 MUST HAVE A VALID CODE.
Type of Weapon/Force Involved (DE 13) MUST contain a valid value.
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100) and
WHEN LRS = 100 AND DE 7 = A ‘, THEN DE 14 MUST
1 Offense Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property 84112
HAVE A CODE OF ‘ 1 ‘ OR ‘ 8 ‘. ‘
Loss (DE 14) MUST have a value of None (‘1’) or Unknown (‘8’).
When an Incident contains an offense of KIDNAPPING/ABDUCTION (NIBRS Code
100) and Offense Attempted/Completed (DE 7) is Completed (‘C’), then Type of WHEN LRS = 100 AND DE 7 = ‘C’, THEN DE 14 MUST
2 84212
Property Loss (DE 14) MUST have a value of None (‘1’), Recovered (‘5’), Stolen HAVE A CODE OF ‘1’, ‘5’, ‘7’, OR ‘8’.
(‘7’) or Unknown (‘8’).
WHEN THERE IS ONLY ONE COMPLETED PROPERTY
When there is only ONE COMPLETED PROPERTY OFFENSE in an incident, a
OFFENSE IN AN INCIDENT, A PROP - ERTY SEG.CAN
property segment can contain a ‘7’ = Stolen Property or an ‘8’ = Unknown. The
3 84312 CONTAIN A ‘7’ = STOLEN PROPERTY OR AN ‘8’ =
incident will reject if an agency sends a ‘7’ and also an ‘8’ within the same
UNKNOWN.THE INCIDENT WILL REJECT IF AN AGENCY
incident, when there is only one completed property offense within the incident.
SENDS A ‘7’ AND ALSO AN ‘8’ WITHIN THE SA
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100) and
WHEN LRS = 100 AND DE 14 EQUALS TO ‘5’ OR ‘7’, THEN
4 Type of Property Loss (DE 14) is Recovered (‘5’) or Stolen (‘7’), then Property 84412
DE 15 AND 16 MUST HAVE A VALID CODE.
Description (DE 15) and Value of Property (DE 16) MUST contain valid values.
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100) and
WHEN LRS = 100 AND DE 14 = ‘5’, THEN DE 17 MUST
5 Type of Property Loss (DE 14) is Recovered (‘5’), then Date Recovered (DE 17) 84512
HAVE A VALID DATE.
MUST contain a valid date.
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100) and
WHEN LRS = 100 AND DE 25 EQUALS TO ‘I’ OR ‘L’, THEN
6 Type of Victim (DE 25) is Individual (‘I’) or Law Enforcement Officer (‘L’), then 84612
DE 33 MUST HAVE A VALID CODE.
Type of Injury (DE 33) MUST contain a valid value.
When an Incident contains KIDNAPPING/ABDUCTION (NIBRS Code 100) and
Offender Sequence Number (DE 36) IS NOT EQUAL to ‘000’, then Offender WHEN LRS = 100 AND DE 36 IS NOT EQUAL TO ‘000’, DE
7 84712
Number to be Related (DE 34) and Relationship of Victim to Offender (DE 35) 34 AND 35 MUST HAVE A VALID CODE.
MUST contain valid values.
Subsection 13: LARCENY/THEFT OFFENSES (23A-H)
Requirements:
Incidents submitted with LARCENY/THEFT OFFENSES (NIBRS Codes 23A-H) or EMBEZZLEMENT (NIBRS Code 270) offenses (both Crimes Against Property) should receive the following
three error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
WHEN LRS = 23 A - H OR 270
When an Incident contains LARCENY/THEFT OFFENSES (NIBRS Codes 23A-H) or EMBEZZLEMENT (NIBRS
AND DE 7 = ‘A’, THEN DE 14
0 Code 270) offenses, and Offense Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property 84013
MUST HAVE A CODE OF ‘1’ OR
Loss (DE 14) MUST have a value of None (‘1’) or Unknown (‘8’).
‘8’.
WHEN LRS = 23 A - H OR 270
When an Incident contains LARCENY/THEFT OFFENSES (NIBRS Codes 23A-H) or EMBEZZLEMENT (NIBRS
AND DE 7 = C ‘, THEN DE 14
Code 270) offenses, and Offense Attempted/Completed (DE 7) is Completed (‘C’), then Type of Property
1 84113 MUST HAVE A CODE OF ‘ 5 ‘ OR
Loss (DE 14) MUST have a value of Recovered (‘5’) or Stolen (‘7’), and. Property Description (15) and Value
‘ 7 ‘ AND DE 15 & 16 MUST
of Property (16) MUST contain valid values.
HAVE A VALID CODE.’
When an Incident contains LARCENY/THEFT OFFENSES (NIBRS Codes 23A-H) or EMBEZZLEMENT (NIBRS WHEN LRS = 23 A - H OR 270
2 Code 270) offenses, and Type of Property Loss (DE 14) is Recovered (‘5’), then Date Recovered (DE 17) 84213 AND DE 14 = ‘5’, THEN DE 17
MUST contain a valid date. MUST HAVE A VALID DATE.
Subsection 14: MOTOR VEHICLE THEFT (240)
Requirements:
Incidents submitted with MOTOR VEHICLE THEFT (Crimes Against Property) (NIBRS Code 240) should receive one of the following five error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains a MOTOR VEHICLE THEFT (NIBRS Code 240) offense and Offense WHEN LRS = 240 AND DE 7 = ‘A’,
0 Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a 84014 THEN DE 14 MUST HAVE A CODE OF
value of None (‘1’) or Unknown (‘8’). ‘1’ OR ‘8’.
When an Incident contains a MOTOR VEHICLE THEFT (NIBRS Code 240) offense and Offense WHEN LRS = 240 AND DE 7 = C ‘,
Attempted/Completed (DE 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST have a THEN DE 14 MUST HAVE A CODE OF ‘
1 84114
value of Recovered (‘5’) or Stolen (‘7’), and. Property Description (DE 15) and Value of Property (DE 5 ‘ OR ‘ 7 ‘ AND DE 15 & 16 MUST
16) MUST contain valid values. HAVE A VALID CODE.’
WHEN LRS = 240 AND DE 14 = ‘5’,
When an Incident contains a MOTOR VEHICLE THEFT (NIBRS Code 240) offense, and Type of
THEN DE 15 MUST HAVE A VALID
2 Property Loss (DE 14) is Recovered (‘5’), then Property Description (DE 15) MUST contain a valid 84214
CODE, AND DATA ELEMENT 17 MUST
value and Date Recovered (DE 17) MUST contain a valid date.
HAVE A VALID DATE.
When an Incident contains a MOTOR VEHICLE THEFT (NIBRS Code 240) offense, and Type of
Property Loss (DE 14) is Recovered (‘5’), then Property Description (15) MUST contain one of the
following codes,
'03' (Automobiles) WHEN LRS = 240 AND DE 14 = ‘5’, IF
'05' (Buses) DE 15 HAS A CODE OF ‘03, ‘ 05 ‘, ‘ 24
3 '24' (Other Motor Vehicles) 84314 ‘, ‘ 28 ‘, OR ‘ 37 ‘, THEN DATA
'28' (Recreational Vehicles) ELEMENT 19 MUST HAVE A VALID
'37' (Trucks) CODE.
and Number of Recovered Vehicles (DE 19) MUST contain a valid value.
When an Incident contains a MOTOR VEHICLE THEFT (NIBRS Code 240) offense, and Type of
Property Loss (DE 14) is Stolen (‘7’), then Property Description (DE 15) MUST contain one of the
following codes,
'03' (Automobiles) WHEN LRS = 240 AND DE 14 = ‘7’,
'05' (Buses) THEN DE 15 MUST HAVE A CODE OF
4 '24' (Other Motor Vehicles) 84414 ‘03’, ‘05’, ‘24’, ‘28’, OR ‘37’ AND DATA
'28' (Recreational Vehicles) ELEMENT 18 MUST HAVE A VALID
'37' (Trucks) CODE.
and Number of Stolen Vehicles (DE 18) MUST contain a valid value.
Subsection 15: PORNOGRAPHY/OBSCENE MATERIAL OFFENSES (370)
Requirements:
Incidents submitted with PORNOGRAPHY/OBSCENE MATERIAL OFFENSES (Crimes Against Society) (NIBRS Code 370) should receive the following error message, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When NIBRS Offense Code is 370 the following MUST be true:
Type of Criminal Activity/Gang Information (DE 12) MUST
WHEN LRS = 370, DE 12 MUST HAVE A VALID CODE AND DE 25
0 have a valid code. 84015
MUST EQUAL ‘S’.
Type of Victim (DE 25) MUST be Society ('S').
Subsection 16: PROSTITUTION OFFENSES (40A, 40B)
Requirements:
Incidents submitted with PROSTITUTION OFFENSES (Crimes Against Society) (NIBRS Codes 40A and 40B) should receive the following error message, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains PROSTITUTION OFFENSES (NIBRS Code 40A AND 40B), then Type of WHEN LRS = 40A OR 40B, DE 25
0 84016
Victim (DE 25) MUST be Society (‘S’). MUST EQUAL ‘S’.
Subsection 17: ROBBERY OFFENSES (120)
Requirements:
Incidents submitted with ROBBERY OFFENSES (Crimes Against Property) (NIBRS Code 120) should receive one of the following six error messages:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120), then Type of Weapon/Force Involved WHEN LRS = 120, DE 13 MUST
0 84017
(DE 13) MUST contain a valid value. HAVE A VALID CODE.
WHEN LRS = 120 AND DE 7 =
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120) and Offense Attempted/Completed (DE
1 84117 A ‘, THEN DE 14 MUST HAVE A
7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a value of None (‘1’) or Unknown (‘8’).
CODE OF ‘ 1 ‘ OR ‘ 8 ‘. ‘
WHEN LRS = 120 AND DE 7 =
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120) and Offense Attempted/Completed (DE ‘C’, THEN DE 14 MUST HAVE A
2 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST have a value of Recovered (‘5’) or Stolen 84217 CODE OF ‘5’ OR ‘7’ AND DE 15
(‘7’), and. Property Description (15) and Value of Property (DE 16) MUST contain valid values. & 16 MUST HAVE A VALID
CODE.
WHEN LRS = 120 AND DE 14 =
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120) and Type of Property Loss (DE 14) is
3 84317 ‘5’, THEN DE 17 MUST HAVE A
Recovered (‘5’), then Date Recovered (DE 17) MUST contain a valid date.
VALID DATE.
WHEN LRS = 120 AND DE 25 =
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120) and Type of Victim (DE 25) is Individual
4 84417 ‘I’ OR ‘L’, THEN DE 33 MUST
(‘I’) or Law Enforcement Officer (‘L’), then Type of Injury (DE 33) MUST contain a valid value.
HAVE A VALID CODE.
WHEN LRS = 120 AND DE 25 =
When an Incident contains ROBBERY OFFENSES (NIBRS Code 120) and Type of Victim (DE 25) is Individual
‘I’ OR ‘L’ AND DE 36 NOT
(‘I’) or Law Enforcement Officer (‘L’) and Offender Sequence Number (DE 36) IS NOT EQUAL to ‘000’, then
5 84517 EQUAL TO ‘000’, THEN DE 34
Offender Number to be Related (DE 34) and Relationship of Victim to Offender (DE 35) MUST contain valid
AND 35 MUST HAVE A VALID
values.
CODE.
Subsection 18: SEX OFFENSES – FORCIBLE (11A-D)
Requirements:
Incidents submitted with SEX OFFENSES - FORCIBLE (Crimes Against Persons) (NIBRS Codes 11A-D) should receive the following two error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When NIBRS Offense Code is 11A, 11B, 11C, or 11D, then:
WHEN LRS = 11 A - 11 D OR 64 A OR 64 B,
Type of Weapon/Force Involved (DE 13) must have a value
DE 13 MUST HAVE A VALID CODE, DE 25
0 Victim Type (DE 25) must be either 'I - Individual' or 'L - Law Enforcement 84018
MUST HAVE A ‘I’ OR ‘L’, AND DE 33 MUST
Injury Type (DE 33) must have a value
HAVE A VALID CODE.
When an Incident contains SEX OFFENSES – FORCIBLE (NIBRS Code 11A-D), and Offender WHEN LRS = 11 A - 11 D OR 64 A OR 64 B
1 Sequence Number (DE 36) IS NOT EQUAL to ‘000’, then Offender Number to be Related (DE 84118 AND 36 NOT EQUAL TO 000 ‘, THEN DE 34
34) and Relationship of Victim to Offender (DE 35) MUST contain valid values. AND 35 MUST HA VE A VALID CODE.’
Subsection 19: SEX OFFENSES – NON-FORCIBLE (36A-36B)
Requirements:
Incidents submitted with SEX OFFENSES – NON-FORCIBLE (Crimes Against Persons) (NIBRS Codes 36A or 36B) should receive the following two error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When an Incident contains SEX OFFENSES – NON-FORCIBLE (NIBRS Codes 36A or 36B), then Type of WHEN LRS = 36A OR 36B, DE 25
0 84019
Victim (DE 25) MUST be Individual (‘I’) or Law Enforcement Officer (‘L’). MUST HAVE A ‘I’ OR ‘L’.
WHEN LRS = 36 A OR 36 B AND
When an Incident contains SEX OFFENSES – NON-FORCIBLE (NIBRS Codes 36A or 36B) and Offender
DE 36 NOT EQUAL TO 000 ‘, THEN
1 Sequence Number (DE 36) IS NOT EQUAL to ‘000’, then Offender Number to be Related (DE 34) and 84119
DE 34 AND 35 MUS T HAVE A
Relationship of Victim to Offender (DE 35) MUST contain valid values.
VALID CODE.’
Subsection 20: STOLEN PROPERTY OFFENSES (280)
Requirements:
Incidents submitted with STOLEN PROPERTY OFFENSES (Crimes Against Property) (NIBRS Code 280) should receive one of the four following error messages, as appropriate:
Error
Requirement Requirement Description Error Message
Number
When NIBRS Offense Code is 280 the following MUST be true::
WHEN LRS = 280, DE 12
0 Type of Criminal Activity/Gang Information (DE 12) MUST have a valid code. 84020
MUST HAVE A VALID CODE.
When an Incident contains STOLEN PROPERTY OFFENSES (NIBRS Code 280), and Offense WHEN LRS = 280 AND DE 7 =
1 Attempted/Completed (DE 7) is Attempted (‘A’), then Type of Property Loss (DE 14) MUST have a value of 84120 A ‘, THEN DE 14 MUST HAVE
None (‘1’) or Unknown (‘8’). A CODE OF ‘ 1 ‘ OR ‘ 8 ‘. ‘
When an Incident contains STOLEN PROPERTY OFFENSES (NIBRS Code 280), and Offense WHEN LRS = 280 AND DE 7 =
2 Attempted/Completed (DE 7) is Completed (‘C’), then Type of Property Loss (DE 14) MUST have a value of 84220 ‘C’, THEN DE 14 MUST HAVE
None (‘1’) or Recovered (‘5’). A CODE OF ‘1’ OR ‘5’.
When an Incident contains STOLEN PROPERTY OFFENSES (NIBRS Code 280) and Type of Property Loss (DE WHEN LRS = 280 AND DE 14
3 14) is Recovered (‘5’), then Property Description (DE 15), Value of Property (DE 16) and Date Recovered (DE 84320 = ‘5’, THEN DE 15, 16 & 17
17) MUST all contain valid values. MUST HAVE A VALID CODE.
Subsection 21: WEAPONS LAW VIOLATIONS (520)
Requirements:
Error
Requirement Requirement Description Error Message
Number
When NIBRS Offense Code is 520 the following MUST be
true:
Type of Criminal Activity/Gang Information (DE
12) WHEN LRS = 520, DE 12 & DE 13 MUST HAVE A VALID CODE AND DE 25
0 84021
Type of Weapon/Force Involved (DE 13) MUST MUST BE EQUAL TO ‘S’
have a valid code
Type of Victim (DE 25) MUST be Society ('S').
Source: LIBRS Validation Specifications.docx