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:

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

Segment 00 Errors and Explanations

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

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

Segment 10 Errors and Explanations

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

Segment 11 Errors and Explanations

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

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

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.

Note: There should only be ONE Segment 30 per Incident

Segment Layout

Segment 30 Errors and Explanations

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

Segment 31 Errors and Explanations

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

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

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

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.

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

Segment 40 Errors and Explanations

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

Segment 41 Errors and Explanations

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

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

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:

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

Segment 51 Errors and Explanations

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

Segment 52 Errors and Explanations

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

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

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

Segment 61 Errors and Explanations

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

Segment 62 Errors and Explanations

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

Segment 63 Errors and Explanations

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

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’, and the full line would read ‘99000512ZZ’ (plus Padding to make 150 characters).

Segment 99 Errors and Explanations

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:

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:

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:

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:

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:

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.

Examples:

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:

Examples:

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:

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:

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

Requirements:

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:

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:

Hard-Coded Edits for LRS Codes Without a Property Description-Based Qualifier:

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

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:

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:

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.

Examples:

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:

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

Examples:

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:

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

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:

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:

Examples:

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:

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:

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:

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:

Examples:

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:

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.

Examples (Criminal Activity):

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:

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. ___

Examples (Gang Information):

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 :

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:

Examples:

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 :

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 :

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 :

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:

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 :

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.

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 :

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:

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:

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:

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:

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:

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

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:

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:

Details:

• Type Drug Measurement (22) indicates how Seized drugs and narcotics are quantified in a drug case.

Allowed Entries:

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:

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:

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.

Examples:

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:

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

Example:

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:

Allowed Entries:

Enter only one (1) code for each Victim Segment:

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:

Allowed Entries:

Enter only one (1) code for each Victim Segment:

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

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:

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:

Example:

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:

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:

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: