Table of Contents. September, 2016 LIBRS Specifications, Rel

Transcription

1 Table of Contents Table of Contents Segment Layouts... 5 Submission Header (00) *** Modified (New Data Elements) ***... 7 Administrative (10)... 8 Administrative Modification (11)... 9 Offense (20) Property (30) Property Description (31) Property Modification (32) Property/Offense (33) *** New Segment *** Offender (40) Offender Using/Gaming Motivation (41) Victim (50) Victim Injury (51) Victim/Offender Relation (52) Arrestee (60) Arrestee Armed (61) Arrestee Statute (62) Arrestee Modification (63) Submission Trailer (99) Zero Records (01) Control Data Element Definitions Segment Descriptor (C1) Submitting Agency (C2) Submission Date (C3) Reporting Period (C4) Action Type (C5) Clearance Indicator (C6) [for Time-Window Submission Only] Number of Segments Transferred (C7) End of Segment Marker (C8) Padding (C9) Software ID (C10) *** New Data Element *** Software Version (C11) *** New Data Element *** Data Element Definitions ORI Number (1) Incident Number (2) Incident Date/Hour (3) ClearedExceptionally (4) Exceptional Clearance Date (5) Offense Sequence Number (L6) Louisiana Revised Statute (6) September, 2016 LIBRS Specifications, Rel

2 Offense Attempted/Completed (7) Offender Suspected of Using / Gaming Motivation (8) Bias Motivation/Bias Crime Type (8A) Location Type (9) Number of Premises Entered (10) Method of Entry (11) Type of Criminal Activity/Gang Information (12) Type of Weapon/Force Involved (13) Property Sequence Number (P1) *** New Data Element *** Type of Property Loss (14) Property Description (15) Value of Property (16) Date Recovered (17) Number of Stolen Vehicles (18) Number of Recovered Motor Vehicles (19) Suspected Drug Type (20) Estimated Drug Quantity (21) Type Drug Measurement (22) Victim Sequence Number (23) Offense Connected to Victim Sequence Number (24) Type of Victim (25) Age of Victim [At Time Incident Occurred] (26) Date of Birth of Victim (L26) Sex of Victim (27) Race of Victim (28) Ethnicity of Victim (29) Resident Status of Victim (30) Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In Line of Duty) Type of Assignment (31) Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In Line of Duty) Type of Activity (32) Type of Injury (33) Offender Number to be Related (34) Relationship of Victim to Offender (35) Offender Sequence Number (36) Age of Offender [At Time the Incident Occurred] (37) Date of Birth of Offender (L37) Sex of Offender (38) Race of Offender (39) Arrestee Sequence Number (40) Arrestee Name (L40) Arrest Number / Local Booking Number for Arrest (41) Arrest Date (42) Type of Arrest (43) Multiple Arrestee Segment Indicator (44) September, 2016 LIBRS Specifications, Rel

3 Louisiana Revised Statute of Arrest (45) Arrest Connection to Offense (L45) Arrestee Was Armed With [At Time of Arrest] (46) Age of Arrestee [At Time of Arrest] (47) Date of Birth of Arrestee (L47) Sex of Arrestee (48) Race of Arrestee (49) Ethnicity of Arrestee (50) Resident Status of Arrestee (51) Disposition of Arrestee Under 17 (52) Location of Incident [Geographical Coordinates] (L53) Station/Division/Precinct Identifier (L54) Arrest Transaction Number (ATN) for Louisiana (L55) LIBRS Segment Overview Diagram... Foldout LIBRS 2.1 Segments and Data Elements Diagram... Foldout September 2016 LIBRS Specifications, Rel

4 September, 2016 LIBRS Specifications, Rel

5 Segment Layouts September 2016 LIBRS Specifications, Rel

6 September, 2016 LIBRS Specifications, Rel

7 Submission Header (00) *** Cells Shaded Brown are either New or Modified Data Elements, beginning with LIBRS 2.2 *** Data Element Description of Data Element Position(s) Length Format Number C1 Segment Descriptor N C2 Submitting Agency A C3 Submission Date D C4 Reporting Period D C10 Software ID ***New*** A/N C11 Software Version ***New*** A/N ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Zero-Reporting Month is not A Segment 00 was submitted that had an invalid reporting month in positions The data entered must be a valid month of 01 through Zero-Reporting Year is Invalid. A Segment 00 was submitted that did not have four numeric digits in positions Zero-Reporting Month/Year submitted prior to the "Base Date." A Segment 00 was submitted with a month and year entered into positions that is either earlier than January 1 of the previous year or before the date the agency began submitting data to LIBRS Zero-Reporting Month/Year Exceeded Month/Year of Submission. A Segment 00 was submitted with a month and year entered into positions that was later than the "Month of Submission" and "Year of Submission" entered into positions September 2016 LIBRS Specifications, Rel

8 Administrative (10) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A L53 Location of Incident (Geographical Coordinates) A/N L54 Station/Division/Precinct Identifier A 3 Incident Date/Hour A 4 Cleared Exceptionally 54 1 A 5 Exceptional Clearance Date D ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number... Error and Explanation First segment, after the Submission Header, in a data submission MUST be an Administrative Segment (10). CANNOT have an initial record other than an Administrative Segment Missing a Mandatory Record Segment for a Complete Incident. When an Action Type of Incident Report ("I") is submitted, the following segments MUST be included: 10 - Administrative Segment 20 - Offense Segment 40 - Offender Segment 41 - Offender Using Segment/Gaming Motivation 50 - Victim Segment. One or more of these segments was missing. September, 2016 LIBRS Specifications, Rel

9 Administrative Modification* (11) * For Time-Window Submissions, Only. Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 6 Louisiana Revised Statute Number A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Incident not on File. Administrative Segment (10 and 11) submitted with an Action Type of "M" (MODIFY) must already be on file with ORI Number (Data Element No. 1) and Incident Number (Data Element No Time-Window (Segment 11) being modified must have Louisiana Revised Statute Number (LRS No.). September 2016 LIBRS Specifications, Rel

10 Offense (20) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A L6 Offense Sequence Number N 6 Louisiana Revised Statute Number A 7 Offense Attempted/Completed 40 1 A 24 Offense Connected to Victim Sequence Number N 9 Location Type N 10 Number of Premises Entered A/N 11 Method of Entry 48 1 A Type of Criminal Activity/Gang Information No. 1 Type of Criminal Activity/Gang Information No A 50 1 A 12 Type of Criminal Activity No A 13 Type of Weapon/Force Involved No A 13 Type of Weapon/Force Involved No A 13 Type of Weapon/Force Involved No A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Note: Submit one Offense Segment for each LRS Code, and one for each Victim in an Incident. Error Number Error and Explanation MUST submit an Offense Segment (20) for each victim. September, 2016 LIBRS Specifications, Rel

11 Data Element Number Property (30) Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 18 Number of Stolen Motor Vehicles A/N 19 Number of Recovered Motor Vehicles A/N ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Property Segments (30 and 31) must exist when an Incident Report (Action Type = "I") is submitted with an Offense Segment (20) whose LRS is a "Crime Against Property." Kidnaping (100), Gambling (39A thru 39D), or Drug/Narcotic (35A thru 35B) Offenses also have this same Property Segment requirement. Error Message: In this case no Property Segments were submitted Only offenses that are "Crimes Against Property," Kidnaping (100), Gambling (39A thru 39D), or Drug/Narcotic (35A thru 35B) can be submitted with Property Segments. Error Message: Property Segments (Segment 30 and 31) CANNOT exist with offenses submitted. September 2016 LIBRS Specifications, Rel

12 Property Description (31) *** Cells Shaded Brown are either New or Modified Data Elements, beginning with LIBRS 2.2 *** Data Element Description of Data Element Position(s) Length Format Number C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 14 Type of Property Loss / Etc N 15 Property Description Type A/N 16 Value of Property N 17 Date Recovered D 20 Suspected Drug Type A 21 Estimated Drug Quantity A/N 22 Type Drug Measurement A P1 Property Sequence Number***New*** N ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N September, 2016 LIBRS Specifications, Rel

13 Property Modification* (32) * For Time-Window Submissions, Only. Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type ( W or M, only) 3 1 A 1 ORI Number A 2 Incident Number A 6 Louisiana Revised Statute Number A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation A Time-Window submission (Action Type of "W") or Modify submission (Action Type = "M") was submitted for "Recovered Property" on a Property Modification Segment (32). When submitted, all LRS codes must be Crimes Against Property, Kidnaping (100), or Gambling (39A thru 39D). In this instance offense codes other than those mentioned were submitted. Error Message: Gambling, Kidnaping and "Crimes Against Property" are the only valid offenses Property Segment A-O-F (already on file) added on (MMDDYYYY) Recovery Date = (MMDDYYYY) September 2016 LIBRS Specifications, Rel

14 Property/Offense (33) ***New*** Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A P1 Property Sequence Number A L6 Offense Sequence Number A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N The Property/Offense Segment is new to LIBRS 2.2, and 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), which is also new to LIBRS 2.2, and the Offense Sequence Number (Data Element L6). September, 2016 LIBRS Specifications, Rel

15 ***New***Property/Offense (33) INVALID Combinations of NIBRS Offense Codes and Property Descriptions Invalid Property Descriptions NIBRS Codes A 23B 23C 23D 23E 23F 23G 23H 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 It is illogical for various NIBRS Offense Codes (Data Element 6) to be connected to properties 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 above shows invalid combinations of NIBRS Offense Codes and Property Descriptions. Cells that are shaded brown represent INVALID combinations of NIBRS Offense codes and Property Descriptions. September 2016 LIBRS Specifications, Rel

16 Offender (40) Data Element Number Error Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 36 Offender Sequence Number N 37 Age of Offender A L37 Date of Birth of Offender D 38 Sex of Offender 39 1 A 39 Race of Offender 40 1 A 8A Bias Motivation / Bias Crime Type A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error and Explanation For First Degree Rape (NIBRS Code 11A) and Statutory Rape (NIBRS Code 36B), the Age of Offender (37) MUST be at least seventeen (17) years of age or older Statutory Rape Offenses (NIBRS Code 36B) require Offenders to be at least two years older than their victims A Statutory Rape (NIBRS Code 36B) MUST be classified as a MISDEMEANOR (LRS 14:80.1 Misdemeanor Carnal Knowledge of a Juvenile) if the Offender is at least two (2), but less than four (4) years older than the Victim A Statutory Rape (NIBRS Code 36B) MUST be classified as a FELONY (LRS 14:80.1 Misdemeanor Carnal Knowledge of a Juvenile) if the Offender is four (4) or more years older than the Victim Any Rape Offense with Victims less than 13 years of age MUST be classified as FIRST DEGREE RAPE. September, 2016 LIBRS Specifications, Rel

17 Data Element Number Offender Using/Gaming Motivation (41) Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 36 Offender Sequence Number N 8 Offender Suspected of Using / Gaming Motivation 28 1 A ** Future Expansion Buffer A C8 End of Segment Marker A 9 Padding ** A/N September 2016 LIBRS Specifications, Rel

18 Victim (50) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 23 Victim Sequence Number N 25 Victim Type 28 1 A 26 Age A L26 Date of Birth D 27 Sex 40 1 A 28 Race 41 1 A 29 Ethnicity 42 1 A 30 Resident Status 43 1 A (LIBRS Only) 32 Aggravated Assault / Homicide Circumstance No. 1 / LEOKA In the Line of Duty, Type of Assignment Aggravated Assault / Homicide Circumstance No. 2 / LEOKA In the Line of Duty, Type of Assignment Aggravated Assault / Homicide Circumstance No. 3 / LEOKA In the Line of Duty, Type of Assignment Additional Justifiable Homicide Circumstance / LEOKA in the Line of Duty, Type of Activity N N N 50 1 A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation For First Degree Rape Offenses, Age of Victim CANNOT BE '13', '14', '15', OR '16'. Consider Reporting the Associated Offense as a Statutory Rape (36B) September, 2016 LIBRS Specifications, Rel

19 Victim Injury (51) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 23 Victim Sequence Number N 33 Injury Type 28 1 A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Segment 51 missing -- must be present if Victim Type is "I" (Individual) or "L" (Law Enforcement Officer) and if offense is applicable. September 2016 LIBRS Specifications, Rel

20 Victim/Offender Relation (52) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 23 Victim Sequence Number N 34 Offender Number to be Related N 35 Relationship of Victim to Offender A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Segment 52 missing -- must be present if Victim Type is "I" (Individual) or "L" (Law Enforcement Officer) and if offense is applicable. September, 2016 LIBRS Specifications, Rel

21 Arrestee (60) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 40 Arrest Sequence Number N 41 Arrest Number/Local Booking Number for A Arrest L55 Arrest Transaction Number A/N L40 Arrestee Name A 42 Arrest Date D 43 Arrest Type 83 1 A 44 Multiple Arrestee Segment Indicator 84 1 A 47 Age A L47 Date of Birth 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 A C6 Clearance Indicator (to be used for Time A Window Submission only) ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation C6 (Clearance Indicator) must be Blank (G) when Action Type is NOT "W" (Time-Window). September 2016 LIBRS Specifications, Rel

22 Arrestee Armed (61) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 40 Arrestee Sequence Number N 46 Arrestee Armed with A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N September, 2016 LIBRS Specifications, Rel

23 Arrestee Statute (62) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 40 Arrestee Sequence Number N 45 Louisiana Revised Statute Number of Arrest A L45 Arrest Connection to Offense A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation The Incident Number associated with the current submission was not found in LIBRS database. The Arrestee Segment submitted with an Action Type of "A" (Add an Arrest) was rejected because the incident is not on the LIBRS database. Error Message: Incident Report not on file. September 2016 LIBRS Specifications, Rel

24 Arrestee Modification (63) [For Time Window Submissions, ONLY] Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C5 Action Type 3 1 A 1 ORI Number A 2 Incident Number A 6 Louisiana Revised Statute Number of Incident A ** Future Expansion Buffer A C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation LRS (6) MUST exist when Action Type is "W" (Time-Window). September, 2016 LIBRS Specifications, Rel

25 Submission Trailer (99) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N C7 Number of Segments Transferred N C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Last line in data submission NOT Segment Type 99 (Submission Trailer) Number of Segments Transferred field (Data Element C7) in Submission Trailer is NOT a valid numeric field Number of Segments Transferred (Data Element C7) in Submission Trailer Segment does not match Record Count for data submission. September 2016 LIBRS Specifications, Rel

26 Zero Records (01) Data Element Number Description of Data Element Position(s) Length Format C1 Segment Descriptor N 2 Incident Number - All Zeroes " " N C8 End of Segment Marker A C9 Padding ** A/N Error Number Error and Explanation Zero-Reporting Incident Number MUST be all Zeroes. A Segment "01" was submitted, but the Incident Number (Data Element 2) entered into positions 3-14 was not all zeroes. September, 2016 LIBRS Specifications, Rel

27 Control Data Element Definitions September 2016 LIBRS Specifications, Rel

28 September, 2016 LIBRS Specifications, Rel

29 Segment Descriptor (C1) Data Characteristics: 2 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) MUST identify a segment of proper length. Error Note: This two-digit identifier is used by LIBRS to determine the type of segment being processed. Allowed Entries: Segment Descriptors 00 Submission Header 01 Zero Records 10 Administration 11 Administration Modification 20 Offense 30 Property 31 Property Description 33 Property Modification 40 Offender 41 Offender Using 50 Victim 51 Victim Injury 52 Victim/Offender Relation 60 Arrestee 61 Arrestee Armed 62 Arrestee Statute 63 Arrestee Modification 99 Submission Trailer September 2016 LIBRS Specifications, Rel

30 Submitting Agency (C2) Data Characteristics: 20 Character Alpha Requirements: MUST be a valid agency. Error Note: 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. September, 2016 LIBRS Specifications, Rel

31 Submission Date (C3) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) MUST be present -- CANNOT be blank. Error ) Each component of the date MUST be valid; that is, months must be 01-12, days must be 01-31, and year must include the century (i.e., 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (e.g., June CANNOT have 31 days). Error ) The date must be greater than that entered within Reporting Period (C4). Error Note: This data element provides LIBRS with the date that this data submission file was generated for submission. September 2016 LIBRS Specifications, Rel

32 Reporting Period (C4) Data Characteristics: 6 Character Date Format: MMYYYY Requirements: 1) MUST be present--cannot be blank. Error ) Each component of the date MUST be valid; that is, months must be 01-12, and year must include the century (i.e., 19xx, 20xx). Error ) The date CANNOT be greater than that entered within Date of Submission (C3). Error ) Reporting Period date CANNOT precede incident date. Error Note: 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). September, 2016 LIBRS Specifications, Rel

33 Action Type (C5) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present--cannot be Blank (G0. Error Note: 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: Action Type I A M D W Action Performed by LIBRS/NIBRS Incident Report (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 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 (Action Type M segments are used for Time-Window Submission correction for an Exceptional Clearance, Recovered Property or Arrests). It can also be used to modify exceptional clearance indicator and/or exceptional clearance date when incident has already been submitted. Delete (Action 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: Exceptional Clearance Exceptional Clearance Date Recovered Property An Arrest. September 2016 LIBRS Specifications, Rel

34 Clearance Indicator (C6) [for "Time-Window" Submissions only] Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be Blank (G), if Action Type (C5) is "W" (Time-Window). Error ) MUST be a valid code. Error ) MUST be Blank (G) when Action Type is NOT "W" (Time-Window). Error Note: 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: 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 Y prior to the date the 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 N that occurred since the agency s base data, and is in the LIBRS/NIBRS database). September, 2016 LIBRS Specifications, Rel

35 Data Characteristics: 6 Character Numeric Requirements: 1) MUST be present -- CANNOT be Blank (G). Error ) MUST be 3 or greater. Error Number of Segments Transferred (C7) 3) MUST be equal to the total number of segments within the data submission file. Error Note: 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 3. September 2016 LIBRS Specifications, Rel

36 End of Segment Marker (C8) Data Characteristics: 2 Character Alpha Requirements: 1) MUST be present -- CANNOT be Blank (G). Error ) MUST be equal to "ZZ". Error Note: 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. September, 2016 LIBRS Specifications, Rel

37 Padding (C9) Data Characteristics: Character Alpha/Numeric Requirements: 1) MUST be Blank (G) if fixed length records are submitted. MUST be one newline character (ASCII 13) if variable length records are submitted. 2) If fixed length records are used this field might be appropriate to "pad" segment length out to exactly column 150. Note: 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). September 2016 LIBRS Specifications, Rel

38 Software ID (C10) Data Characteristics: 5 Characters Alpha/Numeric Requirements: 1) Contains Identification of software used to generate the LIBRS data submisstion September, 2016 LIBRS Specifications, Rel

39 Software Version (C11) Data Characteristics: 10 Characters Alpha/Numeric Requirements: 1) Contains Version of software used to generate the LIBRS data submisstion September 2016 LIBRS Specifications, Rel

40 September, 2016 LIBRS Specifications, Rel

41 Data Element Definitions Data Elements 1 thru L55 September 2016 LIBRS Specifications, Rel

42 September, 2016 LIBRS Specifications, Rel

43 ORI Number (1) Data Characteristics: 9 Character Alpha Requirements: 1) MUST be present -- CANNOT be Blank (G). Errors 10001, 11001, 12001, 13001, 14001, 15001, ) MUST be a valid 9-character NCIC number, where the last 2 positions of the ORI must reflect "00" for all state and local agencies. Errors 10052, 10086, 11004, 12004, 13004, 14004, 15004, ) First two positions MUST be the code of the state, "LA", in which the incident occurred. Error Note: 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". September 2016 LIBRS Specifications, Rel

44 Incident Number (2) Data Characteristics: 12 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Errors 10001, 11001, 12001, 13001, 14001, 15001, ) Zero Reporting Segments (Segment 01) must contain TWELVE ZEROES, same as the Incident Number. Error ) MUST be LEFT JUSTIFIED with Blank RIGHT-FILL if under 12 characters in length. Errors 10016, 11016, 12016, 13016, 14016, 15016, ) Valid character combinations can include A-Z, 0-9, hyphens, and/or blanks. Errors 10017, 11017, 12017, 13017, 14017, 15017, ) MUST be Blank RIGHT-FILL if under twelve characters in length. The field CANNOT have embedded Blanks (G) between the first and last characters entered. Error 10015, 11015, 12015, 13015, 14015, 15015, ) This field MUST be unique for each incident reported by the agency. This means that no two incidents can have the same Incident Number. Some agencies ensure uniqueness by prefixing every incident number with a two-digit year followed by a number starting with 1, while others simply increment the Incident Number by one for each new incident. Error ) CANNOT have duplicate Incident Number for "Time-Window" Segment. Error Note: Incident Number is the reporting agency's 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. 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 distance between the offenses and the distance between the locations where they occurred were September, 2016 LIBRS Specifications, Rel

45 insignificant. Incident Number (2) 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. September 2016 LIBRS Specifications, Rel

46 Incident Date/Hour (3) Data Characteristics: 11 Character Alpha Format: MMDDYYYYXHH Requirements: 1) MUST be present -- CANNOT be blank. Error ) Each component of the date must be valid; that is, months must be 01-12, days must be 01-31, and year must include the century (i.e., 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (e.g., June CANNOT have 31 days). The Incident Date CANNOT exceed the current date. Error ) When an ORI becomes inactive, no incident data may be submitted to LIBRS with an incident date on or after that date. However, adjustments to previously submitted data may be done. Error ) The Incident Date CANNOT be earlier than 01/01/1991 for Incident Report ( I ) submissions. This edit will preclude dates that are obviously incorrect since the FBI began accepting data on this date. Error ) When an agency converts from UCR Summary reporting to Incident-Based Reporting (IBR), or commences to report LIBRS data, 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, otherwise 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 IBR data for the first time on 20 July 2014, all Incident Date/Hour (3) entries for incidents, recovered property, and arrests must be within July, The exception is when Exceptional Clearances occur for a pre- IBR incident. In this case, Incident Date/Hour (3) may be earlier than July, 2014, but Exceptional Clearance Date (5) must be within July, 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). Error ) Incident Date/Hour CANNOT be later than the year and month the data submission file represents. (Ex.: A June 2014 data submission CANNOT contain incidents occurring after June). Error ) The Submission Date (C3), in positions 23-30, and the Incident Date MUST be valid entries. LIBRS uses these two dates to determine if the complete incident should have been reported, or if a subset of the segments should have been submitted as "Time Window" submissions. Error ) Administrative Segments (10) submitted with an Action Type of "W" (Time-Window Submission) CANNOT have a date in Incident Date/Hour (3) that would be a valid date for an Incident occurring since the agency s Base Date. September, 2016 LIBRS Specifications, Rel

47 Incident Date/Hour (3) This is also true for any Administrative Segments (10) subsequently submitted with an Action Type of "M" (Modify) that modify or update a previously submitted Time- Window submission. Error ) Administrative Segments (10) submitted with an Action Type of "M" (Modify) CANNOT change the Incident Date/Hour (3) previously submitted in the original Incident Report (Action Type of "I"). Error ) Administrative Segments (10) submitted with an Action Type of "M" (Modify) CANNOT change the Report Date Indicator (position 51 of the segment) of Segments which were previously submitted with an Action Type of "I" (Incident Report). Error ) Administrative Segments (Segment 10) submitted with an Action Type of "M" (Modify) CANNOT change the hour part of Incident Date/Hour (3) of incidents previously submitted with in the original Incident Report (Action Type of "I ). Error ) If HOUR is entered it must be "00" through "23." Error Note: If the Incident Date occurred at exactly midnight, enter the Incident Date as if the time was 1 minute past midnight. (Example: If the incident occurred at exactly midnight on Thursday, enter Friday's date) and 00 for the hour. 13) If the Incident Date is unknown, use the Report Date. Indicate a Report Date with an "R" in the space before the hour. If this is the Incident Date, then leave the "Report" indicator blank. Error Notes: 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. Otherwise leave the report column nine (9) blank. If the incident hour is unknown, leave the hour blank. September 2016 LIBRS Specifications, Rel

48 Incident Date/Hour (3) Examples: (1) If a robbery occurred at 9:30 p.m. on July 2, 2014, the entry should be " G21" (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 " G23" (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 " RGG" (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 G11 (where G is a blank). Note: When LIBRS requires a Blank (G), it must be a Blank (G), NOT A ZERO. 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 production data that is kept on both LIBRS (state) and NIBRS (FBI) databases. 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. (5) 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, 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 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. September, 2016 LIBRS Specifications, Rel

49 Cleared Exceptionally (4) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) CANNOT be "N" (Not Applicable) if Exceptional Clearance Date (5) is entered. Error ) When a value other than "N" (Not Applicable) is entered, there can be NO Arrestee Segments associated with the Incident. Error ) Administrative Segments (10) submitted with an Action Type of "M" (Modify) must have an "N" (Not Applicable) in Cleared Exceptionally (4) indicator when Arrestees are included as part of the original Incident Report. Error ) Administrative Segment (10) submitted with an Action Type of "W" (Time Window Submission) CANNOT contain an "N" (Not Applicable) in Cleared Exceptionally (4). Error Notes: 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: 1) The investigation must have clearly and definitely established the identity of at least one offender. 2) Sufficient probable cause must have been developed to support the arrest, charging, and prosecution of the offender. 3) The exact location of the offender must be known so that an arrest could be made. 4) 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. September 2016 LIBRS Specifications, Rel

50 Cleared Exceptionally (4) Allowed Entries: Enter one code per incident. Cleared Exceptionally Indicators A Death of Offender B Prosecution Declined (by the prosecutor other than lack of-probable cause) C Extradition Denied D Victim Refused to Cooperate (in the prosecution) E Juvenile/No Custody (the handling of a juvenile without taking him/her into custody, but rather by oral or written notice given to the parents or legal guardian in a case involving a minor offense) O Other (Administrative Closing of a case--this does not clear the incident for LIBRS--reported to NIBRS as a N ) N Not Applicable (Not Cleared Exceptionally) Example: A kidnapper holding a hostage killed himself when the building in which he barricaded himself was surrounded by police. The kidnaping is cleared exceptionally under, "Death of the Offender". September, 2016 LIBRS Specifications, Rel

51 Exceptional Cleared Date (5) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) The clearance date CANNOT be earlier than the incident date. Error ) MUST be present if incident was cleared exceptionally with a data value of A, B, C, D, E, or O in Cleared Exceptionally (4)). Error ) Each component of the date must be valid: months must be 0-12, days must be 01-31, and year must include the century (that is, 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (for example, June CANNOT have 31 days). The Exceptional Clearance Date CANNOT be greater than that entered within the Reporting Period (C4). For example, if the Reporting Period is (that is, June 2014), then the Exceptional Clearance Date CANNOT contain any date 07/01/2014 or greater. Error ) Administrative Segments (10) submitted with an Action Type of "W" (Time-Window Submission) must contain Cleared Exceptionally (4) and Exceptional Clearance Date (5). Both data elements must be present to be a valid submission. Error ) Administrative Segments (10) submitted with an Action Type of "W" (Time-Window Submission) CANNOT have an Exceptional Clearance Date (5) earlier than the "Time-Window" Base Date. This is also true for any "M" (Modify) submissions subsequent to a previously submitted Time-Window Submission (Action Type of W ). Error ) Administrative Segments (10) submitted with an Action Type of "M" (Modify) and an Exceptional Clearance (4) indicator of "N" (Not Applicable) CANNOT have an entry in Exceptional Clearance Date (5). Error ) Administrative Segments (10) submitted with an Action Type of "M" (Modify) for a previously submitted Time-Window Submission (Action Type of W ) must have an Exceptional Clearance Date (5). Error ) Administrative Segments (10) submitted with an Action Type of "W" (Time-Window Submission) or "M" (Modify) CANNOT have an Exceptional Clearance Date (5) earlier than the date the ORI was certified for LIBRS submission. Error Note: If an incident was cleared by exceptional means, then the month, day and year when the incident was cleared is to be entered into this data element. September 2016 LIBRS Specifications, Rel

52 Exceptional Cleared Date (5) Example: The incident was cleared on the books of the reporting agency on May 27, It was entered into the local computer on June 6, 2014, and was submitted to LIBRS sometime in July of The date " " should be entered into this data element. September, 2016 LIBRS Specifications, Rel

53 Offense Sequence Number (L6) Data Characteristics: 3 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be numeric entry (001 through 999) with zero left-fill. Offense Sequence Number (L6) distinguishes one offense from another. Error ) MUST be unique -- CANNOT be duplicated. Error Note: Each offense in an incident must be assigned a unique sequence number from "001" to "999". September 2016 LIBRS Specifications, Rel

54 Louisiana Revised Statute (6) Data Characteristics: 12 Character Alpha Format: TT:SSSS.S/P-I Louisiana Revised Statute Format TT Title SSSS.S Section PPP/I Subpart, or Subpart with Qualifier, or 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: 1) MUST be present--cannot be Blank (G). Error ) MUST be a valid code on Master LIBRS/LRS Code Table. Error Notes: Louisiana Revised Statutes specify the offenses that occur during an incident. 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 spaces14:gg30], and dropping the space after the decimal.) The field should be LEFT JUSTIFIED WITH NO INCLUDED SPACES. Spaces are interpreted as the Endof-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. Local ordinances reported to LIBRS will generate a warning unless LIBRS administrators are first told to expect these local ordinances and a description of the local ordinance has been sent to LIBRS administrators so they can be classified and programmed into LIBRS. No LRS codes will be accepted unless they are indicated on the Master LIBRS/LRS Code Table. If the LRS code is not indicated on this Master Table the incident should NOT be sent to LIBRS. If the LRS is sent before it is classified and defined on the Master LIBRS/LRS Code Table it will be rejected. September, 2016 LIBRS Specifications, Rel

55 Louisiana Revised Statute (6) Examples: (1) 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. 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." (2) 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 14:42.1 does require a Qualifier. (3) 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 should be submitted as14:42.1/v for Victim 001 and 14:42.1/V for Victim 002) Refer to the Master LIBRS/LRS Code Table to determine: 1) LRS Codes that are accepted 2) What offense the LRS code was assigned: NIBRS Code determines offense to be reported. 3) Index Class assigned to each LRS 4) IBR and NIBRS rankings. To determine definitions of Qualifiers see the list at the end of this section. Allowed Entries for Subparts: Some LRS codes must be submitted with a Subpart. Each code may be a different offense when submitted to LIBRS. For instance 14:107/1 would be reported to the FBI as Drunkenness NIBRS 90E) and 14:107/9 would be reported to the FBI as (Prostitution NIBRS 40A). The following LRS codes MUST have a Subpart, and will be rejected if not submitted with a Subpart. The following LRS codes with Subparts are not shown in the Master LIBRS/LRS Code table. 14:59 14:94 14:103 14:107 14:130.1 The LRS codes listed below require a Subpart to determine the proper offense to be submitted to LIBRS. 14:59/A1 14:59/A2 14:59/A3 14:59/A4 14:59/A5 14:59/A6 14:59/A7 14:59/A8 14:59/A9 14:59/A10 14:94/E 14:94/F 14:103/A1 14:103/A2 14:103/A3 14:103/A4 14:103/A5 14:103/A6 September 2016 LIBRS Specifications, Rel

56 Louisiana Revised Statute (6) 14:107/1 14:107/2 14:107/3 14:107/4 14:107/5 14:107/6 14:107/7 14:107/8 14:107/9 14:130.1/A 27:98/B 27:98/C 27:100/A 27:100/B 27:264/A 27:264/B Note: 14:130.1 can also be submitted with a Qualifier. See Allowed Entries for Qualifiers (below) Examples: (1) 14:59/A1 -- In this example, A1" refers to Subpart A, Paragraph 1 of the LRS, and would be reported to the FBI as being in the category of All Other Offenses (NIBRS 90Z). (2) 14:59/A9 -- In this example, A9" refers to the Subpart A, Paragraph 9 and would be reported to the FBI as being in the category of Weapon Law Violation (NIBRS 520). Validation Edit If these LRS codes are submitted without a Subpart, the entire incident will be rejected and the agency will receive the following error message: This LRS code must be submitted with a subpart to identify offense applicable. Error Allowed Entries for Subparts, and Subparts with Qualifiers: LRS Codes can have Subparts, with some requiring Subparts with Qualifiers. Each code may be a different offense when submitted to LIBRS. For instance, 14:129/A1 would be reported to the FBI as Intimidation (NIBRS 13C) and 14:129/A2F would be reported to the FBI as an Aggravated Assault (NIBRS 13A). The following LRS codes will be rejected if not submitted with a subpart or subpart with a Qualifier and have been deleted from the Master LIBRS/LRS Code Table. 14:129 14:228 40:971 The LRS codes listed below require a Subpart or a Subpart with a Qualifier to determine the proper offense to be submitted to LIBRS. 14:108/B1BF 14:108/B1B 14:129/A1 14:129/A2F 14:129/A2T 14:228/A1 14:228/A2 14:228/A3 14:228/A4 14:228/A5 14:228/A6 14:228/A6X Example: (1) 14:228/A6 -- In this example, "A6" refers to the Subpart A, Paragraph 6 of the LRS, and with no Qualifier would be reported to the FBI as All Other Larceny (NIBRS 23H). (2) 14:228/A6Y -- In this examle"a6" refers to the Subpart A, Paragraph 6 of the LRS, and with a Qualifier of "Y", would be reported to the FBI as Destruction/Damage/Vandalism of Property (NIBRS 290) September, 2016 LIBRS Specifications, Rel

57 Louisiana Revised Statute (6) Validation Edit If this LRS is submitted without a Subpart or a Subpart with a Qualifier the entire incident will be rejected. The agency would receive an error message that says: This LRS code must be submitted with a subpart or a subpart with a Qualifier to define the offense applicable. Error Validation Edit If the LRS is submitted with a subpart and no Qualifier, the agency would receive a warning message that says: WARNING--This LRS code was submitted with a subpart and no Qualifier. Refer to the Master LIBRS/LRS Code Table to be sure the correct offense is being reported. Warning :228/A6Y 14:228/A7 27:309/BR 27:309/B 27:309/C 40:971/A 40:971/B1A 40:971/B1BX 40:971/B1B 40:971/B1C 40:971/B1D 40:971/B1E 40:971/B1F 40:971/B1G 40:971/B1H 40:971/C Allowed Entries for Qualifiers: Some LRS codes must be submitted with a Qualifier in order to determine the proper offense to be reported. For instance, 14:42/V would be reported to the FBI as a Forcible Rape (11A) and 14:42/A would be a Forcible Sodomy (11B). The following LRS codes will be rejected if not submitted with a Qualifier and have been deleted from the Master LIBRS/LRS Code Table. 14:42 14: :43 14: : :51 14:52 14:53 14:54 14:62 14:63 14: : : :90 14: :122 14: :205 14:404 The LRS codes listed below require a Qualifier to determine the proper offenses to be submitted to LIBRS. 14:42/A 14:42/V 14:42.1/A 14:42.1/V 14:43/A 14:43/V 14:43.1/N 14:43.1/P 14:43.2/N 14:43.2/P 14:51/H 14:51/U 14:52.1/H 14:52.1/U 14:52/H 14:52/U 14:53/H 14:53/U 14:54/H 14:54/U 14:62/I 14:62/M 14:62/Z 14:63/I 14:63/M 14:63.3/I 14:63.3/M 14:87.2/F 14:87.2/L 14:87.2/W 14:87.5/F 14:87.5/L 14:87.5/W 14:90/G 14:90/R 14:90.2/G 14:90.2/R 14:122/F 14:122/T 14:130.1/B 14:130.1/F 14:130.1/I 14:130.1/T 14:130.1/X 14:130.1/Y 14:205/H 14:205/U 14:404/J 14:404/Q Note: 14:130.1 can also be submitted with a Subpart. See Allowed Entries for Subparts (above). September 2016 LIBRS Specifications, Rel

58 Louisiana Revised Statute (6) Example: (1) 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). (2) 14:51/U -- U refers to a Qualifier (see Qualifier List) and would be reported to the FBI as the offense of Arson (NIBRS 200). Validation Edit If these LRS codes are submitted without a Qualifier, the entire incident will be rejected and the agency would receive an error message that says: "This LRS must be submitted with a Qualifier to identify offense applicable." Error Allowed Entries for With or Without Qualifiers: Qualifiers: Some LRS codes can be submitted with or without a Qualifier. For instance, 14:44.1 would be reported to the FBI as a Kidnaping (NIBRS 100) and 14:44.1/N would be Forcible Fondling (NIBRS 11D). LRS codes listed below will be accepted with or without a Qualifier or a hard code to determine the proper offense code to be reported to LIBRS. 14: :30.1/D 14: :32.1/AA 14: :44.1/A 14:44.1/N 14:44.1/O 14:44.1/P 14:44.1/V 14: :60 14:60/I 14: :65.1/F 14:67 14:67/B 14:67/C 14:67/E 14:67/K 14:67/S 14:67/Z 14: :70.4/FR 14:70.4/X 14: :70.5/FR 14:93 14:93/F 14: :107.1/F 14: :129.1/F 14:129.1/T 14: :133.1/F 14:133.1/T Warning Messages will be returned for the following LRS codes: 14:30.1 with no Qualifier will be reported to the FBI as Murder and Non-negligent Homicide (NIBRS 09A), and the reporting agency will receive the following Warning message: "WARNING -- This LRS submitted without a Qualifier will be reported as Murder and Non-negligent Homicide (09A). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning 22125) 14:32.1 with no Qualifier will be reported to the FBI as Driving Under the Influence (NIBRS 90D), and the reporting agency will receive the following Warning message: "WARNING -- This LRS submitted without a Qualifier will be reported as Driving Under the Influence (90D). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning September, 2016 LIBRS Specifications, Rel

59 Louisiana Revised Statute (6) 14:44.1 with no Qualifier will be reported to the FBI as Kidnaping (NIBRS 100). The reporting agency will receive the following Warning message: "WARNING -- This LRS submitted without a Qualifier will be reported as Kidnaping (100). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning :60 with no Qualifier will be reported to the FBI as a Robbery (NIBRS 120). The reporting agency will receive the following Warning message: WARNING This LRS submitted without a Qualifier will be reported as a Robbery (120). If this is not the correct offense resubmit this LRS code with a Qualifier. Warning :65.1 with no Qualifier will be reported to the FBI as a Purse Snatching (NIBRS 23B). The reporting agency will receive the following Warning message: "WARNING --- This LRS submitted without a Qualifier will be reported as Purse- Snatching (23B)." If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning :70.4 with no Qualifier will be reported to the FBI as a Credit Card/Automatic Teller Machine Fraud (NIBRS 26B). The reporting agency will receive the following Warning message: WARNING This LRS submitted without a Qualifier will be reported as Credit Card/Automatic Teller Machine Fraud (26B). If this is not the correct offense resubmit this LRS code with a Qualifier. Warning :70.5 with no Qualifier will be reported to the FBI as Bribery (NIBRS 510). The reporting agency will receive the following Warning message: WARNING This LRS submitted without a Qualifier will be reported as Bribery (510). If this is not the correct offense resubmit this LRS code with a Qualifier. Warning :93 with no Qualifier will be reported to the FBI as a Family Offense Nonviolent (NIBRS 90F). The reporting agency will receive the following Warning message: "WARNING --- This LRS submitted without a Qualifier will be reported as Family Offense Nonviolent (90F). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning :107.1 with no Qualifier will be reported to the FBI as All Other Offenses (NIBRS 90Z). The reporting agency will receive the following Warning message: "WARNING --- This LRS submitted without a Qualifier will be reported as All Other Offenses (90Z). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning :129.1 with no Qualifier will be reported to the FBI as a Simple Assault (NIBRS 13B). The reporting agency will receive the following Warning message: "WARNING --- This LRS submitted without a Qualifier will be reported as a Simple Assault (13B). If this is not the correct offense, resubmit this LRS code with a Qualifier. Warning September 2016 LIBRS Specifications, Rel

60 Louisiana Revised Statute (6) Hard-Coded Edits for LRS Codes Without a Property Description-Based Qualifier 14:67 with no Qualifier will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H), or other offenses as determined by Property Description (15) hard codes, shown below. When LRS of 14:67 is submitted with no Qualifier and Property Description (15) is other than "03", 04, "05", "24", "28", "37" or "38" the agency will receive the following Warning message: "WARNING-- This LRS submitted without a Qualifier will be reported as All Other Larceny-Theft (23H)" If this is not the correct property description code, resubmit property description code. Warning When LRS 14:67 is submitted with no Qualifier and Property Description (15) is "38", the offense will be reported to the FBI as Theft of Motor Vehicle Parts (NIBRS 23G) and the agency will receive the following Warning message: "WARNING-- This LRS submitted without a Qualifier and "38" in DE # 15 will be reported as Theft of Motor Vehicle Parts (23G)." If this is not the correct Property Description code, resubmit Property Description code. Warning When LRS 14:67 is submitted with no Qualifier and Property Description (15) is "03", "05", "24", "28", or "37", the offense will be reported to the FBI as Motor Vehicle Theft (240), and the agency will receive the following Warning message: "WARNING -- This LRS submitted without a Qualifier and "03", "05", "24", "28", or "37" in DE # 15 will be reported as Motor Vehicle Theft (240)." If this is not the correct property description code, resubmit property description code. Warning When LRS 14:67 is submitted with no Qualifier and Property Description (15) is "04", the offense will be reported as Theft of a Bicycle, and the agency will receive the following Warning message: "WARNING -- This LRS submitted without a Qualifier and "04" in DE # 15 will be reported as theft of a bicycle." If this is not the correct property description code, resubmit property description code. Warning LRS 14:68 will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H), or Motor Vehicle Theft (NIBRS 240) as determined by Property Description (15) hard coding shown below: When LRS 14:68 is submitted with no Qualifier and Property Description (15) is not 03", 05", 24", 28" or 37", the agency will receive the following Warning message: WARNING-- This LRS submitted will be reported as All Other Larceny-Theft (23H). If this is not the correct property description code, resubmit property description code. Warning When LRS 14:68 is submitted and Property Description (15) is 03", 05", 24", 28" September, 2016 LIBRS Specifications, Rel

61 Louisiana Revised Statute (6) or 37", Motor Vehicle Theft (NIBRS 240), then the agency will receive the following Warning message: WARNING-- This LRS submitted and 03", 05", 24", 28" or 37", in DE # 15 will be reported as Motor Vehicle Theft (240). If this is not the correct property description code, resubmit property description code. WARNING 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: Validation Edit When Juvenile Qualifiers are used, Offender Age must be 01" - 16" for a JU:RUN - Runaway Offense (90I), JU:UNG - Ungovernable (90C), JU:CUR - Curfew (90B), or JU:TRU - Truancy (90Z). Error JU:CUR... Juvenile Curfew Violations will be reported to the FBI as Curfew/Loitering/Vagrancy violations (NIBRS 90B - Society) JU:RUN... Juvenile Runaways will be reported to the FBI under Runaways offense (NIBRS 90I - Society - Not a crime) JU:TRU... Juvenile Truancy will be reported to the FBI as All Other Offenses (NIBRS 90Z - Society - Not a Crime) JU:UNG... Juvenile Ungovernables will be reported to the FBI under Disorderly Conduct Offense (NIBRS 90C - Society) Allowed Entries for Inchoates: When LRS codes of 14:25, 14:26, 14:28 and 14:107.2 are reported as offenses, the base LRS code of the actual offense must be immediately followed by a dash and the data value listed below indicating which Inchoate would be applicable. Only one of the following Inchoate Modifiers can be used per LRS offense: LRS Inchoate Modifiers A Accessory After the Fact C Conspiracy I Inciting a Felony S Solicitation H Hate Crime Penalty Enhancer September 2016 LIBRS Specifications, Rel

62 Louisiana Revised Statute (6) Example: 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 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). When a LRS Code is a Group A Offense (Felony), but is submitted with the Inchoates of "-A", "-C", "-I", or "-S" appended, the offense will be reported to NIBRS as All Other Offenses (NIBRS 90Z). When a LRS Code is a Group B Offense (Misdemeanor), but is submitted with the Inchoates of "- A", "-C", "-I", or "-S" appended, the offense will be reported to NIBRS as the appropriate Group B Offense as defined on the LIBRS/LRS Master Code Table. Requirements: 1) When Solicitation for Murder (14:28.1) is reported, it should be submitted WITHOUT a Qualifier. This offense will be reported to the FBI as All Other Offense (NIBRS 90Z). 2) When Principal (14:24) is used as an LRS charge, since this is a definitional LRS and does not carry any penalties, it is not necessary to submit this LRS to LIBRS. 3) An LRS code appended with "A", "C", "I", "S", or "H" indicates the offense is an Inchoate of the LRS Offense shown in first ten digits Louisiana Revised Statute (6) or Louisiana Revised Statute of Arrest (45). These Modifiers for an LRS code should always be considered "Completed", even if the principal LRS offense was not. The offender completed the conspiracy, even if the offense itself was not completed by the offender conspired with. Error ) When an LRS Code is submitted with the Inchoate "-H" appended, the LRS will be reported to the FBI to NIBRS under the offense code defined on the LIBRS/LRS Master Code Table. Note: An LRS Code appended with "-H" indicates the offense is a Hate Crime, and the penalty will be enhanced by 14: Offenses with an Inchoate appended will be reported based on the base LRS (usually shown in the first ten digits of Louisiana Revised Statute (6) or Louisiana Revised Statute of Arrest (45). 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. September, 2016 LIBRS Specifications, Rel

63 Louisiana Revised Statute (6) AA... Vehicular Homicide with Intent to Kill: (Murder and Nonnegligent Manslaughter NIBRS 09A - Person) A... 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 consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity. (Forcible Sodomy NIBRS 11B - Person) B... Theft from Building: A theft from within a building which is either open to the general public or where the offender has legal access. (Theft from Building - 23D - Property) C... Theft from Coin Operated Machine: Theft from a machine or device which is operated or activated by the use of coins. (Theft from Coin Operated Machine - 23E - Property) D... 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 dangerous substance, which is the direct cause of the death of the person who ingested or consumed the controlled dangerous substance. (Drug/Narcotic Violations - 35A - Society) E... Embezzlement: Unlawful misappropriation by an offender to his/her own use or purpose of money, property, or some other thing of value entrusted to his/her care, custody, or control. (Embezzlement NIBRS Property) F... Actual Force Used Against a Victim or Threat of Force Displaying a Weapon: Might be used to determine if a purse snatching is to be reported as Strong-Arm Robbery (14:65.1/F), or as Larceny Theft (14:65.1) (Aggravated Assault NIBRS 13A Person; or Robbery- NIBRS Person) FR... Fraud - False Pretense/Swindle/Confidence Game: Intentional misrepresentation of existing fact or condition, or the use of some other deceptive scheme or device, to obtain money, goods, or other things of value. (False Pretense/Swindle/Confidence Game NIBRS 26A - Property) G... Betting and Wagering: To unlawfully stake money or something else of value on the happening of an uncertain event or on the ascertainment of a fact in dispute. (Betting/Wagering - 39A - Society) H... Inhabited Dwelling: Structure occupied as a place of settled residence or habitat (lived in regularly or routinely). Arson reporting (Arson NIBRS Property) I... Immovable Structures: Fixed permanent or immovable things; include house trailer or houseboat if used as permanent dwelling. September 2016 LIBRS Specifications, Rel

64 Louisiana Revised Statute (6) Burglary: Unlawful entry into a building or other structure with intent to commit a felony or a theft. Trespass of Real Property: To unlawfully enter land, a dwelling, or other real property. (Burglary NIBRS Property, or Trespass of Real Property NIBRS 90J - Society) J... Self-Inflicted Serious Bodily Injuries: (All Other Offenses NIBRS 90Z - Person) JU:CUR... Juvenile Curfew Violations: will be reported to the FBI as curfew/loitering/ vagrancy violations (Curfew/Loitering/Vagrancy Violations NIBRS 90B - Society) JU:RUN... Juvenile Runaways: will be reported to the FBI under Runaways offense (Runaway NIBRS 90I - Society - Not a Crime) JU:TRU... Juvenile Truancy: Absent from school without permission. Reported to NIBRS as All Other Offenses (NIBRS 90Z - Society - Not a Crime) JU:UNG.. Juvenile Ungovernables: will be reported to the FBI as Disorderly Conduct (Disorderly Conduct NIBRS 90C - Society) K... Pocket Picking: Theft of articles from another person's physical possession by stealth where the victim usually does not become immediately aware of the theft. (Pocket Picking NIBRS 23A - Property) L... Murder and Non-Negligent Manslaughter: Willful (non-negligent) killing of one human being by another (human being live born--not an embryo or fetus in utero) (Murder and Non-Negligent Manslaughter NIBRS 09A - Person) M... Movable Structures: Tents, boats, airplanes, lawnmowers, hand tools, farm and construction equipment, etc.--not permanent dwellings--larceny Theft (All Other Larceny NIBRS 23H- Property) N... Rubbing/Touching: No actual penetration-"indecent liberties", "child molesting", no elements of NIBRS 11A, 11B or 11C were applicable (Forcible Fondling NIBRS 11D - Person) 0... 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 because of his/her youth or because of his/her temporary or permanent mental or physical incapacity. (Forcible Sodomy NIBRS 11B - Person) P... 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 person's will. Or, not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity. (Sexual Assault With an Object NIBRS 11C - Person) September, 2016 LIBRS Specifications, Rel

65 Louisiana Revised Statute (6) Q... Victim Had Offender Inflict Serious Bodily Injuries to Him/Her: Victim made the offender inflict injuries to his/her person--no intent on part of the offender. (Aggravated Assault NIBRS 13A - Person) R... Operating/Assisting Gambling: To unlawfully operate, promote, or assist in the operation of a game of chance. (Operating/Promoting/ Assisting Gambling NIBRS 39B - Property) S... Shoplifting: The theft, by someone other than an employee of the victim, of goods or merchandise exposed for sale. (Shoplifting NIBRS 23C - Property) T... Threat of Force Used Against the Victim: No weapons and no physical attack used in this threat. (Intimidation NIBRS 13C - Person) U... Uninhabited Dwelling: Structures uninhabited or abandoned or not normally in use. Arson reporting (Arson NIBRS Property) V... Vaginal penetration: With force or without force where the victim is incapable of giving consent because of youth or because of temporary or permanent mental incapacity (Forcible Rape NIBRS 11A - Person) W... Fetal Death: Human embryo or fetus in utero (All Other Offenses NIBRS 90Z - Society) X... 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 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. (Counterfeiting/Forgery NIBRS Property) Y... Destroyed Records or Property: (Destruction/Damage/Vandalism of Property NIBRS Property) Z... Theft from a Motor Vehicle: Theft of articles from motor vehicle whether locked or unlocked. (Theft from a Motor Vehicle NIBRS 23F - Property) LRS Inchoate Modifiers A Accessory After the Fact C Conspiracy I Inciting a Felony S Solicitation H Hate Crime Penalty Enhancer September 2016 LIBRS Specifications, Rel

66 Offense Attempted/Completed (7) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code of "A" (Attempted) or "C" (Completed). Error ) When Attempted ( A ) is entered and Louisiana Revised Statute (6) is either a Crime Against Property, or a Gambling (NIBRS 39A or NIBRS 39B), Kidnaping (NIBRS 100) or Drug/Narcotic offense (NIBRS 35A or 35B), then Type of Property Loss (14) must be None ("1") or Unknown ("8 ). Error ) When Completed ( C ) is entered and Louisiana Revised Statute (6) is either a Crime Against Property, or a Gambling (NIBRS 39A or NIBRS 39B), Kidnaping (100), or Drug/Narcotic offense (NIBRS 35A or NIBRS 35B), then Property Segments (Segments 30 and 31) MUST be present with a valid code in Type of Property Loss (14). Error ) Offense Attempted/Completed (7) MUST be Completed ( C ) when Louisiana Revised Statute (6) is an "Assault" or "Homicide." Error Notes: This element is used to indicate whether each offense in the incident was completed or merely attempted. Allowed Entries: Enter only one (1) code for each Offense Segment: Offense Attempted/Completed A Attempted C Completed Example: 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. Offense 001 should be entered as Aggravated Rape (LRS 14:42/V) and have Completed ("C") entered in Offense Attempted/Completed (7). Offense 002 should also be entered as Aggravated Rape (LRS 14:42/V), but will have Attempted ( A ) entered in Offense Attempted/Completed (7). September, 2016 LIBRS Specifications, Rel

67 Bias Motivation/Bias Crime Type (8A) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) If more than one code entered, CANNOT be a duplicate. Error ) Value "N" = Not Applicable is mutually exclusive of any other value entered, i.e., "N" is to be entered only if no other code applies. Error Notes: 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: Enter up to four (4) codes for each Offender Segment: Offender Suspected of Using/Gambling Motivation A Alcohol C Computer Equipment D Drugs/Narcotics G Gaming Activity Motive for Crime (LIBRS only) N Not Applicable Examples: (1) 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 knife. Alcohol ( A ) should be entered in Offender Suspected of Using/Gaming Motivation (8). (2) 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 ( C ) should be entered in Offender Suspected of Using/Gaming Motivation (8). (3) 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 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 (8). September 2016 LIBRS Specifications, Rel

68 Bias Motivation/Bias Crime Type (8A) Data Characteristics: 2 Character Alpha Requirements: 1)... MUST be present -- CANNOT be blank. Error )... MUST be a valid code. Error Notes: 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. Allowed Entries: Enter only one code for each Offender Segment (40): Race/Ethnicity/Ancestry Religion LIBRS Data Value Category NIBRS Data Value 11 Anti-White Anti-Black or African American Anti-American Indian or Alaska Native Anti-Asian Anti-Multiple Races, Group Anti-Native Hawaiian or Other Pacific Islander Anti-Arab Anti-Hispanic or Latino Anti-Other Race/Ethnicity/Ancestry Anti-Jewish Anti-Catholic Anti-Protestant Anti-Islamic (Muslim) Anti-Other Religion Anti-Multiple Religions, Group Anti-Atheism/Agnosticism Anti-Mormon Anti-Jehovah s Witness Anti-Eastern Orthodox (Russian, Greek, Other) Anti-Other Christian 82 September, 2016 LIBRS Specifications, Rel

69 Sexual Orientation Disability Gender Gender Identity None/Unknown Bias Motivation/Bias Crime Type (8A) 83 Anti-Buddhist Anti-Hindu Anti-Sikh Anti-Gay (Male) Anti-Lesbian (Female) Anti-Lesbian, Gay, Bisexual, or Transgender (Mixed Group) Anti-Heterosexual Anti-Bisexual Anti-Physical Disability Anti-Mental Disability Anti-Male Anti-Female Anti-Transgender Anti-Gender Non-Conforming None (no bias) (mutually exclusive) Unknown (offender s motivation not known) (mutually exclusive) Age Ancestry Creed Gender Organizational Affiliation 99 * * * Bias Motivations Changes Beginning with LIBRS 2.2 * * * LIBRS Will Continue to Accept this Data Value, But Will Require Translation to NIBRS Data Value NIBRS Converted Data Values Required from LIBRS-Only Data Values Redefined/Repurposed; Migration of Historical Data Required New Bias Motivation Inadvertently Removed from Previous Specification, Now Restored Other Bias (LIBRS Only) 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 (6) probably should be appended with the Hate Crime Penalty Enhancer (-H) to represent enhanced penalties related to hate crimes in LRS 14: September 2016 LIBRS Specifications, Rel

70 Bias Motivation/Bias Crime Type (8A) Notes: Beginning with LIBRS 2.2, Several changes have been made to the Bias Motivation (Data Element 8A) code table, including ten new Bias Motivation data values (16, 28, 29, 81,82, 83, 84, 85, 61 and 62). Two Bias Motivation data values (71, 72) have been redefined and repurposed; and, one Bias Motivation has been redefined and its data value deleted (73). Two other LIBRSonly Bias Motivations (70, 74) have been clarified regarding their conversion to NIBRS data values. Bias Motivation code 71 (Ancestry) will no longer be accepted. Bias because of a Victim s ancestry will now be coded as 33 (Anti-Other Race/Ethnicity/Ancestry ). Bias Motivation code 72 (Creed) will no longer be accepted. Creed is now considered redundant with Bias Motivation code 25 (Anti-Other Religion). Bias because of a Victim s creed will now be coded as 25 (Anti-Other Religion). Bias Motivation code 73 (Gender) will no longer be accepted. NIBRS has released four new codes that explicitly splits gender bias into the following specific categories: 61 Anti-Male 62 Anti-Female 71 Anti-Transgender 72 Anti-Gender Non-Conforming. For Bias Motivations that are not collected by the FBI (that is, they are LIBRS-only), the existing documentation suggests those LIBRS-only Bias Motivations (70 and 74, for example) should be converted to Bias Motivation code 88 (None) before sending them to NIBRS, indicating that no bias occurred. However, the NIBRS extraction and conversion process has, in fact, been translating them to 99 (Unknown) which is logical, and should continue to be used. The new LIBRS Specification 2.2 will be updated to reflect what has actually occurred in practice. September, 2016 LIBRS Specifications, Rel

71 Location Type (9) Data Characteristics: 2 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error Notes: 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. Allowed Entries: Enter only one (1) code per Offense Segment: *** Cells Shaded Brown (37 thru 58) are new Location Types, beginning with LIBRS 2.2. *** 01 Air, Bus, Train or Terminal 24 Specialty Store (includes fur store, jewelry store, TV store, dress shop, etc.) 02 Bank Savings and Loan (includes other financial institutions) 25 Other/Unknown (use only if none of the above codes apply) 03 Bar or Night Club 37 Abandoned/Condemned Structure 04 Church, Synagogue or Temple (includes other religious buildings) 38 Amusement Park 05 Commercial or Office Building 39 Arena/Stadium/Fairgrounds/Coliseum 06 Construction Site Convenience Store 41 ATM Separate from Bank (formerly Casino Land Based) Auto Dealership New/Used (formerly Casino Riverboat) 08 Department or Discount Store 42 Camp/Campground 09 Drug Store, Doctor Office or Hospital (includes medical supply building) 44 Daycare Facility 10 Field/Woods 45 Dock/Wharf/Freight/Modal Terminal 11 Government/Public Building 46 Farm Facility September 2016 LIBRS Specifications, Rel

72 Location Type (9) 12 Grocery or Supermarket 47 Gambling Facility/Casino/Race Track 13 Highway, Road or Alley (includes street) 48 Industrial Site 14 Hotel, Motel, Etc. (includes other temporary lodgings) (includes other temporary lodgings) 49 Military Installation 15 Jail or Prison (includes penitentiary) 50 Park/Playground 16 Lake or Waterway 51 Rest Area 17 Liquor Store 52 School College/University 18 Parking Lot or Garage 53 School Elementary/Secondary 19 Rental Storage Facility (includes "Mini- Storage" and "Self-Storage" buildings) 54 Shelter Mission/Homeless 20 Residence or Home 55 Shopping Mall 21 Restaurant (includes cafeteria) 56 Tribal Lands 22 School (includes university) 57 Community Center 23 Service or Gas Station 58 Cyberspace September, 2016 LIBRS Specifications, Rel

73 Location Type (9) Examples: (1) 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 initiated and best describes the circumstances of the crime, Bar/Night Club ("03") should be entered. (2) 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 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"). September 2016 LIBRS Specifications, Rel

74 Number of Premises Entered (10) Data Characteristics: 2 Character Alpha/Numeric Requirements: 1) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on the Master LIBRS/LRS Code Table] of 220 and Louisiana Revised Statute is one of the following: 14:60/I 14:62/I 14: : : : : : :130.1/I 14:228/A4 and Location Type (9) contains Hotels/Motels/Etc. ("14") or Rental Storage Facility ("19"). Error ) MUST be numeric entry of if entered. Error ) When entered, Location Type 9 (9) must be Hotel/Motel/Etc. ("14") or Rental Storage Facility ("19"), and LRS (6) has a related NIBRS offense code of 220 [as defined on the Master LIBRS/LRS Code Table], and Louisiana Revised Statute (6) is one of the following: 14:60/I 14:62/I 14: : : : : : :130.1/I 14:228/A4 (Error Notes: 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., "ministorage" and "self storage" buildings. Example: A "self-storage" building was burglarized and 11 rented storage compartments were forcibly entered. The number "11" (for eleven compartments) should be entered into Number of Premises Entered (10). September, 2016 LIBRS Specifications, Rel

75 Method of Entry (11) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) MUST be entered if Louisiana Revised Statue (6) has a NIBRS offense code of 220 (Burglary) [as defined on Master LIBRS/LRS Code Table], and a Louisiana Revised Statute (6) that is one of the following: 14:60/I 14:62/I 14: : : : : : :130.1/I 14:228/A4 Error ) MUST be blank when offense code is not Burglary (NIBRS 220) and Louisiana Revised Statute (6) is not one of the following: 14:60/I 14:62/I 14: : : : : : :130.1/I 14:228/A4 Error Allowed Entries: Enter only one (1) code per Offense Segment: F N Force No Force Note: 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". Example: 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 and stole a typewriter. Since one door was forced, the Method of Entry should be entered as Force ( F ). September 2016 LIBRS Specifications, Rel

76 Type of Criminal Activity/Gang Information (12) Data Characteristics: 1 Character Alpha Requirements (Criminal Activity) 1) MUST be a valid code. Error ) If more than one code entered, CANNOT be a duplicate. Error ) MUST be entered if Louisiana Revised Statute (6) has a NIBRS offense code as defined on the Master LIBRS/LRS Code Table of: A... 35B C A... 90Z and is a "Crime Against Property" (LARS.ibrndxcl = Property ). The following LRS codes meet the above requirements (that is, NIBRS code + Crime Against Property): 14:59/A :59/A :59/A :59/A :59/A6...14:59/A7 14:59/A : : :70.4/X... 14: :72 14: : : : : : : :130.1/X... 14: : : :202 14:203 14: : : : : :212 14:218 14: : : : : :228/A1 14:228/A6X... 14:228/A : : : :353 14:405 14: : : : : :971/B1BX 40:971/B1D... 40:971/B1E... 40:971/B1F... 40:971/B1G... Error )(a) When NIBRS Offense Code is 250, then Type of Criminal Activity/Gang Information (12) MUST have a valid code. Error )(b) When NIBRS Offense Code is 35A or 35B, then Type of Criminal Activity/Gang Information (12) MUST have a valid code. Error )(c) When NIBRS Offense Code is 370, then Type of Criminal Activity/Gang Information (12) MUST have a valid code AND Type of Victim (25) MUST be Society ( S ). Error )(d) When NIBRS Offense Code is 280, then Type of Criminal Activity/Gang Information (12) MUST have a valid code. Error )(e) When NIBRS Offense Code is 520, then Type of Criminal Activity/Gang Information (12) AND Type of Weapon/Force Involved (13) MUST have a valid code AND Type of Victim (25) MUST be Society ( S ). Error September, 2016 LIBRS Specifications, Rel

77 Type of Criminal Activity/Gang Information (12) 3)(f) When NIBRS Offense Code is 39C, then Type of Criminal Activity/Gang Information (12) MUST have a valid code. Error Allowed Entries (Criminal Activity): Up to three (3) of the following Type of Criminal Activity Codes can be entered for each of the above Offenses: B C D E I O P T U X Buying/Receiving Cultivation/Manufacturing/Publishing (that is, production of any type) Distribution/Selling Exploiting Children Possession with Intent to Sell (reported to NIBRS as a P ) Operating/Promotion/Assisting Possessing/Concealing Transporting/Transmitting/Importing Using/Consuming Other (reported to NIBRS as a "P") Example: The Offenders published and sold pornographic photographs of children. Therefore, up to three types of Criminal Activity can be entered: Cultivating/Manufacture/Publishing ( C ), Distributing/Selling ( D ), and Exploiting Children ("E"). Requirements (Gang Information): 4) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined in the Master LIBRS/LRS Code Table] of: 09A... 09B A... 11B... 11C... 11D A... 13B... 13C and is a "Crime Against Person" (LARS.ibrndxcl = Person ) for NIBRS Offense codes 09A, 09B, 100, 11A, 11B, 11C, 11D, 13A, 13B and 13C, or is a Crime Against Property (LARS.ibrndxcl = Property ) for NIBRS Offense code 120. The following LRS codes meet the above requirements (that is, NIBRS code + Crime Against Property/Person): 14: : : : :32.1/AA 14: : : : : : : : : :35 14: : : :35.3/M... 14:37 14: : : : : : : : : :39.1 September 2016 LIBRS Specifications, Rel

78 Type of Criminal Activity/Gang Information (12) 14: : : : : : : : : :42/A 14:42/V... 14:42.1/A... 14:42.1/V... 14:43/A... 14:43/V 14:43.1/N... 14:43.1/P... 14:43.2/N... 14:43.2/P... 14: : : : : :44.1/A 14:44.1/N... 14:44.1/O... 14:44.1/P... 14:44.1/V... 14: : : : : :46:30 14: : : : :64 14: : : : :65 14:65.1/F... 14: : : :87.2/F 14:87.2/L... 14:87.5/F... 14:87.5/L... 14: : :93/F... 14: : :94/E... 14:103/A1 14:107.1/F... 14:108/B1B... 14:108/B1BF.. 14: :122/F 14:122/T... 14: : :129/A :129/A2F 14:129/A2T... 14: :129.1/F... 14:129.1/T... 14:130.1/A 14:130.1/T... 14:130.1/F... 14:133.1/F... 14:133.1/T... 14:285 14:404/Q... 14: Error Notes (Criminal Activity): Use this data element to provide additional information on the criminal activity of Offender(s) in the incident. 5) A value of None/Unknown ( N ) is mutually exclusive with any other Gang Information codes. Error Notes (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. Allowed Entries (Gang Information): Two (2) Gang Information codes can be entered for each of the above offenses: J G N Juvenile Gang Other Gang None/Unknown Example (Gang Information): 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 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 September, 2016 LIBRS Specifications, Rel

79 Type of Criminal Activity/Gang Information (12) associated with a local gang. The entry for Type of Criminal Activity/Gang Information should be Juvenile Gang ( J ). Note (Gang Information): If a value of None/Unknown ( N ) is entered, codes "J" and "G" cannot to be entered. September 2016 LIBRS Specifications, Rel

80 Type of Weapon/Force Involved (13) Data Characteristics: 3 Character Alpha Requirements: 1) MUST be a valid code. Error ) If more than one code entered, CANNOT be a duplicate. Error ) Value "99" (None) is mutually exclusive with any other value, i.e. "99" to be entered only if no other code applies. Error ) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: 09A... 09B... 09C A... 11B... 11C... 11D A... 13B The following LRS codes are the Louisiana equivalent of the above NIBRS Offense codes: 14: : : : :32 14:32.1/AA... 14: : : : : : : : : : : : : :35.3/M 14: : : : : : : : : : : :42/A... 14:42/V... 14:42.1/A... 14:42.1/V 14:43/A... 14:43/V... 14:43.1/P... 14:43.1/N... 14:43.2/P 14:43.2/N... 14: : : :44 14: :44.1/V... 14:44.1/A... 14:44.1/O... 14:44.1/P 14:44.1/N... 14: : : :46 14: : : : :59/A9 14: : : : : : : : :65.1/F... 14:66 14: : :87.2/F... 14:87.2/L... 14:87.5/F 14:87.5/L... 14: : : :93/F 14: : :94/E... 14:94/F... 14:95 14: : : : : : : : : : : :103/A :107.1/F... 14:108/B1B... 14:108/B1BF 14: :122/F... 14:129/A2F... 14: :129.1/F 14:130.1/A... 14:130.1/F... 14:133.1/F... 14: :136 14:404/Q 14: : : : : : : : : : :1792 Error September, 2016 LIBRS Specifications, Rel

81 Type of Weapon/Force Involved (13) 5) If the firearm is one of the following types of automatic weapons, add "A" as the third character: Firearm (Type not Stated) Handgun Rifle Shotgun Other Firearm. Error ) The third character of Type of Weapon/Force Involved (13) MUST be Automatic (A) or Blank (G). Error ) When an Offense Segment (20) is submitted for one of the following Louisiana Revised Statutes (6), the Offense will be reported to the FBI as a Simple Assault (13B) and MUST have Personal Weapons (40), Other (90), Unknown (95), or None (99) entered in Type of Weapon/Forced Involved: 14: : : :34.5.1*... 14:35 14: : :35.3*... 14: : :38.3*... 14:103/A :108/B1B... 14: :130.1/A Error ) When a Homicide Offense (NIBRS 09A, 09B or 09C) is submitted, Type of Weapon/Force Involved (13) CANNOT have None (99) entered. Some Type of Weapon/Force Involved, other than None (99), MUST be used in a Homicide Offense. Below are the Louisiana Revised Statutes (6) for Homicide Offenses in Louisiana: 14: : : : :32 14:32.1/AA... 14: :87.2/L... 14:87.5/L... 14:501 Error ) If the Louisiana Revised Statute (6) is a simple assault (NIBRS 13B), but the weapon involved is: Firearm 11A... Automatic Firearm Handgun 12A... Automatic Handgun Rifle 13A... Automatic Rifle Shotgun 14A... Automatic Shotgun Other Firearm 15A... Other Automatic Firearm then this Offense should be reported as an Aggravated Assault (NIBRS 13A). Error ) For Human Trafficking Offenses (NIBRS Codes 64A, 64B and 40C), a data value for Type of Weapon/Force Involved (13) MUST be specified. ***New in LIBRS 2.2 *** September 2016 LIBRS Specifications, Rel

82 Type of Weapon/Force Involved (13) Notes: 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. Allowed Entries: Can enter up to three (3) codes for each of the above offenses: 11 Firearm (type not stated) 12 Handgun 13 Rifle 14 Shotgun 15 Other Firearm 20 Knife/Cutting Instrument (e.g., ax, ice pick, screwdriver, switchblade, etc.) 30 Blunt Object (e.g., club, hammer, etc.) 35 Motor Vehicle (when used as a weapon) 40 Personal Weapons (i.e., hands, feet, teeth, etc.) 50 Poison 60 Explosives 65 Fire/Incendiary Device 70 Drugs/Narcotics/Sleeping Pills 85 Asphyxiation (by drowning, strangulation, suffocation, gas, etc.) 90 Other (any weapon or force not fitting the above specifically coded weapon/force. Should include toy or pretend weapons if Victim thought it was real. Can also include deadly diseases.) 95 Unknown 99 None Example: 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 would be: Handgun ("12"), Shotgun ("14") and Other Automatic Firearm ("15A ). September, 2016 LIBRS Specifications, Rel

83 Data Characteristics: 3 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Property Sequence Number (P1) *** New Data Element in LIBRS 2.2 *** 2) MUST be numeric entry (001 through 999) with zero left-fill. Property Sequence Number (P1) distinguishes one property from another. 3) MUST be unique -- CANNOT be duplicated. Note: Each property in an incident must be assigned a unique sequence number from "001" to "999". September 2016 LIBRS Specifications, Rel

84 Type of Property Loss (14) Data Characteristics: 1 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) When Type of Property Loss (14) is None (1) or Unknown (8), then Data Elements 15 through 22 MUST be Blank ( ) for all Offenses, except when the following Louisiana Revised Statute (6) Drug Violation Offenses (NIBRS 35A) are reported: 14:30.1/D... 32: : : : : : : : :966 40: : : : : : : : : : : : : : : : : : : If Type of Property Loss (14) has a value of None ( 1 ) entered when one of the above LRS codes is present in the incident, then Suspected Drug Type (20) MUST have a valid entry. Error (a) [This edit applies to the LRS codes listed above, ONLY.] If Offense Attempted/Completed (7) is Attempted ( A ), then Type of Property Loss (14) MUST be None ("1") or Unknown ("8"). These are the only two data values accepted. (Errors 84001, 84003, 84104, 84105, 84006, 84107, 84108, 84009, 84010, 84112, 84013, 84014, 84117, 84120) 4) Type of Property Loss (14) MUST be entered if Louisiana Revised Statute (6) has one of the following NIBRS Offense codes [as defined on Master LIBRS/LRS Code Table]: A... 23B... 23C... 23D... 23E... 23F... 23G... 23H A... 26B... 26C... 26D... 26E A... 35B 39A... 39B... 39C... 39D A... 90Z and is a Crime Against Property (LARS.ibrndxcl = Property ). The following LRS codes meet the above requirements (that is, NIBRS code + Crime Against Property): 14:51/H... 14:51/U... 14:52.1/H... 14:52.1/U... 14:52/H 14:52/U... 14:53/H... 14:53/U... 14:54/H... 14:54/U 14: : : : :56.4 September, 2016 LIBRS Specifications, Rel

85 Type of Property Loss(14) 14: : :59/A :59/A :59/A3 4:59/A :59/A :59/A :59/A :59/A8 14:59/A : :60/I... 14:62/I... 14:62/M 14:62/Z... 14: : : : : : : : : : : : : : : : :65.1/F... 14: :67 14:67/B... 14:67/C... 14:67/E... 14:67/K... 14:67/S 14:67/Z... 14: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :69 14: : : : : : :70.4/FR... 14:70.4/X... 14: :70.5/FR 14: : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :130.1/B 14:130.1/I... 14:130.1/X... 14:130.1/Y... 14: :132 14: : : : :136 14: : : : :140 14:141 14: : : : :204 14:205/H... 14:205/U... 14: : :208 14: : : : :213 14: : : : : : : : : : : : : : :225 14: : : :228/A :228/A2 14:228/A :228/A :228/A :228/A6Y... 14:228/A6X 14:228/A : : : :331 14: : : : :511 14: : : : : : :98/B... 27:98/C... 27: :100/A 27:100/B... 27: : :264/A... 27:264/B 32: : : :971/B1A... 40:971/B1B 40:971/B1BX.. 40:971/B1C... 40:971/B1D... 40:971/B1E... 40:971/B1F 40:971/B1G... 40:971/B1H... 40: :1321.G... 46:114.2 Error ) For every Property Description code (15) entered into a Property Description Segment (31) having a Type of Property Loss (14) of Recovered ( 5 ), there MUST also be a corresponding Property Description Segment (31) with a matching Property Description (15) code and a Type of Property Loss (14) of Stolen/Etc. ("7"). This September 2016 LIBRS Specifications, Rel

86 Type of Property Loss (14) applies to both initial submissions and resubmissions for Incident Reports (Action Type of I ). This rule DOES NOT apply, of course, for Offenses that allow for property to be Recovered without first being Stolen. Specifically, it does not apply to NIBRS Offense codes of 280 and 250. Nor does it apply when a Property Description of Vehicle Parts/Accessories ("38") is subsequently reported as Recovered when a vehicle was stolen, and individual parts within a vehicle were not reported as Stolen. Error ) When the Type of Property Loss is Burned ("2") Counterfeited/Forged ("3"), Destroyed /Damaged/Vandalized ("4") Recovered ("5") Seized ("6") Stolen/Etc. ("7") then the following data elements in the Property Description Segment (31) must have applicable entries Property Description (15) Value of Property (16) Date Recovered (17) Number of Stolen Motor Vehicles (18) Number of Recovered Motor Vehicles (19) Suspected Drug Type (20) Estimated Drug Quantity (21) Type of Drug Measurement (22) Error ) When making a Time-Window Submission (Action Type of "W") or Modifying a previously submitted incident (Action Type of "M"), then Type of Property Loss/Etc. (14) MUST be Recovered ("5"). Error ) 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 Stolen Property ( 7 ) or Unknown ("8"), but not a combination of the two. 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. Error 84203, 84304, ) To ensure that Drug/Narcotic Offenses (NIBRS 35A and 35B) are properly reported, Property Description (15) CANNOT have a value of Drug/Narcotic Equipment ("11") for a Drug/Narcotic Violation of NIBRS 35A. Similarly, Drug/Narcotics ("10") September, 2016 LIBRS Specifications, Rel

87 Type of Property Loss (14) CANNOT be entered for a Drug Equipment Violation of (35B). This is enforced by software when there is a single Crime Against Property Offense. However, when an incident contains multiple Crimes Against Property Offenses, where, for example, one Offense is a Drug/Narcotic Violation (NIBRS 35A), and the other is a Robbery (NIBRS 120), that involves Drug/Narcotic Equipment ("11"), it can be entered. In this case, the above edit rule should be bypassed. Similarly, Drugs/Narcotics ("10") can be entered along with a Drug Equipment Violation (35B), as long as that property is involved in the Robbery (NIBRS 120). Error ) The Type of Property Loss code (14) must be applicable to Offense(s) submitted in Louisiana Revised Statutes (6). Refer to Mandatories for the correct values to use for each of the offenses. Error Notes: 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. Allowed Entries: Enter only one (1) code for each Property Description Segment. However, as many property segments as applicable can be submitted per incident: 1 None 2 Burned (includes damage caused in fighting the fire) 3 Counterfeited/Forged 4 Destroyed/Damaged/Vandalized 5 Recovered (to impound property that was previously stolen) 6 Seized (to impound property that was not previous stolen, 250, 35A, 35B, and 39A-39D are the only offenses that will be accepted as seized) 7 Stolen/Etc. (includes bribed, defrauded, embezzled, extorted, ransomed, robbed 8 Unknown September 2016 LIBRS Specifications, Rel

88 Property Description (15) Data Characteristics: 2 Character Alpha/Numeric Requirements: 1) MUST be a valid code. Error ) If more than one code entered, CANNOT be duplicates. Error ) When Pending Inventory ("88") is entered, then Value of Property (16) MUST be Unknown ("1", representing $1.00). One dollar is used as a quality assurance edit check that instructs LIBRS to accept the Pending Inventory ("88") entry. Error ) A Property Description (15) code MUST be entered when the value entered in Type of Property Loss/Etc. (14) contains the following: Burned ( 2 ) Counterfeited or Forged ( 3 ) Destroyed, Damaged or Vandalized ( 4 ) Recovered ( 5 ) Seized ( 6 ) Stolen/Etc. ( 7 ). Error ) For every Property Description code (15) entered into a Property Description Segment (31) having a Type of Property Loss (14) of Recovered ( 5 ), there MUST also be a corresponding Property Description Segment (31) with a matching Property Description (15) code and a Type of Property Loss (14) of Stolen/Etc. ("7"). This applies to both initial submissions and resubmissions for Incident Reports (Action Type of I ). This rule DOES NOT apply, of course, for Offenses that allow for property to be Recovered without first being Stolen. Specifically, it does not apply to NIBRS Offense codes of 280 and 250. Nor does it apply when a Property Description of Vehicle Parts/Accessories ("38") is subsequently reported as Recovered when a vehicle was stolen, and individual parts within a vehicle were not reported as Stolen. (Error 10072, modified) Note: Property Description (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 one Property Description (15) code per Property Description (31) Segment, but can enter multiple Property Description (31) Segments. Do NOT enter duplicate Property Description (15) codes within an Incident, UNLESS a different Type of Property Loss (14) code is used. An exception would be if there is more than one Drug that was Seized in the Incident. However, rules found in the Mandatory Data Element Requirements must still be followed. September, 2016 LIBRS Specifications, Rel

89 Property Description (15) *** Cells Shaded Brown (41 thru 76, and 78 thru 80) are new Property Descriptions, beginning with LIBRS 2.2. *** 01 Aircraft (airplanes, dirigibles, gliders, etc.) 02 Alcohol (alcoholic beverages, e.g., beer, wine, liquor, etc.) 03 Automobiles (all vehicles that serve the primary purpose of transporting people) 04 Bicycles (includes all cycles regardless of number of wheels) Buses (motor vehicles that are specifically designed, but not necessarily used, to transport groups of people on a commercial basis) Clothes/Furs (wearing apparel for human use, including accessories such as belts, shoes, scarves, ties, etc.) 07 Computer Hardware/Software (computers, computer peripherals, and storage media) 08 Consumable Goods (expendable items to be used by humans for nutrition, enjoyment, or hygiene, e.g., food, beverages, grooming products, cigarettes, gasoline, firewood, etc.) 09 Credit/Debit Cards (includes automatic teller cards) 10 Drugs/Narcotics 11 Drug Narcotic Equipment 12 Farm Equipment (tractors, combines, etc.) 13 Firearms (excluding air powered or gas powered guns) 14 Gambling Equipment (gambling paraphernalia) 15 Heavy Construction / Industrial Equipment 16 Household Goods (beds, chairs, desks, sofas, tables, refrigerators, stoves, washer/dryers, air conditioning and heating equipment, small appliances, etc.) 17 Jewelry / Precious Metals 18 Livestock (excluding household pets, such as cats and dogs) 19 Merchandise (items held for sale) 20 Money (legal tender, coins and paper currency) Negotiable Instruments (any document, other than currency which is payable without restriction, e.g., endorsed checks, endorsed money orders, bearer bonds, etc.) Nonnegotiable Instruments (documents requiring further action to become negotiable, e.g., unendorsed checks, food stamps, stocks and bonds, etc.) 23 Office-type Equipment (typewriters, cash registers, etc.) 24 Other Motor Vehicles (any other motor vehicles, e.g., motorcycles, motor scooters, snowmobiles, golf carts, etc.) 25 Purses/Handbags / Wallets 26 Radios/TV's/ VCR's (includes cameras, all stereo and video equipment) 27 Recordings-Audio/Visual (includes all media capable of reproducing audio or video) 28 Recreational Vehicles (motor vehicles that are specifically designed, but not necessarily used, to transport people and also provide temporary lodging for recreational purposes) September 2016 LIBRS Specifications, Rel

90 Property Description (15) Structures-Single Occupancy Dwellings (houses, town houses, duplexes, mobile homes, or other private dwellings which are occupied by a single person, family, house mates, or other group) Structures-Other Dwellings (any other residential dwellings not meeting the definition of "Single Occupancy Dwellings," e.g., apartments, tenements, flats, boarding houses, dormitories, as well as temporary living quarters, such as hotels, motels, inns, etc.) 31 Structures-Other Commercial/Business (stores, office buildings, restaurants, etc.) 32 Structures-Industrial/Manufacturing (factories, plants, assembly lines, etc.) 33 Structures- Public/Community (colleges, hospitals, jails, libraries, meeting halls, passenger terminals, religious buildings, schools, sports arenas, etc.) 34 Structures-Storage (barns, garages, storehouses, warehouses, etc.) 35 Structures-Other (any other structure not fitting in the "Structures" descriptions, e.g., outbuildings, monuments, buildings under construction, etc.) 36 Tools (hand and power tools) Trucks (motor vehicles specifically designed, but not necessarily used, to transport cargo on a commercial basis) Vehicle Parts/Accessories (motor vehicle batteries, engines, transmissions, heaters, hubcaps, tires, manufacturers' emblems, license plates, side view mirrors, radios, antennas, tape decks, etc.) 39 Watercraft (motorboats, sailboats, houseboats, etc.) 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 September, 2016 LIBRS Specifications, Rel

91 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 Property Description (15) Other (all other property not fitting the above specific descriptions. This includes "intangibles" which are anything which CANNOT be perceived by the sense of touch; i.e., benefits, a right or privilege, a promotion, enhanced reputation; or a detriment, e.g., a loss of reputation, injured feelings, etc.) 78 Trailers 79 Watercraft Equipment/Parts/Accessories 80 Weapons Other 88 Pending Inventory (property description unknown until an inventory is conducted) 99 (G, Blank ) (special category to be used by the National NIBRS program to compile statistics on certain designated types of property, e.g., "CB" radios, which are the object of theft fads. Since this code is not designated at this time, types of property should be appropriated into another code.) September 2016 LIBRS Specifications, Rel

92 Value of Property (16) Data Characteristics: 9 Character Numeric Requirements: 1) MUST be numeric entry with zero or blank left-fill if entered. Error ) If Value of Property (16) is unknown, must enter a value of Unknown ( 1, representing $1.00). A value of ZERO ( 0 ) is allowed only when Property Description (15) codes are the following: Credit/Debit Cards (ZERO ( 0 ) value is required) Nonnegotiable Instruments (ZERO ( 0 ) value is required) Other Special Category. Error ) When Property Description (15) has Credit/Debit Cards ("09") or Nonnegotiable Instruments ("22") entered, a ZERO ( 0 ) value is required for Value of Property (16). Errors ) If a Value of Property (16) has a code entered, then Property Description (15) MUST be entered. Error ) For Property Description Segments (31) having Type of Property Loss (14) entries for both Stolen/Etc. ( 7 ) and Recovered ("5"), the Recovered "property" CANNOT have Value of Property (16) value(s) greater than corresponding Stolen property Value of Property (16) value(s). Error ) When Value of Property (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 if it was an intended entry. Also, a Warning message is always produced when the value is $1,000,000 or greater. For example, if the value of a property was $12, but was inadvertently entered as $1,200,099 in LIBRS submission file, a "Warning" message will be generated. In this case, the cents were entered as whole dollars. Error September, 2016 LIBRS Specifications, Rel

93 Value of Property (16) Notes: 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, " ". If value is known and it is between $1.00 and $2.00 the reporting agency should enter $2.00, that is, " ". This is the minimum dollar value that can be entered in Value of Property (16), as "1" (or ) is used for Unknown. Example: 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 $ The value of the property would be rounded to the nearest whole dollar and reported as " "- $ September 2016 LIBRS Specifications, Rel

94 Date Recovered (17) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) Each component of the date must be valid: months must be 01-12, days must be 01-31, and year must include the century (i.e., 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (e.g., June CANNOT have 31 days). The date CANNOT be greater than that entered within the "Month of Submission" and "Year of Submission" fields on the data record. For example, if "Month of Submission" and "Year of Submission" are "06/1995," the recovered date CANNOT contain any date 07/01/1995 or greater. Error ) CANNOT be earlier than Incident Date/Hour (3). Error ) If entered, then both Property Description (15) and Value of Property (16) MUST be entered. Error ) If entered, Type of Property Loss (14) must be Recovered ( 5 ). Error ) Property Description Segments (31) submitted with as part of a Time-Window (Action Type of "W") CANNOT HAVE a Date Recovered (17) BEFORE the date which is calculated using the Base Date technique (January 1 of the year prior to the current year, or earlier than the date the agency started submitting Incident-Based Reporting data). For any subsequent Modify (Action Type of "M ) submission of a previously submitted Time-Window Submission (Action Type of "W"), this edit also applies. Error Note: 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 (17) for the same Property Description (15), enter the earliest date. If the Date Recovered is unknown, enter the date of the report. Example: On March 28, 2014, three (3) cars were stolen from a used car lot. One of the cars was recovered on July 1, On July 24, 2014, the second car was recovered. The date entered into this data element should be " ". September, 2016 LIBRS Specifications, Rel

95 Data Characteristics: 2 Character Alpha/Numeric Number of Stolen Vehicles (18) Requirements: 1) MUST be numeric entry with zero left-fill, if entered. Error ) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 240 or hard coded edit based on Property Description (15) having Motor Vehicle codes, and Type of Property Loss/Etc. (14) is Stolen (7), and the Louisiana Revised Statute Number MUST BE one of the following: 14: : :68.4 and Type Property Loss/Etc. (14) MUST be Stolen/Etc ("7") and Offense Attempted/ Completed (7) MUST also be Completed ( C ). (Error ) Entry MUST be made when Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 240, or hard coded edit based on Property Description (15) having Motor Vehicle codes as property being stolen and the Louisiana Revised Statute Number MUST BE one of the following: 14: : :68.4 and Type Property Loss/Etc. (14) is Stolen/Etc. ("7") and Offense Attempted/ Completed (7) is Completed ("C"). Error ) Property Description (15) MUST contain AT LEAST ONE of the following vehicle codes: Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks. Error ) If more than one vehicle code is entered in Property Description (15), then Number of Stolen Vehicles (18) MUST BE EQUAL TO OR GREATER THAN this number of different codes, unless the number of stolen vehicles is Unknown ("00"). Error ) If the Louisiana Revised Statute code (6) of 14:67 is submitted without a Qualifier but Property Description (15) is one of the following: Automobiles Buses Other Motor Vehicles September 2016 LIBRS Specifications, Rel

96 Number of Stolen Vehicles (18) Recreational Vehicles Trucks then the agency will receive this warning message: WARNING -- This LRS submitted without a Qualifier and "03", "05", "24", "28", or "37" in DE # 15 will be reported as Motor Vehicle Theft (240)." If this is not the correct property description code resubmit property description code. WARNING ) If the Louisiana Revised Statute code of 14:68 is submitted and if Property Description (15) is not equal to: Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks then the agency will receive this warning message: WARNING-- This LRS submitted will be reported as All Other Larceny-Theft (23H). If this is not the correct property description code resubmit property description code. WARNING ) If Louisiana Revised Statute code (6) of 14:68 is submitted and if Property Description (15) is Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks. which equals Motor Vehicle Theft (240), then the agency would receive this warning message: WARNING-- This LRS submitted and 03", 05", 24", 28" or 37", in DE # 15 will be reported as Motor Vehicle Theft (240). If this is not the correct property description code resubmit property description code. WARNING ) Number of Stolen Vehicles (18) MUST BE LEFT BLANK (G) if the Louisiana Revised Statute (6) Offense IS NOT REPORTED AS A MOTOR VEHICLE Theft (240) or hard coded edit based on Property Description (15) does not list one of the following Motor Vehicle codes as Stolen property Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks. Error September, 2016 LIBRS Specifications, Rel

97 Number of Stolen Vehicles (18) Note: Number of Stolen Vehicles (18) indicates how many motor vehicles were stolen in an incident reported as a Motor Vehicle Theft. September 2016 LIBRS Specifications, Rel

98 Number of Recovered Motor Vehicles (19) Data Characteristics: 2 Character Alpha/Numeric Requirements: 1) MUST be a numeric entry with zero left-fill if entered. Error ) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 240 or has a hard-coded edit based on Property Description (15) containing a Motor Vehicle code indicating Recovered Property and with a Louisiana Revised Statute (6) from the following list: 14: : :68.4 and Type of Property Loss (14) is Recovered ( 5 ). Error ) If number between 01 and 99 is entered, it MUST BE EQUAL TO OR LESS THAN the number reported Stolen in Number of Stolen Motor Vehicles (18). Error ) Entry must be made when Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: 240 or hard-coded edit based on Property Description (15) containing Motor Vehicle codes indicating Recovered property and Louisiana Revised Statute (6) MUST BE one of the following: 14: : :68.4 and Type of Property Loss (14) is Recovered ( 5 ), and Property Description (15) contains a vehicle code. Error ) When "01" to "99" is entered into Number of Recovered Motor Vehicles (19), then Property Description (15) must contain at least one of the following vehicle codes: Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks Error ) The Number of Recovered Motor Vehicles (19) must be greater than or equal to the number of Property Description (15) entries with motor vehicle designation. For example, if Property Description (15) vehicle codes of Automobiles ( 03 ) and Buses ("05") have corresponding Type of Property Loss (14) entries of Recovered ( 5 ), then the Number of Recovered Motor Vehicles (19) MUST be at least 2, UNLESS the Number of Recovered Motor Vehicles (19) is Unknown ("00"). Error September, 2016 LIBRS Specifications, Rel

99 Number of Recovered Motor Vehicles (19) 7) Number of Recovered Motor Vehicles (19) MUST BE LEFT BLANK if the LRS Offense is NOT reported as a Motor Vehicle Theft (NIBRS 240), or Type of Property Loss (14) shows NO Recovered ( 5 ) property with a Property Description (15) from the following list of motor vehicle codes: Automobiles Buses Other Motor Vehicles Recreational Vehicles Trucks Error Note: Number of Recovered Motor Vehicles (19) indicates how many motor vehicles were recovered in an incident that reported Motor Vehicle Thefts. September 2016 LIBRS Specifications, Rel

100 Suspected Drug Type (20) Data Characteristics: 2 Character Alpha Requirements: 1) Suspected Drug Type (20 ) MUST be entered if Louisiana Revised Statutes (6) has a NIBRS offense code [as defined on Master LIBRS/LRS Code Table] of 35A and Louisiana Revised Statute (6) is one of the following: 14:30.1/D... 32: : : : : : : : :966 40: : : : : : : : : : : : : : : : : : : and Type of Property Loss (4) has a value of Seized ("6") and Property Description (15) has a value of Drugs/Narcotics ("10"). If there are multiple LRS Offenses (6) listed and Drugs/Narcotics ( 10 ) was split between the different types of LRS Offenses (6), only enter the Suspected Drug Types (20) applicable to the Offenses listed above. Error ) When more than one Suspected Drug Type (20) code is entered, there can be NO duplicates. Error ) MUST be a valid code. Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 35A and Louisiana Revised Statute (6) is one of the following: 14:30.1/D... 32: : : : : : : : :966 40: : : : : : : : : : : : : : : : : : : and, Type Property Loss (14) is Seized ("10"), Property Description (15) is Drugs/Narcotics ("10"), and a Suspected Drug Type (20) is entered, then Estimated Quantity (21), Type Drug Measurement (22), and Value of Property (16) MUST BE ENTERED. Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 35A and the Louisiana Revised Statute (6) is one of the following: 14:30.1/D... 32: : : : September, 2016 LIBRS Specifications, Rel

101 Suspected Drug Type (20) 40: : : : :966 40: : : : : : : : : : : : : : : : : : : and Type Property Loss (14) is None ("1") then Suspected Drug Type (20) is required. However, if Type Property Loss (14) of Seized ("6") is also reported, THIS EDIT IS BYPASSED. Errors ) Second character must be "X" (indicates Counterfeit), or Blank G. Error Notes: 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. Allowed Entries: Enter as many as apply, but DO NOT DUPLICATE CODES. Allowed Entries: Description: Reported to NIBRS as: Drug Measurement Category to be used: A Crack Cocaine A WEIGHT B Cocaine (all forms except crack) B WEIGHT C Hashish C WEIGHT D Heroin D WEIGHT E Marijuana E WEIGHT F Morphine F CAPACITY G Opium G WEIGHT H Other Narcotics H UNITS I LSD I UNITS J PCP J CAPACITY September 2016 LIBRS Specifications, Rel

102 Suspected Drug Type (20) K Other Hallucinogens K UNITS L Amphetamines / Methamphetamines L WEIGHT M Other Stimulants M UNITS N Barbiturates N UNITS O Other Depressants O UNITS P Other Drugs P UNITS U Unknown Type Drug U any September, 2016 LIBRS Specifications, Rel

103 Estimated Drug Quantity (21) Data Characteristics: 13 Character Alpha/Numeric Format: #########.### Requirements: 1) MUST be numeric entry with Zero ( 0 ) or Blank (G) left-fill and right-fill. The decimal fractional quantity must be expressed in thousandths as three digits, and a decimal point must separate the whole part of the number from the fractional part. The DECIMAL POINT MUST BE THE TENTH CHARACTER OF THE FIELD. Error ) When Estimated Drug Quantity (21) is entered, Suspected Drug Type (20), Type Drug Measurement (22) and Value of Property (16) MUST ALSO BE ENTERED. Error ) Estimated Drug Quantity (21) is valid only if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 35A and Louisiana Revised Statute (6) that is one of the following: 14:30.1/D... 32: : : : : : : : :966 40: : : : : : : : : : : : : : : : : : : and, Type of Property Loss (14) is Seized ("6"), and Property Description (15) is Drugs/Narcotics ("10"). Error Notes: 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 " ", 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 ( ). If LRS Offense (6) is not reportable as a drug violation (35A), this data element MUST BE LEFT BLANK (G). September 2016 LIBRS Specifications, Rel

104 Type Drug Measurement (22) Data Characteristics: 2 Character Alpha Requirements: 1) MUST be a valid code, if entered. Error ) Type Drug Measurement (22) is used if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 35A and the Louisiana Revised Statute (6) is one of the following: 14:30.1/D... 32: : : : : : : : :966 40: : : : : : : : : : : : : : : : : : : and Type of Property Loss (14) is Seized ( 6 ), and Property Description (15) is Drugs/Narcotics ("10"). Error ) Each Suspected Drug Type (DE20) can only be measured using its corresponding measurement category. Error ) When Type Drug Measurement is entered, then Suspected Drug Type (20), Estimated Drug Quantity (21), and Value of Property (16) must also be completed. Error ) Estimated Drug Quantity (21) must have a value of " " when Type Drug Measurement (22) is Not Reported ("XX") and Value of Property (16) is Unknown ("1"). Submission of a Not Reported( XX ) for Type Drug Measurement (22) requires that a value of " " also be submitted for Estimated Drug Quantity (21) Note: Type Drug Measurement (22 ) indicates how Seized drugs and narcotics are quantified in a drug case. as a quality assurance check. Once the Type Drug Measurement (22) has been determined, the Incident will need to be resubmitted reflecting the completed data. Error September, 2016 LIBRS Specifications, Rel

105 Type Drug Measurement (22) Allowed Entries: Weight Category GM Gram KG Kilogram OZ Ounce LB Pound Capacity 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. NC Number of Cigarettes (Marijuana cigarettes only) Other XX Not Reported/Unknown September 2016 LIBRS Specifications, Rel

106 Victim Sequence Number (23) Data Characteristics: 3 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be numeric entry (001 through 999) with ZERO LEFT-FILL. The purpose of Victim Sequence Number is to distinguish one victim from another. Error ) MUST be unique - CAN NOT HAVE DUPLICATES. Error Note: Each victim in an incident MUST be assigned a unique Victim Sequence Number (23) from "001" to "999". September, 2016 LIBRS Specifications, Rel

107 Offense Connected to Victim Sequence Number (24) Data Characteristics: 3 Character Numeric Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) If the Offense is a Crime Against Person, and the Offense is connected to a Victim, then Type of Victim (25) must be an Individual ( I ) or Law Enforcement Officer ("L"). Error ) If the Offense is a Crime Against Society, and the Offense is connected to a Victim, then Type of Victim (25) must be Society ( S ). Error ) Each Offense Connected to Victim Sequence Number (24) entered in the Offense Segment (20) MUST also have a corresponding Victim Sequence Number (23 ) entered in a Victim Segment (50). Error ) When Offense Connected to Victim Sequence Number (24) relates to the Offense of Simple Assault (NIBRS "13B"), there CANNOT be "major" injury codes indicating an Aggravated Assault. The permissible codes are Apparent Minor Injury ("M") and None ("N"). Error ) Each Offense Segment (20) must have a corresponding Victim segment (50). Error ) Victim CANNOT be connected to Mutually Exclusive or Lesser Included Offenses. Error Offenses are Mutually Exclusive when they CANNOT occur to the same victim in an incident by NIBRS definitions. Offenses are Lesser Included when, in the same incident, one Offense is an element of a second Offense, and should not both be reported as having happened to the Victim. The chart on the following page 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. September 2016 LIBRS Specifications, Rel

108 09A Murder 09A--Murder 09B Negligent Manslaughter 09B--Negligent Manslaughter 11A Forcible Rape 11A--Forcible Rape 11B Forcible Sodomy 11B--Forcible Sodomy 11C Sexual Assault w/ Object 11C--Sexual Assault w/ Object 11D Forcible Fondling 11D--Forcible Fondling 120 Robbery 120--Robbery 13A Aggravated Assault 13A--Aggravated Assault 13B Simple Assault 13B--Simple Assault 13C Intimidation 13C--Intimidation 23A Pocket-Picking 23A--Pocket-Picking 23B Purse Snatching 23B--Purse Snatching 23C Shoplifting 23C--Shoplifting 23D Theft from Building 23D--Theft from Building 23E Theft from Coin Machine 23E--Theft from Coin Machine 23F Theft from Motor Vehicle 23F--Theft from Motor Vehicle 23G Theft of Motor Vehicle Parts 23G--Theft of Motor Vehicle Parts 23H All Other Larceny 23H--All Other Larceny 240 Motor Vehicle Theft 240--Motor Vehicle Theft 36A Incest 36A--Incest 36B Statutory Rape 36B--Statutory Rape Offense Connected to Victim Sequence Number (24) 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 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 Motor Vehicle Theft X X 36A... Incest X X X X X 36B... Statutory Rape X X X X X 09C Justifiable Homicide CANNOT occur with any other offense. September, 2016 LIBRS Specifications, Rel

109 Offense Connected to Victim Sequence Number (24) Note: 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. Example: 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. Offense Aggravated Robbery (14:64) would be connected to Victim 002. Offense Second Degree Kidnaping (14:44.1) would be connected to Victim 001. September 2016 LIBRS Specifications, Rel

110 Type of Victim (25) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be blank. Error ) MUST be a valid code. Error ) When Offense is a Crime Against Person, and the Offense is connected to a Victim, then Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L"). Error ) When Offense is a Crime Against Society, and the Offense is connected to a Victim, then Type of Victim (25) MUST be Society ("S"). Error ) When Offense is a Crime Against Property, and the Offense is connected to a Victim, then Type of Victim (25) CANNOT be Society ( S"). Type of Victim (25) CAN ONLY BE: I... Individual B... Business F... Financial Institution G... Government R... Religious Organization O... Other U... Unknown Error ) Crimes Against Society can have ONLY ONE VICTIM. Error ) Type of Victim (25) MUST be Law Enforcement Officer ("L") when submitting the following Louisiana Revised Statute codes: 14: : :34.2. Error ) For Human Trafficking Offenses (NIBRS Codes 64A, 64B and 40C), the data value for Type of Victim (25) MUST be Individual ("I"). ***New in LIBRS 2.2 *** Allowed Entries: Enter only one (1) code per Victim Segment (50): I B F G L R S O Individual Business Financial Institution Government Law Enforcement Officer (used to identify LEOKA assaults and homicides to Law Enforcement Officers In-the-Line-of-duty) reported to NIBRS as an Individual ( I ). Religious Organization Society/Public Other September, 2016 LIBRS Specifications, Rel

111 U Unknown Type of Victim (25) Note: 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. Example: 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 three victims: 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") September 2016 LIBRS Specifications, Rel

112 Age of Victim (26) [At Time Incident Occurred] Data Characteristics: 3 Character Alpha Requirements: 1) MUST be present when Type of Victim (25) is Individual ("I") or Law Enforcement Officer ("L"). Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered. Error ) When Relationship of Victim to Offender (35) contains a relationship of Spouse ("SE"), then the Victim CANNOT BE LESS THAN 10 YEARS OLD. Error ) Exact Age A... MUST be a valid code if alpha characters, i.e., NN, NB, or BB. Error or B... A single two-character age MUST be in first two positions of the field. The third position MUST be blank. Error ) Estimated Age A... MUST be 2 numeric digits, and have a trailing "E". Error or B... Age CANNOT be an estimate if Date of Birth of Victim (L26) is entered, and Incident Date/Hour (3) is an actual Incident Date (that is, not a Report date ("R")). Error or C... The estimated age CANNOT be Unknown ( 00 ) and have a trailing "E". Error ) Statutory Rape Victim s Age (26) must be 12 years to 16 years. Error Notes: 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"). September, 2016 LIBRS Specifications, Rel

113 Allowed Entries: Enter only one (1) code for each Victim Segment: NN Under 24 Hours (neonate) NB 1-6 Days Old (new born) BB Days Old (baby) 01 to 98 Years Old (age in years) 99 Over 98 Years Old 00 Unknown (CANNOT have "E" with this data value) Age of Victim (26) [At Time Incident Occurred] Example: (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. September 2016 LIBRS Specifications, Rel

114 Date of Birth of Victim (L26) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) Each component of the date MUST be valid (that is, months must be 01-12, days must be 01-31, and year must include the century (e.g., 19xx, 20xx)). In addition, days CANNOT exceed maximum for the month (e.g., June CANNOT have 31 days). The date CANNOT be greater than that entered within the Month of Data Submission and Year of Data Submission field on the data record. For example, if Month of Data Submission and Year of Data Submission are "06/2014, the Date of Birth of Victim (L26) CANNOT contain any date 07/01/2014 or greater. Error ) MUST be on or before Incident Date/Hour (3). Error ) If entered, and Incident Date/Hour (3) contains the actual incident date, then Age of Victim (26) at the time of the incident MUST be an exact age. Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered. Error Note: 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). September, 2016 LIBRS Specifications, Rel

115 Sex of Victim (27) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) MUST be present if Type of Victim (25) is Individual ("I") or Law Enforcement Officer ("L"). Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered in Sex of Victim (27). Error ) Sex of Victim (27) MUST be Male ("M") or Female ("F") to be Connected to Offense codes of Forcible Rape ("11A") and Statutory Rape ("36B"). Error Note: 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 one (1) code for each Victim Segment: Sex of Victim M Male F Female U Unknown September 2016 LIBRS Specifications, Rel

116 Race of Victim (28) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. (Error 15004) 2) MUST be present if Type of Victim (25) is Individual ("I") or Law Enforcement Officer ("L"). Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered. Error Note: 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 one (1) code for each Victim Segment: *** Row Shaded Brown is new Race of Victim, beginning with LIBRS 2.2. *** Race of Victim W White B Black I American Indian / Alaskan Native A Asian / Pacific Islander P Native Hawaiian or Other Pacific Islander U Unknown September, 2016 LIBRS Specifications, Rel

117 Ethnicity of Victim (29) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") in order for data to be entered into Ethnicity of Victim (29). Error Note: 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 one code for each Victim Segment: Ethnicity of Victim H Hispanic Origin N Not of Hispanic Origin U Unknown September 2016 LIBRS Specifications, Rel

118 Resident Status of Victim (30) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered. Error Notes 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 one code for each Victim Segment: Resident Status of Victim R Resident N Nonresident U Unknown September, 2016 LIBRS Specifications, Rel

119 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Assignment (31) Data Characteristics: 2 Character Numeric Requirements: 1) MUST be a valid code. Error ) When more than one code is entered within Aggravated Assault/ Murder category, there can be NO duplicates. Error ) MUST be entered if Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: 13A 09A, 09B or 09C and Louisiana Revised Statute (6) is one of the following: 14: : : : :32 14:32.1/AA... 14: : : : : :35.3/M... 14: : : : : : : : : : :87.2/F... 14:87.2/L... 14:87.5/F 14:87.5/L... 14:93/F... 14: :94/E... 14:107.1/F 14: :108/B1BF.. 14:122/F... 14:129/A2F... 14:129.1/F 14:130.1/F... 14:133.1/F... 14:404/Q... 14:501 and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above offenses. Error ) Unknown Circumstances ("10") is MUTUALLY EXCLUSIVE with all other codes, that is, no other code can be entered. Enter Unknown ("10") ONLY if no other code applies. Error ) NO MORE THAN one circumstance category (that is, Aggravated..., Negligent..., Justifiable...) can be entered. Error ) When Assault/Homicide Circumstances (31) is Other Felony Involved ("08"), then the incident MUST have two or more Offenses. Error September 2016 LIBRS Specifications, Rel

120 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) 7) Aggravated Assault CANNOT use Mercy Killing ("07"), as this code does not relate to Aggravated Assault. Error Notes: Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In Line of Duty (31)) describes the circumstances of either an Aggravated Assault, Homicide or an Assault or Homicide against a Law Enforcement Officer in the line of duty. Example: Two rival juvenile street gangs rumble over "turf" rights to sell drugs and one of the gang members is killed. Possible entries are Argument ("01"), Drug Dealing ("03"), and Juvenile Gang ("05"). 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." Aggravated Assault, Murder and Non-Negligent Manslaughter Circumstances 8) Enter up to two codes for the Aggravated Assault, Murder and Non-Negligent Manslaughter Circumstances when Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09A or 13A, and the Louisiana Revised Statute (6) is one of the following: 14: : : :32.1/AA... 14:34 14: : : : :35.3/M 14: : : : : : : : : : :87.2/F... 14:87.2/L... 14:87.5/F... 14:87.5/L... 14:93/F 14: :94/E... 14:107.1/F... 14:108/B1BF.. 14: :122/F... 14:129/A2F... 14:129.1/F... 14:130.1/F... 14:133.1/F 14:404/Q Error Allowed Entries for Aggravated Assault and Non-Negligent Manslaughter Circumstances: Aggravated Assault and Non-Negligent Manslaughter Circumstances 01 Argument 03 Drug Dealing 04 Gangland 05 Juvenile Gang 06 Lovers Quarrel 07 Mercy Killing (Not applicable to Aggravated Assault) 08 Other Felony Involved 09 Other Circumstances 10 Unknown Circumstances 40 Child Abuse (LIBRS only, reported to NIBRS as Other Circumstances ("09")) September, 2016 LIBRS Specifications, Rel

121 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) Negligent Manslaughter Circumstances: 9) Enter only one code for Negligent Manslaughter Circumstances (31) when Louisiana Revised Statue (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09B, and Louisiana Revised Statute (6) is one of the following: 14: :501 Error Allowed Entries for Negligent Manslaughter Circumstances Negligent Manslaughter Circumstances 30 Child Playing with Weapon 31 Gun Cleaning Accident 32 Hunting Accident 33 Other Negligent Weapon Handling 34 Other Negligent Killings 40 Child Abuse (LIBRS only, reported to NIBRS as Negligent Killings ("34")) 9a) If Non-Negligent Circumstances (31) is Child Abuse ("40"), then the Victim that is Connected to this Offense MUST HAVE AN AGE THAT EQUALS NN NB BB , with a trailing E. Error Justifiable Homicide Circumstances 10) Enter only one code for Justifiable Homicide Circumstances when Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09C, and Louisiana Revised Statute (6) is 14:20 Error Allowed Entries for Justifiable Homicide Circumstances: Justifiable Homicide Circumstances 20 Criminal Killed by Private Citizen 21 Criminal Killed by Police Officer September 2016 LIBRS Specifications, Rel

122 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) 11) When Criminal Killed by Private Citizen ("20") or Criminal Killed by Police Officer ("21") is entered, then Additional Justifiable Homicide Circumstances (32) MUST be entered. Error 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. 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. 12) When Justifiable Homicide (NIBRS Code 09C) is reported, NO OTHER OFFENSE may be reported in the Incident Report. Error Law Enforcement Officer Assault Circumstances 13) For assaults on a Law Enforcement Officers(s), the Louisiana Revised Statute (6) MUST be one of the following Louisiana Revised Statutes: 14: : : : : : : : : : : : : : : :94/E... 14:108/B1BF.. 14:108/B1B... 14:122/F... 14: :129.1/F... 14:130.1/A... 14:130.1/F... 14:133.1/F and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above Offenses. Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 13A and Type of Victim (25) is Law Enforcement Officer ( L ), then the data element (31) MUST HAVE THREE VALID CODES: The first code, Assault on Law Enforcement Officer ("02"), MUST ALSO have a second valid code from the following list: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Mercy Killing (Not applicable to Aggravated Assault) Other Felony Involved Other Circumstances Unknown Circumstances September, 2016 LIBRS Specifications, Rel

123 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) to describe the circumstances of the Aggravated Assault. MUST ALSO have a third valid code from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush - No Warning S... Mentally Deranged T... Traffic Pursuits and Stops U... All Other (LIBRS Only) Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 13B and Type of Victim (25) is Law Enforcement Officer ( L ), then Data Element 31 MUST HAVE THREE VALID CODES. The first code MUST be Assault on Law Enforcement Officer ("02"), followed by a second valid code from the following list: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Other Felony Involved Other Circumstances 10 Unknown Circumstances to describe the circumstances of the Simple Assault. MUST ALSO have a third valid code from the following list: Two-Officer Vehicle One-Officer Vehicle September 2016 LIBRS Specifications, Rel

124 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning S... Mentally Deranged T... Traffic Pursuits and Stops U... All Other (LIBRS Only) Error Allowed Entries for Law Enforcement Officer Assault Circumstances: MUST Enter "02" If Type of Victim (25) is Law Enforcement Officer ("L") and another code of from the following list: Law Enforcement Officer Assault Circumstances 01 Argument 02 Assault on Law Enforcement Officer(s) 03 Drug Dealing 04 Gangland 05 Juvenile Gang 06 Lovers Quarrel 07 Mercy Killing (Not applicable to Aggravated Assault) 08 Other Felony Involved 09 Other Circumstances 10 Unknown Circumstances Note: For the third valid code, see the following section of Allowed Entries Under Law Enforcement Officer(s) Killed/Assaulted (in the Line of Duty) Type of Assignment Circumstances (32). September, 2016 LIBRS Specifications, Rel

125 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) Law Enforcement Officer Murder or Non-Negligent Manslaughter Circumstances 16) For murder or non-negligent manslaughter of a Law Enforcement Officer(s) Killed (in the Line of Duty), one of the following Louisiana Revised Statutes (6) MUST be used:: 14: : : :32.1/AA... 14: :87.2/L... 14:87.5/L and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above offenses. Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09A and Type of Victim (25) is Law Enforcement Officer ("L"), then Data Element 31 MUST HAVE THREE VALID CODES. The first code MUST be Assault on Law Enforcement Officer ("02"), followed by a second valid code from the following list: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Other Felony Involved Other Circumstances 10 Unknown Circumstances to describe the circumstances of the Murder and Non-Negligent Manslaughter. MUST ALSO have a third valid code from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning September 2016 LIBRS Specifications, Rel

126 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) U... All Other (LIBRS Only) Error Allowed Entries for Law Enforcement Officer Murder and Non-Negligent Manslaughter Circumstances: Enter up to two codes: Law Enforcement Officer Murder and Non-Negligent Manslaughter Circumstances 01 Argument 03 Drug Dealing 04 Gangland 05 Juvenile Gang 06 Lovers Quarrel 07 Mercy Killing (Not applicable to Aggravated Assault) 08 Other Felony Involved 09 Other Circumstances 10 Unknown Circumstances Note: For the third valid code, see the following section of Allowed Entries Under Law Enforcement Officer(s) Killed/Assaulted (in the Line of Duty) Type of Assignment Circumstances (32). Law Enforcement Officer Negligent Manslaughter Circumstances 18) For a Negligent Manslaughter of a Law Enforcement Officer(s) Killed (in the Line of Duty), the Louisiana Revised Statute (6) MUST be one of the following: 14: :501 and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above offenses. 19) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09B and Type of Victim (25) is Law Enforcement Officer ("L"), then Data Element 31 MUST HAVE TWO VALID CODES. The first code MUST be from the following list: Child Playing with Weapon Gun Cleaning Accident Hunting Accident Other Negligent Weapon Handling Other Negligent Killings to describe the circumstances of the Negligent Manslaughter, September, 2016 LIBRS Specifications, Rel

127 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) The second valid code MUST come from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning U... All Other Error Allowed Entries for Law Enforcement Officer Negligent Manslaughter Circumstances Enter only one (1) code Law Enforcement Officer Negligent Manslaughter Circumstances 30 Child Playing with Weapon 31 Gun-Cleaning Accident 32 Hunting Accident 33 Other Negligent Weapon Handling 34 Other Negligent Killings Note: For the third valid code, see the following section of Allowed Entries Under Law Enforcement Officer(s) Killed/Assaulted (in the Line of Duty) Type of Assignment Circumstances (32). LEOKA in the Line of Duty, Type of Assignment: 20) Enter only one code from the allowed entries shown, below, along with the valid codes from the Law Enforcement Officer(s) Killed or Assaulted (in the Line of Duty) Circumstances (31) allowed entries. Louisiana Revised Statute (6) MUST be in Requirement 13, 16, and 18. September 2016 LIBRS Specifications, Rel

128 Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (In the Line of Duty) Type of Assignment (31) Allowed Entries for Law Enforcement Officer Assault, Murder and Non-Negligent Manslaughter, and Negligent Manslaughter (in the Line of Duty) Type of Assignment Circumstances: Law Enforcement Officer Assault, Murder and Non-Negligent Manslaughter, and Negligent Manslaughter (in the Line of Duty) Type of Assignment Circumstances 12 Two-Officer Vehicle 13 One-Officer Vehicle 14 One-Officer Vehicle Assisted 15 Detective or Special Assignment Alone 16 Detective or Special Assignment Assisted 17 Other Alone 18 Other Assisted Enter only one code. (LIBRS Only) Note: Type of Victim (25) MUST be Law Enforcement Officer ("L") and Louisiana Revised Statute (6) MUST be an 09A, 09B, 13A or 13B, and listed in Requirement 13, 16 or 18 of Data Element 31. (LIBRS Only) September, 2016 LIBRS Specifications, Rel

129 Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) 2) When this Data Element (32) is entered, then Aggravated Assault/Homicide Circumstances/Law Enforcement Officer Killed/Assaulted (in the Line of Duty) Type of Assignment Circumstances (31) MUST show one of the following Justifiable Homicide (NIBRS 09C) Circumstances: 20 Criminal Killed by Private Citizen Criminal Killed by Police Officer if Type of Victim (25) is not equal to Law Enforcement Officer ( L ). Error Note: This Data Element (32) further describes the Circumstances of a Justifiable Homicide and further describes the Circumstances of a Homicide or Assault Against a Law Enforcement Officer by indicating the Type of Activity for LEOKA reporting. Allowed Entries for Justifiable Homicide: Enter only one code for Justifiable Homicide (NIBRS 09C): Justifiable Homicide 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 Example of Justifiable Homicide: 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: (cont d on next page) A B Criminal Attacked Police Officer and That Officer Killed Criminal Criminal Attacked Police Officer and Criminal Killed by Another Police Officer September 2016 LIBRS Specifications, Rel

130 Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) 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"). Allowed Entries for Law Enforcement Officer Killed or Assaulted (in the Line of Duty) Type of Activity Enter only one code for Law Enforcement Officers Killed or Assaulted (in the Line of Duty) Type of Activity (32), when Type of Victim (25) is Law Enforcement Officer ("L"): (LIBRS Only) Law Enforcement Officer Killed or Assaulted (in the Line of Duty) Type of Activity K Responding to "Disturbance" calls (family quarrels, man with gun, etc.) L Burglaries in progress or pursuing burglary suspects M Robberies in progress or pursuing robbery suspects N Attempting other arrests O Civil Disorder (riot, mass disobedience) P Handling, transporting, custody of prisoners Q Investigating suspicious persons or circumstances R Ambush - no warning S Mentally deranged T Traffic pursuits and stops U All Other 3) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on the Master LIBRS/LRS Code Table] of 09A and Type of Victim (25) is Law Enforcement Officer ("L"), then Data Element 31 must have AT LEAST TWO valid codes (can enter up to two codes, but CANNOT be duplicates): The first valid code can be from the following list in Data Element 31: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Other Felony Involved Other Circumstances 10 Unknown Circumstances to describe the circumstances of the Murder and Non-Negligent Manslaughter. MUST ALSO have a second valid Data Element 31 code from the following list: Two-Officer Vehicle One-Officer Vehicle September, 2016 LIBRS Specifications, Rel

131 Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning S... Mentally Deranged T... Traffic Pursuits and Stops U... All Other (LIBRS Only) Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 09B and Type of Victim (25) is Law Enforcement Officer ("L"), then Data Element 31 MUST HAVE TWO VALID CODES. The first code MUST be from the following list: Child Playing with Weapon Gun Cleaning Accident Hunting Accident Other Negligent Weapon Handling Other Negligent Killings to describe the circumstances of the Negligent Manslaughter, The second valid code MUST come from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects September 2016 LIBRS Specifications, Rel

132 Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning U... All Other (LIBRS Only) Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 13A and Type of Victim (25) is Law Enforcement Officer ( L ), then the data element (31) MUST HAVE THREE VALID CODES: The first code, Assault on Law Enforcement Officer ("02"), MUST ALSO have a second valid code from the following list: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Mercy Killing (Not applicable to Aggravated Assault) Other Felony Involved Other Circumstances Unknown Circumstances to describe the circumstances of the Aggravated Assault. MUST ALSO have a third valid code from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances September, 2016 LIBRS Specifications, Rel

133 Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) R... Ambush - No Warning S... Mentally Deranged T... Traffic Pursuits and Stops U... All Other (LIBRS Only) Error ) When Louisiana Revised Statute (6) has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of 13B and Type of Victim (25) is Law Enforcement Officer ( L ), then Data Element 31 MUST HAVE THREE VALID CODES. The first code MUST be Assault on Law Enforcement Officer ("02"), followed by a second valid code from the following list: Argument Drug Dealing Gangland Juvenile Gang Lovers Quarrel Other Felony Involved Other Circumstances 10 Unknown Circumstances to describe the circumstances of the Simple Assault. MUST ALSO have a third valid code from the following list: Two-Officer Vehicle One-Officer Vehicle One-Officer Vehicle Assisted Detective or Special Assignment Alone Detective or Special Assignment Assisted Other Alone Other Assisted and one valid Additional Law Enforcement Officers Killed/Assaulted in the Line of Duty (32) from the following list (LIBRS ONLY): K... Responding to Disturbance calls (Family Quarrels, Man with Gun) L... Burglaries in Progress or Pursuing Burglary Suspects M... Robberies in Progress or Pursuing Robbery Suspects N... Attempting Other Arrests O... Civil Disorder (Riot, Mass Disobedience) P... Handling, Transporting, Custody of Prisoners Q... Investigating Suspicious Persons or Circumstances R... Ambush, with No Warning S... Mentally Deranged T... Traffic Pursuits and Stops U... All Other (LIBRS Only) Error September 2016 LIBRS Specifications, Rel

134 Additional Justifiable Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (in the Line of Duty) Type of Activity (32) Example of Assault on a Law Enforcement Officer: Officer stopped vehicle on the interstate because the operator of the vehicle was speeding, not maintaining control of the vehicle, and had an invalid license plate. When stopped, the offender got out of the car and hit the officer with a club, grabbed a suitcase out of the vehicle and ran away. Assuming the facts above, the entries for Data Element 31 are: 02 = Assault on Law Enforcement Officer 13 = One Officer Vehicle The possible entries for Data Element 32 are: Q = Investigating suspicious persons or circumstance, and T = Traffic Pursuits and Stops As only ONE code can be entered into Data Element 32, the most descriptive code (as determined by the reporting agency) should be used. In this case, the reporting agency entered Traffic Pursuits and Stops ("T"). September, 2016 LIBRS Specifications, Rel

135 Type of Injury (33) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) If more than one code entered, CANNOT be a duplicate. Error ) None ("N") is MUTUALLY EXCLUSIVE with any other value entered. That is, None "N" is to be used only if no other code applies. Error ) MUST be entered if Louisiana Revised Statute (6) is a Crime Against Person and has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: A... 11B... 11C... 11D A... 13B Z and the Louisiana Revised Statute is one of the following: 4: : : : : : : : : : : : : : : :35.3/M... 14: : : : : : : : : : : : :42/A...14:42/V 14:42.1/A... 14:42.1/V... 14:43/A... 14:43/V...14:43.1/N 14:43.1/P... 14:43.2/N... 14:43.2/P... 14: : : : : : :44.1/A 14:44.1/N... 14:44.1/O... 14:44.1/P... 14:44.1/V...14: : : : : : : : : : :81 14: : : :87.2/F...14:87.5/F 14: : :93/F... 14: : : :94/E... 14: :103/A1...14:107.1/F 14:108/B1BF... 14:108/B1B... 14: :122/F...14:129/A2F 14: :129.1/F... 14:130.1/A... 14:130.1/F...14:133.1/F 14: : :404/J... 14:404/Q...32:668 and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above offenses. Error ) When Offense Connected to Victim Sequence Number (24) relates to the Offense of Simple Assault (NIBRS "13B"), there CANNOT be major injury codes which would indicate an Aggravated Assault. Permissible codes are Apparent Minor Injury ("M") and None ("N"). Error September 2016 LIBRS Specifications, Rel

136 Type of Injury (33) 6) For Human Trafficking Offenses (NIBRS Codes 64A, 64B and 40C), a data value for Type of Injury (33) MUST be specified. ***New in LIBRS 2.2 *** Notes: This Data Element (33) 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 one 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 (includes Nose) I Possible Internal Injury L Severe Laceration M Apparent Minor Injury O Other Major Injury T Loss of Teeth U Unconsciousness September, 2016 LIBRS Specifications, Rel

137 Offender Number to be Related (34) Data Characteristics: 3 Character Numeric Requirements: 1) MUST be entered if Louisiana Revised Statute (6) is a Crime Against Person, and has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: 09A... 09B... 09C A... 11B... 11C... 1D A... 13B... 13C 36A... 36B 90Z and has a Louisiana Revised Statute (6) that is one of the following: 4: : : : : : : : : : : : : : : :35.3/M... 14: : : : : : : : : : : : :42/A...14:42/V 14:42.1/A... 14:42.1/V... 14:43/A... 14:43/V...14:43.1/N 14:43.1/P... 14:43.2/N... 14:43.2/P... 14: : : : : : :44.1/A 14:44.1/N... 14:44.1/O... 14:44.1/P... 14:44.1/V...14: : : : : : : : : : :81 14: : : :87.2/F...14:87.5/F 14: : :93/F... 14: : : :94/E... 14: :103/A1...14:107.1/F 14:108/B1BF... 14:108/B1B... 14: :122/F...14:129/A2F 14: :129.1/F... 14:130.1/A... 14:130.1/F...14:133.1/F 14: : :404/J... 14:404/Q...32:668 and Offense Connected to Victim Sequence Number (24) MUST relate to one of the above offenses. Error ) MUST be numeric entry with ZERO LEFT-FILL, if entered. Error ) Type of Victim (25) MUST be Individual ("I") or Law Enforcement Officer ("L") for data to be entered. Error ) If more than one number entered, then this Data Element (34) CANNOT BE A DUPLICATE. Error September 2016 LIBRS Specifications, Rel

138 Offender Number to be Related (34) 5) "000" may only be entered when there is ONLY ONE Offender Segment (40) submitted and nothing was known about identity and number of offender(s). Error ) A corresponding Offender Segment (40) MUST BE PRESENT. Error ) When a Victim is connected to a Crime Against Person or Robbery Offense, all Offender Sequence Numbers (36), MUST also be entered in Offender Number to be Related (34). If the Victim is related to the Offender in more than one way, use the closest relationship. Error ) 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. ***New in LIBRS 2.2 *** 9) 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). ***New in LIBRS 2.2 *** Notes: Offender Number to be Related (34), along with Relationship of Victim to Offender (35), describes 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. Example: If Victim 001's relationship to Offender 004 is to be reported, enter "004". September, 2016 LIBRS Specifications, Rel

139 Data Characteristics: 2 Character Alpha Relationship of Victim to Offender (35) Requirements: 1) Every Offender indicated in Offender Number to be Related (34) requires an entry in Relationship of Victim to Offender (35), except when the Offender Sequence Number (36) is Unknown ("000"). This field MUST be Blank (G) in instances where "000" is entered. Error ) MUST be a valid code. Error ) Husbands and wives (that is, spouses) must be at least 10 years of age. Error 15050, ) The Sex of Victim (27) and Sex of Offender (38) MUST reflect the implied relationship. The following relationships must reflect a specific sex for the Victim, Offender or both depending upon the relationship: Error Relationship Sex Codes XS Victim was Ex-Spouse Different SE Victim was Spouse Different CS Victim was Common-Law Spouse Different ES Victim was Estranged Spouse Different HR Homosexual Same VO Victim was Offender Same BG Victim was Boyfriend/Girlfriend Different XB Victim was Ex-Boyfriend/Girlfriend Different NM Non-Married Live-In Different Error ) The Age of Victim and Age of Offender MUST reflect the implied relationship. Relationship Victim MUST Be CH Victim was Child Younger PA Victim was Parent Older GP Victim was Grandparent Older GC Victim was Grandchild Younger VO Victim was Offender Same Age BE Victim was Babysitee (the Baby) Younger SE Victim was Spouse At Least 10 years ES Victim was Estranged Spouse At Least 10 years. CS Victim was Common-Law Spouse At Least 10 years. XS Victim was Ex-Spouse At Least 10 years NM Victim was Non-Married Live-In At Least 10 years. Error September 2016 LIBRS Specifications, Rel

140 Relationship of Victim to Offender (35) 6) Relationship CANNOT be entered when Offender Number to be Related (34) is Unknown ("000"). Error ) When Victim was Offender ("VO") is entered, a minimum of two Victims Segments (50) and two Offender Segments (40) MUST be submitted. "VO" indicates situations such as brawls and domestic disputes where all of the participants in the incident were Victims and Offenders of the same Offense (for example, assaults or double murders where two people kill each other). In most cases, each Victim is also the Offender; therefore, every Victim Segment (50) will contain a "VO" code. However, there may be some situations where only one of the Victims is also the Offender, but where the other Victim(s) are not also the Offender(s) (for example, a Victim who is not an Offender could be an innocent bystander in a barroom brawl, or a child who is victimized as a result of the parents domestic dispute). Error ) When entered, Victim was Offender ("VO") CAN ONLY BE ENTERED ONCE in a Victim Segment (50) and can refer to an Offender ONLY ONCE. Since "VO" points to himself/herself, a Victim CANNOT at the same time be two Offenders. Error 15071, ) When the related Offender has "Unknown" values entered for Age, Sex and Race, the relationship must be Relationship Unknown ("RU"). This edit ensures a logical relationship. For example, if Brother ( SB ) was entered fro Relationship of Victim to Offender (25), then Age, Sex and Race would NOT be Unknown values. Error ) In a multiple Offender incident, a Victim CANNOT have a relationship of Spouse ("SE") to MORE THAN ONE Offender. Error ) In a multiple Victim incident, two or more Victims CANNOT have a Victim relationship of Spouse ("SE") to the same Offender. Error ) MUST be entered if Louisiana Revised Statute (6) is a Crime Against Person, and has a NIBRS Offense code [as defined on Master LIBRS/LRS Code Table] of: 09A... 09B... 09C A... 11B... 11C... 11D A... 13B... 13C 36A... 36B 90Z and Louisiana Revised Statute (6) is one of the following: 14: : : :31 14: :32.1/AA... 14: : : : : : : : : : : : :35.2 September, 2016 LIBRS Specifications, Rel

141 Relationship of Victim to Offender (35) 14: :35.3/M... 14: : : : : : : : : : : : : : : : : : : : : :42/A...14:42/V 14:42.1/A... 14:42.1/V... 14:43/A... 14:43/V...14:43.1/N 14:43.1/P... 14:43.2/N... 14:43.2/P... 14: : : : : : :44.1/A 14:44.1/N... 14:44.1/O... 14:44.1/P... 14:44.1/V...14: : : : : : : : : : : : : : : : : : : : : :87.2/F... 14:87.2/L... 14:87.5/F... 14:87.5/L...14: : : :93/F... 14: : : :94/E... 14: :103/A1...14:107.1/F 14:108/B1BF... 14:108/B1B... 14: :122/F...14:122/T 14: : :129/A :129/A2F...14:129/A2T 14: :129.1/F... 14:129.1/T... 14:130.1/A...14:130.1/T 14:130.1/F... 14:133.1/F... 14:133.1/T... 14: :285 14: :404/J... 14:404/Q... 14: :668 Relationship of Victim to Offender (35) MUST be Blank (G) when "000" is entered into Offender Number to be Related (34). Error ) 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. ***New in LIBRS 2.2 *** Notes: 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"). September 2016 LIBRS Specifications, Rel

142 Relationship of Victim to Offender (35) 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: Relationship of Victim to Offender Within Family SE Victim was Spouse CS Victim was Common-Law Spouse PA Victim was Parent SB Victim was Sibling (brother or sister) 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 (step-grandparents, ex-common law spouses. etc.) NM Victim was Non-Married Live-In (to NIBRS as CS) Outside Family, But Known to Victim 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/Ex-Girlfriend (to NIBRS as BG) CF Victim was Child of Boyfriend or Girlfriend HR Victim was in Homosexual Relationship XS Victim was Ex-Spouse EE Victim was Employee ER Victim was Employer OK Victim was Otherwise Known ES Victim was Estranged Spouse (to NIBRS as SE) Not Know By Victim RU Relationship Unknown ST Victim was Stranger Other VO Victim was Offender Examples: (1) An employee assaulted his employer (a person) with his fists. Victim was Employer (ER) should be entered. (2) 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 Offender. September, 2016 LIBRS Specifications, Rel

143 Data Characteristics: 3 Character Numeric Offender Sequence Number (36) Requirements: 1) MUST be present -- CANNOT BE BLANK. Error ) MUST be numeric entry with ZERO LEFT-FILL. Offender Sequence Number (36) distinguishes one Offender from another and identifies a situation where nothing was known about the number of Offenders, or who they were. For example, a corpse was found in a ditch and there were no eyewitnesses or other information that could provide data about possible Offenders. In this case, Unknown ("000") would be entered. However, if five Offenders were seen running from the scene, then five Offender records would be submitted, each with a difference Offender Sequence Number (36). Error ) If an incident is Exceptionally Cleared (4), then Unknown ("000") CANNOT be entered. Unknown ("000") indicates that nothing is known about the Offender(s) regarding number and any identifying information. One of the criteria for Exceptionally Clearing (4) an incident is that at least one of the Offenders be known. Error ) For a Justifiable Homicide (NIBRS 09C), AT LEAST ONE of the Offenders must have "known" information for Age, Sex, and Race. Consequently, Unknown ("000") is not valid as an Offender Sequence Number (36). Error ) If the number is Unknown ("000"), no other Offender Segments (40) can be submitted. Error ) MUST be UNIQUE - CANNOT BE DUPLICATED. Error ) When Offender Sequence Number (36) is Unknown ("000"), Offender Suspected of Using/Gaming Motivation (8) must be Not Applicable ("N ) and Bias Motivation/Bias Crime Type (8A) must be None ("88"). Error 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: (1) 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 37 through 39. Also, Offender Suspected of Using (8) must be Not Applicable ("N") and Bias Motivation/Bias Crime Type (8A) must be None "88". (2) 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". Applicable Unknown codes should be entered into Data Elements 37, 38, and 39. Also, Offender Suspected of September 2016 LIBRS Specifications, Rel

144 Offender Sequence Number (36) Using (8) MUST be Not Applicable ("N")and Bias Motivation/Bias Crime Type (8A) MUST be None ("88"). September, 2016 LIBRS Specifications, Rel

145 Age of Offender (37) [At Time of Incident] Data Characteristics: 3 Character Alpha Requirements: 1) MUST be present when Offender Sequence Number (36) is other than Unknown ("000"). Error ) CANNOT be entered when Offender Sequence Number (36) is Unknown ("000"). Error ) When an incident is Cleared Exceptionally (4), AT LEAST ONE of the Offenders MUST have known values in Age, Sex, and Race. Error ) For a Justifiable Homicide (NIBRS 09C) AT LEAST ONE of the Offenders MUST have known information for Age, Sex, and Race. Error ) If Relationship of Victim to Offender (35) contains a relationship of Spouse ("SE"), then the Offender CANNOT be less than 10 years old. Error ) Exact Age: A... MUST contain numeric entry of Error B... A single, two-character Age MUST be in first two positions of the field. The third position must be Blank (G). Error ) Estimated Age: A... MUST be 2 numeric digits, and have a trailing "E". Error B... Age CANNOT be an estimate if Date of Birth of Offender (L37) is entered, and Incident Date/Hour (3) is an actual Incident Date (that is, not a Report Date ("R")). Error C... The estimated Age CANNOT be Unknown ("00") and have a trailing "E". Error Note: Age of the Offender (37) is entered either as an exact number of years, an estimated age, or as unknown. Allowed Entries: Enter only one code per Offender Segment(40): Age of Offender (at Time of Incident) 01 to 98 Years Old (age in years) 99 Over 98 Years Old 00 Unknown (CANNOT have "E" with this data value) September 2016 LIBRS Specifications, Rel

146 Age of Offender (37) [At Time of Incident] 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"). Example: 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 estimated age of 27). September, 2016 LIBRS Specifications, Rel

147 Date of Birth of Offender (L37) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) Each component of the date must be valid; that is, months must be 01-12, days must be 01-31, and year must include the century (i.e., 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (for example, June CANNOT have 31 days). The data CANNOT be greater than that entered within the "Month of Data Submission" and "Year of Data Submission" fields on the data record. For example, if "Month of Data Submission" and "Year of Data Submission" are "06/2014," the Date of Birth CANNOT contain any date 07/01/2014 or greater. Error ) Date of Birth of Offender (L37) MUST be before Incident Date/Hour (3). Error ) If entered, and Incident Date/Hour (3) contains the actual Incident Date, then Age of Offender (at Time of Incident) (37) must be an exact age. Error Note: If the Date of Birth of the Offender is known, it is to be indicated in this data element. September 2016 LIBRS Specifications, Rel

148 Sex of Offender (38) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present when Offender Sequence Number (36) is other than Unknown ("000"). Error ) MUST be a valid code. Error ) CANNOT be entered when Offender Sequence Number (36) is Unknown ("000"). Error ) When an incident is Cleared Exceptionally (4), AT LEAST ONE of the Offenders MUST have known values in Age, Sex and Race. Error ) For a Justifiable Homicide (NIBRS 09C) AT LEAST ONE of the Offenders MUST have known information for Age, Sex and Race. Error ) For Forcible Rape (NIBRS 11A) or Statutory Rape (NIBRS36B), one or more of the Offenders MUST HAVE A DIFFERENT SEX than the rape Victim. Error Note: This Data Element (38) indicates Sex of the Offender. Allowed Entries: Enter only one code per Offender Segment (40): Sex of Offender M Male F Female U Unknown Example: 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"). September, 2016 LIBRS Specifications, Rel

149 Race of Offender (39) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present when Offender Sequence Number (36) is other than Unknown ("000"). Error ) MUST be a valid code. Error ) CANNOT be entered when Offender Sequence Number (36) is Unknown ("000"). Error ) When an incident is Cleared Exceptionally (4), AT LEAST ONE of the Offenders MUST have known values in Age, Sex and Race. Error ) For a Justifiable Homicide (NIBRS 09C) AT LEAST ONE of the Offenders MUST have known information for Age, Sex and Race. Error Note: Race of an Offender is indicated in this Data Element (39). Allowed Entries: Enter only one code per Offender Segment (40): Race of Offender W White B Black I American Indian/Alaskan Native A Asian/Pacific Islander U Unknown September 2016 LIBRS Specifications, Rel

150 Arrestee Sequence Number (40) Data Characteristics: 3 Character Numeric Requirements: 1) MUST be present--cannot be Blank (G). Error ) MUST be numeric entry of 001 to 999 with ZERO LEFT-FILL. Error ) MUST be unique -- CANNOT be duplicated. Error ) Number of Arrestees (40) CANNOT be greater than number of Offenders. Error Note: Each Arrestee reported is assigned a UNIQUE Sequence Number from "001" to "999". Example: If two persons were arrested in connection with a previously submitted incident, two Arrestee Segments should be submitted: one with Arrestee Sequence Number "001" and the other with "002". September, 2016 LIBRS Specifications, Rel

151 Arrestee Name (L40) 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 Note: 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. September 2016 LIBRS Specifications, Rel

152 Arrest Number/Local Booking Number for Arrest (41) Data Characteristics: 12 Character Alpha Requirements: 1) MUST be present--cannot be Blank (G). Error ) MUST be left-justified with blank right-fill if under 12 characters in length. Error ) Valid character combinations can include A-Z, 0-9, and hyphens. For example, SC is valid, but *SC or SC is invalid. Error ) MUST be blank right-fill if under 12 characters in length. CANNOT have embedded Blanks (G) between the first and last character entered. Error Note: 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. September, 2016 LIBRS Specifications, Rel

153 Arrest Date (42) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) MUST be present--cannot be Blank (G). Error ) Each component of Arrest Date (42) MUST be valid; that is, months must be 01-12, days must be 01-31, and year must include the century (that is, 19xx, 20xx). In addition, days CANNOT exceed maximum for the month (for example, June CANNOT have 31 days). Arrest Date (42) CANNOT EXCEED THE CURRENT DATE. Arrest Date CANNOT be greater than that entered with the "Month of Data Submission" and "Year of Data Submission" fields on the data record. For example, if "Month of Data Submission" and "Year of Data Submission" are "06/2014", the Arrest Date (42) CANNOT contain any date 07/01/2014 or greater. Error ) CANNOT be earlier than Incident Date/Hour (3). Error ) Arrestee Segments (60) submitted as Time-Window Submission (Action Type of Time Window ( W )) CANNOT have Arrest Date (42) earlier than the Agency s Base Date. This also applies to any subsequent Modify Submission ("M ) of a previously submitted Time-Window Submission ("W"). Error Note: Arrest Date (42) is used to enter the month, day and year when the actual arrest took place. September 2016 LIBRS Specifications, Rel

154 Type of Arrest (43) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present--cannot be Blank (G). Error ) MUST be a valid code. Error Notes: 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) September, 2016 LIBRS Specifications, Rel

155 Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present--cannot be Blank (G). Error 16001) 2) MUST be a valid code. Error 16004) Multiple Arrest Segment Indicator (44) Notes: 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 ). Allowed Entries: Enter only one code per Arrestee Segment: Multiple Arrestee Segment Indicator M Multiple C Count Arrestee N Not Applicable Note: Count Arrestee ( C ) and Multiple ("M") codes are to be used in this Data Element (44) ONLY when the same agency submits two or more Arrestee Segments (for different incidents) relating to the same Arrestee. EXAMPLES: (1) 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. 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 ). September 2016 LIBRS Specifications, Rel

156 Louisiana Revised Statute Number of Arrest (45) Data Characteristics: 12 Character Alpha Format: TT:SSSS.S/P-I Louisiana Revised Statute Format TT Title SSSS.S Section PPP/I Subpart, or Subpart with Qualifier, or 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: 1) MUST be present--cannot be Blank (G). Error ) MUST be a valid code on Master LIBRS/LRS Code Table. This CODE DOES NOT HAVE TO MATCH one of the code(s) entered for Louisiana Revised Statute (6) within Offense Segments (6) submitted in an Incident Report. Error ) The Louisiana Revised Statute (6) CANNOT be Justifiable Homicide (14:20), because this Offense does not result in a subsequent arrest of the Offender. Error ) An incident CANNOT have arrests when Louisiana Revised Statute (6) is Justifiable Homicide (LRS 14:20, or NIBRS 09C). A Justifiable Homicide never involves an arrest of the Offender (the person who committed the Justifiable Homicide). Error September, 2016 LIBRS Specifications, Rel

157 Louisiana Revised Statute of Arrest (45) Notes: 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 spaces14: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. September 2016 LIBRS Specifications, Rel

158 Arrest Connection to Offense (L45) Data Characteristics: 15 Character Alpha Requirements: MUST be a valid Offense Sequence Number (L6). The Offense Segment (20) referred to by this Data Element (L45) MUST exist. Notes: Arrest Connection to Offense (L45) is OPTIONAL at this time. 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. September, 2016 LIBRS Specifications, Rel

159 Arrestee was Armed With [At Time of Arrest] (46) Data Characteristics: 3 Character Alpha Requirements: 1) MUST be present--cannot be blank. Error ) MUST be a valid code. Error ) If more than one code entered, CANNOT be a DUPLICATE. Error ) Unarmed ("01") is MUTUALLY EXCLUSIVE with any other value. That is, it is to be used ONLY when no other code applies. Error Note: If the Arrestee was in possession of a toy or play weapon this would be reported as being Unarmed ("01"). 5) The third character must be either Blank (G) or Automatic ("A"). Error ) If the firearm is Automatic, add Automatic ("A") as the third character of code; valid only with the following codes: Error Firearm (Type Not Stated) 12 Handgun 13 Rifle 14 Shotgun 15 Other Firearm Notes: 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. September 2016 LIBRS Specifications, Rel

160 Arrestee was Armed With [At Time of Arrest] (46) Allowed Entries: Enter as many codes as apply. However, DO NOT enter the same code Arrestee was Armed with (at Time of Arrest) 01 Unarmed (If toy or play weapon, or not commonly known weapon) 11 Firearm (Type Not Stated) 12 Handgun 13 Rifle 14 Shotgun 15 Other Firearm 16 Lethal Cutting Instrument (for example, switchblade knife, martial arts "stars", etc.) 17 Club/Blackjack/Brass Knuckles more than once for the same Arrestee: Example: (1) 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 not generally considered to be a weapon, it does not qualify for reporting to LIBRS. (2) 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 used items as weapons, they were not commonly known weapons. September, 2016 LIBRS Specifications, Rel

161 Age of Arrestee (47) Data Characteristics: 3 Character Alpha Requirements: 1) MUST be present--cannot be blank. (Error 16001) 2) If age is under 17, then Data Element # 52 (disposition of Arrestee Under 17) must be entered. (Error 16052) 3) EXACT AGE: A... MUST contain numeric entry of Error B... A single, two-character Age MUST be in first two positions of the field. The third position must be Blank (G). Error C... When Age is unknown, don't confuse Over 98 Years Old ("99") with Unknown ("00"). Whenever Over 98 Years Old ("99") is entered, a warning message is produced. WARNING )... ESTIMATED AGE: A... MUST be 2 numeric digits, and have a trailing "E". Error B... Age CANNOT be an estimate if Date of Birth of Arrestee (47) is reported. Error C... The estimated Age CANNOT be Unknown ("00") and have a Error trailing "E". 5) When Juvenile Qualifiers are used, Age of Arrestee (47) must be 01" thru 16" for the following Juvenile Qualifiers: JU:RUN JU:UNG JU:CUR JU:TRU Error Runaway Offense (90I) Ungovernable (90C) Curfew (90B) Truancy (90Z). Note: Age of the Arrestee (47) can be entered either as an exact number of years, an estimated age, or as unknown. September 2016 LIBRS Specifications, Rel

162 Age of Arrestee (47) Allowed Entries: Enter only one code per Arrest Segment (60): Age of Arrestee 01 to 98 Years Old (Age in Years) 99 Over 98 Years Old 00 Unknown (CANNOT have "E" with this data value) When Arrestee's Age is not known, estimate the Arrestee's Age and append an "E" (Estimated). Example: 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 and estimated 37 years old ("37E"). Use the latter when possible. September, 2016 LIBRS Specifications, Rel

163 Date of Birth of Arrestee (L47) Data Characteristics: 8 Character Date Format: MMDDYYYY Requirements: 1) Age CANNOT BE ESTIMATED when Date of Birth is Known. If the age is reported as Estimated (with trailing "E") in Age of Arrestee at the Time of Arrest (47), and the agency also reports Date of Birth of Arrestee (L47) this incident will be rejected. When Date of Birth is known, Age CANNOT be estimated. Error ) AGE CANNOT BE UNKNOWN if Date of Birth (L47) is Known. If Age of an Arrestee (at Time of Arrest) is reported as Unknown ("00") and Date of Birth of Arrestee (L47) is also reported, this incident will be rejected. If Date of Birth is Known, Age CANNOT be unknown. Error Note: If Date of Birth of the Arrestee is Known, it should be entered into this Data Element. September 2016 LIBRS Specifications, Rel

164 Sex of Arrestee (48) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be Blank (G). Errors ) MUST be a valid code. Although Unknown ("U") is a valid code for Victim and Offender sex, it is NOT valid for Arrestees. Errors Note: This Data Element (48) indicates the sex of the Arrestee. Allowed Entries: Enter only one code per Arrest Segment: Age of Arrestee M Male F Female September, 2016 LIBRS Specifications, Rel

165 Race of Arrestee (49) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be present -- CANNOT be Blank (G). Errors ) MUST be a valid code. Errors Notes: Race of Arrestee (49) is indicated by this Data Element. Allowed Entries: Enter only one code per Arrest Segment (60): Race of Arrestee W White B Black I American Indian / Alaskan Native A Asian / Pacific Islander U Unknown September 2016 LIBRS Specifications, Rel

166 Ethnicity of Arrestee (50) Data Characteristics: 1 Character Alpha Requirements: If entered, MUST be a valid code. Errors Note: This Data Element indicates the ethnic origin of the Arrestee. Allowed Entries: Enter only one code per Arrest Segment: Ethnicity of Arrestee H Hispanic Origin N Not of Hispanic Origin U Unknown September, 2016 LIBRS Specifications, Rel

167 Resident Status of Arrestee (51) Data Characteristics: 1 Character Alpha Requirements: If entered, MUST be a valid code. Error Notes: 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 one code per Arrest Segment (60): Resident Status of Arrestee R Resident N Nonresident U Unknown September 2016 LIBRS Specifications, Rel

168 Disposition of Arrestee Under 17 (52) Data Characteristics: 1 Character Alpha Requirements: 1) MUST be a valid code. Error ) MUST be entered if Arrestee Age is Under 17. Error ) CANNOT be entered if Arrestee Age is 17 or Over. Error ) Disposition of Arrestee Under 17 (52) MUST be entered, when Age of Arrestee (47) indicated an Age for a Juvenile. Note that when Age is for a juvenile, the Disposition of Arrestee Under 17 (52) MUST be entered. Error Notes: Disposition of Arrestee Under 17 (52) is to be used ONLY if the Arrestee was 16 years of age or younger at the time of arrest. Allowed Entries: Enter only one code per Arrest Segment (60) -- for Juveniles only: Disposition of Arrestee Under 17 Handled Within the Department and Released (e.g., released to parents, released with D warning, etc.) (reported to NIBRS as a H ) J Referred to Juvenile Court or Probation Department (reported to NIBRS as a R ) W Referred to Welfare Agency (reported to NIBRS as a R ) P Referred to Other Police Agency (reported to NIBRS as a R ) A Referred to Criminal or Adult Court (reported to NIBRS as a R ) Example: (1) 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 Department and Released ("D"). (2) 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 Court ("A"). September, 2016 LIBRS Specifications, Rel

169 Location of Incident (L53) [Geographical Coordinates] Data Characteristics: 12 Character Alpha/Numeric Format: DDMMSSDDMMSS First six characters are LONGITUDE in: DD MM SS Degrees Minutes Seconds Second six characters are LATITUDE in: DD MM SS Degrees Minutes Seconds Requirements: If entered, the field MUST contain 12 numeric places. NO spaces allowed. Error Note: 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. Allowed Entries: Not required for LIBRS Releases 1.0/1.1. or 2.0, unless agency uses geographical coordinates to track incidents Entries should either be valid geographical coordinates, or Blank (G). If agencies submit zeroes, program will produce errors because zeroes are numeric. September 2016 LIBRS Specifications, Rel

170 Station/Division/Precinct Identifier (L54) Data Characteristics: 6 Character Alpha Requirements: None Notes: This field is OPTIONAL and is for the reporting agency's use in locating incidents. September, 2016 LIBRS Specifications, Rel

171 Data Characteristics: 15 Character Alpha/Numeric Arrest Transaction Number (L55) Requirements: MUST be present if fingerprints are submitted to the Bureau of Identification of the Louisiana State Police. Notes: 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 Character 5 Characters 6-7 Characters 8-12 Characters th, 5th, 6th, and 7th characters of the ORI number of the agency that made the arrest, or where the live scan device is housed. live scan device number assigned to the device being used to generate this Arrestee's fingerprints. indicates the year this Arrestee's fingerprints are being scanned into this device. Arrest Sequence Number for this arrest event. This is a number counter that sequentially assigns a number to each arrest event 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. September 2016 LIBRS Specifications, Rel