O-NIBRS_SystemSpec_07-17-2015-v2-7
O-NIBRS
Oregon Uniform Crime Reporting
System Software Specification
Version 2.7
July 21, 2015
(Blank Page)
NOTE: This revised system specification supercedes all other previously released
editions. We have made many changes mostly clarifications and typographical.
This System Specification is to be used for the development of a Report
Management System (RMS) that will be used to submit data to the O-NIBRS
Repository at OUCR, all mandatory data elements must be included in each
submission. Agencies are strongly encouraged to develop their RMS’s to include
as many optional data elements as possible.
While law enforcement agencies using Report Management Systems (RMS’s)
currently written to a previous O-NIBRS specification may continue to do so, their
respective RMS’s should be updated to meet this specification as soon as is
feasible. Due to possible changes in reporting requirements for NIBRS, N-DEx or
through legislation in the future, this O-NIBRS System Specification is subject to
change. Until such change becomes necessary, this revision will be the only
System Specification all RMS’s should be designed to meet.
Change Revision Summary can be found at the back of the manual. All changes in
this manual are highlighted in [blue] text, and enclosed in brackets ([ ]). Future
changes will be handled in this same manner.
We are currently developing the documentation to allow for acceptance of data in an
XML format. Please contact us for more information.
(Blank Page)
Table of Contents
Table of Contents ................................................................................................................. i
Introduction...........................................................................................................................1
System Overview ..................................................................................................................1
Offense Codes ......................................................................................................................3
Incident Reports ...................................................................................................................9
Agency Segment 10
Administrative Segment 11
Offense Segment 12
Property Segment 13
Victim Segment 14
Offender Segment 15
Arrestee Segment 16
Individual Segment 17
Individual Supplemental Segment 18
Vehicle Segment 19
Zero Reporting Segment 20
Narrative Segment 21
Data Element Definitions ....................................................................................................23
Data Elements 23
Data Values 23
Description of Data Elements 23
Detailed Data Element Descriptions...................................................................................23
Agency Segment 25
Administrative Segment 49
Offense Segment 73
Property Segment 89
Victim Segment 101
Offender Segment 119
Arrestee Segment 125
Individual Segment 143
Individual Supplemental Segment 163
Vehicle Segment 175
Zero Reporting Segment 189
Narrative Segment 193
Additional Data Elements Required by Offense Type...................................................... 195
Additional Edits .................................................................................................................. 203
General Edits 203
Administrative Segments 203
Offense Segments 204
Property Segments 204
Victim Segments 205
Arrestee Segments 205
Offense Code Edits 206
Narrative Segment Edits 207
Page ii O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Table of Contents - continued
Electronic Submission Specifications ............................................................................. 209
File Name Format 209
FTP or Upload Submission 209
Variable Length Record Format 209
Codes Must be Right-Justified with Zero Left-Fill 210
Record Descriptor Word (RDW) Explanation 210
Segment Levels 210
Action Types 211
Month and Year 211
Record Layout Definitions................................................................................................. 213
Change Revision Summary (v. 2.5) .................................................................................. 229
Change Revision Summary (v. 2.6) .................................................................................. 230
Change Revision Summary (v. 2.6a)................................................................................. 230
Change Revision Summary (v. 2.7) .................................................................................. 231
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page iii
Introduction
It should be stated that the National Incident Based Reporting System (NIBRS) guidelines should be followed along with the
Oregon reporting guidelines. This document describes the system specifications of the Oregon Uniform Crime Reporting system
software. It begins with a system overview that describes the flow of data within the system and how the various components
interact. Then the collection and submission requirements are set forth along with the data validation rules.
System Overview
The primary objective of the new Oregon-NIBRS (O-NIBRS) system is to meet the expanding reporting, analysis, and query
requirements of the state and the law enforcement agencies within it. Thus, the new system is designed to gather information to
produce new statistical reports. It also provides an extendible framework for building an extensive statewide database of persons
and vehicles that will provide local agencies direct query capability through a secure internet connection.
In addition, O-NIBRS is the sole-source for the collection and submission of data for the National Data Exchange (N-DEx) for all
law enforcement agencies within the State of Oregon. N-DEx provides law enforcement agencies an investigational database
with similar search capabilities to O-NIBRS except on a nationwide scale. Because of the investigational nature of both the O-
NIBRS and N-DEx databases, it is essential that law enforcement agencies include as much information as possible in each O-
NIBRS record. For this reason, a number of data elements that were once optional are now mandatory or conditional. Data
available to law enforcement through these 2 databases will only be as good as what law enforcement agencies submit into them.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 1
(Blank Page)
Page 2 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Offense Codes
It is important that all offenses committed in an incident are identified. For example, if a Rape case also involved a Motor Vehicle
Theft and Kidnapping, then you would report all three offenses. However, you must be certain that each reported offense is a
separate and distinct crime. It could be just a part of the original offense. For example, every Robbery includes some type of Assault.
Therefore, Assault should not be reported as a separate crime because it is part of the Robbery offense. On the other hand, if during
a robbery the victim is forced to engage in sexual relations, then you would report both Robbery and Forcible Rape because forced
sexual intercourse is not an element of Robbery.
The offense codes are grouped into three categories: Crimes Against People, Crimes Against Property, and Crimes Against Society.
Crimes against people are crimes in which the victim is present and directly involved in the offense. Crimes against property are
generally crimes where the victim is not present or directly involved in the offense. Crimes against society are crimes that represent
society's prohibitions on engaging in certain types of activity. Some of the following offense codes aren't classified in any of the above
categories because they represent special activities unique to Oregon.
Oregon classifies crimes in four categories; Person (PE), Property (PR), Society (SO) and Oregon Specific Offense (ORSO). The PE
crimes must have a person as a victim, PR crimes must have business and/or person victims, SO crimes report only Society as the
victim and ORSO are subject to special consideration because they can have any of the above as victims. Most ORSO offenses are
Society crimes so you’ll need to see the section on Additional Data Elements Required by Offense (check the table of contents for the
page number) at the back of the manual to determine which ones need additional data.
Offense Listing
Homicide
011 Willful Murder PE
012 Aggravated Murder PE
013 Negligent Manslaughter PE
014 Negligent Homicide – Traffic ORSO
015 Justifiable Homicide PE
Rape
020 Forcible Rape PE
Robbery
031 Highway PR
032 Business PR
033 Service Station PR
034 Conv. Store PR
035 Residence PR
036 Bank PR
037 Car Jacking PR
039 Other Robbery PR
Assault
041 Aggravated Assault PE
042 Attempted Murder PE
043 Simple Assault PE
044 Bomb Threat PE
045 Intimidation /Other Criminal Threat PE
046 Stalker PE
047 Restraining Order Violation PE
048 Reckless Endangering PE
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 3
Burglary
051 Residence PR
052 Business PR
053 Other Structure PR
Larceny
061 Pickpocket PR
062 Purse Snatching PR
063 Shoplifting PR
064 Theft from a Motor Vehicle PR
065 Theft of MV Parts/Accessories PR
066 Theft of Bicycle PR
067 Theft from Building PR
068 From Coin Operated Machine PR
069 All other Larceny PR
Motor Vehicle Theft
071 Motor Vehicle Theft PR
075 Unauthorized Entry into Motor Vehicle PR
Arson
090 Arson PR
Counterfeiting/Forgery
100 Counterfeiting /Forgery PR
Fraud
111 No Account Check PR
112 Account Closed Check PR
113 Not Sufficient Funds Check PR
114 Credit Card /Automatic Teller Machine PR
115 By Deception /False Pretenses PR
116 Of Services /False Pretenses PR
117 Provide False Information to Law Enforcement PR
119 Fraud – Other PR
11C Impersonation PR
11D Welfare Fraud PR
11E Wire Fraud PR
11F Identity Theft PR
11G Computer Crime PR
Embezzlement
120 Embezzlement PR
Stolen Property
130 Stolen Property PR
Vandalism
140 Vandalism PR
141 Crime Damage - damage to property as a result PR
of a criminal act other than Arson or Vandalism
Page 4 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Weapon Law Violations
151 Possess Illegal SO
152 Carry Concealed SO
153 Ex-con in Possession SO
154 Shooting in Prohibited Area SO
155 Explosives/Pyrotechnics SO
159 Weapon Law – Other SO
Prostitution
161 Engage in /Prostitution SO
162 Promote SO
163 Compel SO
[164 Purchase/Human Trafficking SO]
169 Prostitution – Other SO
Sex Crimes
170 Pornography /Obscene Material SO
171 Non-Force Rape PE
172 Contribute to Sex Delinquency PE
173 Physical Molest PE
174 Obscene Phone Call PE
175 Incest PE
176 Exposer PE
177 Forcible Sodomy PE
178 Non-Force Sodomy PE
179 Sex Crime-Other PE
17B Peeping Tom SO
17C Sexual Assault with an Object PE
17D Invasion of Personal Privacy PE
17E Unlawfully Being Where Minors Congregate SO
17F Unlawful Contact With a Minor PE
Drug Law
180 Drug Law Violations SO
181 Drug Paraphernalia SO
Gambling
191 Bookmaking SO
192 Numbers and Lottery SO
193 Games SO
194 Illegal Devices /Machines SO
195 Illegal Payoff SO
196 Sports Tampering SO
199 Other - Gambling Activities SO
Family Offense/Family Offense Non-Violent
201 Child Abandonment PE
202 Child Neglect PE
204 Non-Support PE
205 Criminal Mistreatment PE
209 Family - Other PE
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 5
DUII
210 Driving Under Influence SO
Tobacco
220 Minor in Possession - Tobacco SO
Liquor Law
221 Minor in Possession – Alcohol SO
222 Illegal Liquor-Make, Sell, Possess SO
223 Illegal Establishment SO
224 Drinking in Public SO
225 Furnishing SO
226 Importing SO
227 License Violations SO
228 Minor on Premises SO
229 Liquor Law - Other SO
Extortion/Blackmail
230 Extortion /Blackmail PR
Disorderly Conduct
240 Disorderly Conduct SO
Kidnapping
251 For Additional Criminal Purpose PE & PR
252 Hostage/Shield or Removal/Delay of Witness PE & PR
253 For Ransom PE & PR
254 Hi-Jack, Terrorist PE & PR
255 Custodial Interference PE & PR
256 Involuntary Servitude/Human Trafficking PE & PR
257 Commercial Sex Acts/Human Trafficking PE & PR
[257 Commerical Sex Acts/Human Trafficking PE & PR]
All Other
261 Trespass SO
262 Escape from Your Custody SO
265 Animal Cruelty SO
266 Bribery PR
267 Animal Ordinances SO
268 Garbage Littering SO
269 Other [PE or PR or] SO
Non Criminal Offenses
270 Non Criminal Domestic Disturbance ORSO
Curfew
280 Curfew SO
Runaway
290 Runaway (Juveniles only) SO
Page 6 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Traffic Crime
391 Hit & Run - Misdemeanor ORSO
392 Hit & Run - Felony ORSO
393 Reckless Driving ORSO
394 Eluding ORSO
395 DWS /Revoked - Misdemeanor ORSO
396 DWS /Revoked - Felony ORSO
397 Fail to Display Operators License ORSO
Fish Sport
411 Fishing License Violation ORSO
412 Fishing Closed Season /Area ORSO
413 Fishing Prohibited Hours /Methods ORSO
414 Fishing Exceed Bag Limit ORSO
415 Fishing Possession /Misdemeanor ORSO
416 Fishing Possession /Felony ORSO
419 Fishing - Other ORSO
Fish Commercial
421 Fish - Commercial ORSO
422 Fish - Closed Season /Area ORSO
423 Fish Prohibited Hours /Methods ORSO
424 Fish Possession - Misdemeanor ORSO
425 Fish Possession - Felony ORSO
426 Records Violations ORSO
429 Fish - Other ORSO
Fish Personal Use
431 License Violation ORSO
432 Closed Season /Area ORSO
433 Prohibited Methods ORSO
434 Exceed Bag Limit ORSO
435 Possession Violation ORSO
439 Other ORSO
Game
441 License Violation ORSO
442 Closed Season /Area ORSO
443 Prohibited Hours /Methods ORSO
444 Casting Light ORSO
445 Exceed Bag Limit ORSO
446 Possession in Season - Misdemeanor ORSO
447 Possession out Season - Misdemeanor ORSO
448 Possession out Season - Felony ORSO
449 Other ORSO
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 7
Marine Violation
471 License Violation ORSO
472 Insufficient Life Preservers ORSO
473 Muffling ORSO
474 Other Equipment Violation ORSO
475 Operate Without Lights ORSO
476 Reckless Operation ORSO
477 Speeding ORSO
478 Operate While Intoxicated ORSO
479 Other ORSO
Illegal Alien
500 Illegal Alien ORSO
Custody
511 Protective Custody ORSO
512 Detox ORSO
513 Mental ORSO
514 Material Witness ORSO
[No longer being used
Warrant
520 Warrant ORSO]
Failure to Register as Sex Offender
525 Failure to Register as Sex Offender ORSO
Stolen Motor Vehicle Recovered For Other Agency
530 Vehicle Recovered for Other Agency PR ORSO
Stolen Property Recovered For Other Agency
540 Property Recovered for Other Agency PR ORSO
Fugitive
550 [Warrant]Fugitive] ORSO
Page 8 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Incident Reports
The data elements representing the O-NIBRS data structure have been grouped into distinct segments. These segment groupings provide the
framework for reporting data to the state.
Law enforcement agencies collect detailed data regarding individual incidents and submit them as separate "reports" using prescribed data
elements and data values. This incident report describes the incident, the details of offenses, victims, property, and arrestees. An incident
report may consist of many possible combinations of circumstances ranging from a simple one offense, victim, and offender situation, to a
complex set of multiple offenses, property losses, victims, offenders, and arrestees. In addition, each of the victims may not be involved in each
of the offenses. In other words, one, some, or all of the victims may be connected to each applicable offense.
Incident reports are submitted for all incidents occurring within an agency's jurisdiction where an offense was committed. Each report is made
up of six main segments, or groups of information, and three auxiliary segments. The six primary segments detail the Admin, Offenses, Victims,
Property, Offenders and Arrestees associated with the case. The system will eventually handle and process all National Data Exchange (N-
DEx) data elements. Contact us for more information on providing N-DEx elements outside of what is already collected in O-NIBRS.
The additional segments provide for the collection of information related to people and vehicles involved in the incident as well as narrative
information. These segments include Names, Dates of Birth, Vehicle Makes, Models, etc. and incident narratives. This data will aid
investigative research for the state's law enforcement agencies by directing the investigating agency to the agency reporting the incident.
The purpose of the agency segment is to collect information about the submitting law enforcement agency. The data is required for reporting
employee and population information.
The data elements collected in each segment of information are detailed on the following pages.
Additional data elements will be included as the FBI moves forward with collection of data for the N-DEx System.
References are made to the National Incident Based Reporting System (NIBRS) manuals.
These manuals are: NIBRS – Volume 1 – Data Collection Guidelines and NIBRS – Volume 4 – Error Message Manual and will be referenced
as NIBRS Vol. 1 and NIBRS Vol. 4, respectively.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 9
Agency Segment
Each electronic data submission is accompanied by one segment containing information about the submitting agency. This information should
be updated whenever a change occurs, but is required to be in the September data submission.
The data contained in the Agency Segment is used to ensure that reports of juristiction population and workforce are correct.
The data elements used in the Agency Segment are:
A.1 ORI Number
A.2 Agency Name
A.3 Agency Mnemonic
A.4 Agency Type
A.5 Agency Administrator
A.6 OUCR Representative's Name
A.7 Phone Number
A.8 Fax Number
A.9 Reporting Media Type
A.10 Regional System Name
A.11 Agency Population
A.12 Number of Sworn Males
A.13 Number of Sworn Females
A.14 Number of Civilian Males
A.15 Number of Civilian Females
A.16 Location Address
A.17 Location City
A.18 Location State
A.19 Location Zip Code
A.20 Mailing Address
A.21 Mailing City
A.22 Mailing State
A.23 Mailing Zip Code
A.24 Email Address of OUCR Representative
Note that this segment should be place before any other segments.
Page 10 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Administrative Segment
Note that while Data Elements 1.1 (ORI Number) and 1.2 (Incident Number) are part of the Administrative Segment, they are repeated as the
first two data elements in the Offense, Property, Victim, Offender, Arrestee, Individual, Individual Supplement and Vehicle Segments for the
purpose of linking those segments to the Administrative Segment.
This segment contains administrative data that is applicable to the entire incident report. This is the master segment for the entire Incident
report. Only one Administrative Segment may be submitted per incident. A complete incident record submission begins with an Administrative
Segment and continues with the Offense, Property, Victim, Offender, Arrestee, and the Oregon specific People and Vehicle Index segments.
Each segment is linked with the matchingAdministrative Segment by the agency's ORI and Incident Numbers.
The data elements used in the Administrative Segment are:
1.1 ORI Number
1.2 Incident Number
1.3 Incident Date
1.4 Report Date Indicator
1.5 Incident Hour
1.6 Cleared Exceptionally
1.7 Exceptional Clearance Date
1.8 County Code
1.9 Longitude
1.10 Latitude
1.11 Agency's Location Code
1.12 Incident Address
1.13 Incident Address City
1.14 Incident Address State
1.15 Incident Address Zip Code
1.16 Officer ID
1.17 Security Flag
1.18 Incident Status
1.19 Point of Contact (POC) – Name
1.20 POC – Phone
1.21 POC – Email
1.22 Reported Date
1.23 Cargo Theft
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 11
Offense Segment
Offense Segments are used to identify and describe the offenses involved in the incident (e.g., 090 Arson, 161 Prostitution, etc.). An Offense
Segment is to be submitted for each of the (up to) ten most serious offenses in the incident. Refer to the "Offense Codes" chapter that lists the
offenses by seriousness. Only one Offense Segment is to be submitted for each Offense Code even though there may have been more than
one victim of the crime. At least one Offense Segment must be submitted for each Incident Report.
Example: In the same incident, the offender assaulted two persons by threatening them with a handgun. Only one Offense Segment should be
submitted with "041" = Aggravated Assault entered into Data Element 2.1 (Offense Code). Note that two Victim Segments should also be
submitted which are linked to this Offense Segment by entering "041" into Data Element 4.2 (Victim Connected to Offense Codes).
The data elements used in the Offense Segment are:
1.1 ORI Number
1.2 Incident Number
2.1 Offense Code
2.2 Offense Attempted/Completed
2.3 Oregon Revised Statute
2.4 Offender(s) Suspected of Using
2.5 Location Type
2.6 Number of Premises Entered
2.7 Method of Entry
2.8 Type of Criminal Activity
2.9 Type of Weapon/Force Involved
2.9 Automatic Weapon Indicator
2.10 Firearm Make Type
2.11 Knife Type Code
2.12 Offense Hate/Bias Code
2.13 Domestic Violence Indicator
2.14 Gang Involvement Indicator
2.15 Location Qualifier
Page 12 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Property Segment
Property Segments are used to describe the type, value, and quantity of property involved in the incident. A Property Segment is to be
submitted for each Property Type Loss, etc. which occurred in the incident.
Property Segment data should only be entered for offenses classified as Crimes Against Property. Data elements 3.1 through 3.9 should show
the Total losses, recoveries, seizures, quantity, etc. Submit only one Property Segment report for each type of loss, etc. This includes the
situation when all "Stolen" property is "Recovered" and the value of the recovered property is the same. Two segments would be submitted, one
for "Stolen" and the other for "Recovered."
The data elements used in the Property Segment are:
1.1 ORI Number
1.2 Incident Number
3.1 Property Type Loss, etc.
3.2 Property Description Category
3.3 Value of Property
3.4 Number of Property Items
3.5 Property Offense Code
3.6 Date Recovered
3.7 Suspected Drug Type
3.8 Estimated Drug Quantity
3.9 Type of Drug Measurement
Up to twenty (20) articles (e.g., "Aircraft," "Alcohol," "Automobiles," etc.) can be reported for each type of property loss/etc. If there was no
property loss/etc., "1" = None is to be entered into Data Element 3.1 (Property Type Loss, etc.), and Data Elements 3.2 through 3.9 are to be left
blank (except when the offense is a drug offense -see more detail in Section 3). If it is not known whether a property loss/etc. occurred, "8" =
Unknown is to be entered into Data Element 3.1, and Data Elements 3.2 through 3.9 are to be left blank.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 13
Victim Segment
Victim Segments are used to describe the victims involved in the incident (e.g., their age, sex, race, etc.). A separate Victim Segment is to be
submitted for each of the (up to 999) victims involved in the incident. There must be at least one Victim Segment for each offense in the incident
report.
The data elements used in the Victim Segment are:
1.1 ORI Number
1.2 Incident Number
4.1 Victim (Sequence) Number
4.2a Victim Connected to Offense Code(s)
4.2b Victim Connected to ORS(s)
4.3 Type of Victim
4.4 Age (of Victim)
4.5 Sex (of Victim)
4.6 Race (of Victim)
4.7 Ethnicity (of Victim)
4.8 Resident Status (of Victim)
4.9 Aggravated Assault/Homicide Circumstances
4.10 Additional Justifiable Homicide Circumstances
4.11 Type of Injury
4.12 Related Offender(s)
4.13 Relationship(s) of Victim to Offender(s)
4.14 LEOKA Type of Act
4.15 LEOKA Assignment Type
4.16 LEOKA Activity Type
4.17 LEOKA – Other Officer ORI
Page 14 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Offender Segment
Offender Segments are used to describe the offenders in the incident (e.g., their age, sex, race, etc.). An Offender Segment is to be submitted
for each of the (up to 99) offenders involved in the incident. There must be at least one Offender Segment in each incident report.
The data elements used in the Offender Segment are:
1.1 ORI Number
1.2 Incident Number
5.1 Offender (Sequence) Number
5.2 Age (of Offender)
5.3 Sex (of Offender)
5.4 Race (of Offender)
5.5 Ethnicity (of Offender)
If nothing is known about the offender(s) -- i.e., no one saw the offender(s) and there were no suspects, so even the number of offenders is
unknown -- then 00 is to be entered into the Offender Sequence Number (5.1) and Data Elements 5.2 through 5.4 are to be left blank.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 15
Arrestee Segment
Arrestee Segments are used to report the apprehension of the persons who were arrested for the crimes reported. An Arrestee Segment is to
be submitted for each of the (up to 99) arrestees involved in the incident. This segment describes the individuals arrested for offenses in an
incident. If there were no arrestees, this segment should not be submitted. The Arrestee Segment describes the arrestee (e.g., age, sex, race,
etc.) and the circumstances of the arrest.
The data elements used in the Arrestee Segment are:
1.1 ORI Number
1.2 Incident Number
6.1 Arrestee (Sequence) Number
6.2 Arrest (Transaction) Number
6.3 Arrest Date
6.4 Type of Arrest
6.5 Multiple Clearance Indicator
6.6 Arrest Offense Code
6.7 Arrestee Was Armed With
6.8 Date of Birth (of Arrestee)
6.9 Age (of Arrestee)
6.10 Sex (of Arrestee)
6.11 Race (of Arrestee)
6.12 Ethnicity (of Arrestee)
6.13 Resident Status (of Arrestee)
6.14 Disposition of Arrestee Under 18
6.15 Drug Codes
6.16 DUII Intoxicant Type
6.17 Breath Analyzer Results
Page 16 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Individual Segment
Individual Segments (I & H) are used to collect information related to each person involved in the incident being reported. The Individual Type
indicates how the individual was involved in the case, i.e., a Victim, Arrestee, Offender, or Person of Interest (other).
The data elements used in the Individual Segment are:
1.1 ORI Number
1.2 Incident Number
I.1 Individual Type
I.2 Individual (Sequence) Number
I.3 Name
I.4 Date of Birth (of Individual)
I.5 Age (of Individual)
I.6 Sex (of Individual)
I.7 Race (of Individual)
I.8 Ethnicity (of Individual)
I.9 Resident Status (of Individual)
I.10 Hair Color
I.11 Eye Color
I.12 Skin Color
I.13 Height
I.14 Weight
I.15 Scars, Marks, and Tattoos
I.16 Gang Affiliation Code
I.17 Corrections Indicator
I.18 Registered Sex Offender Flag
I.19 Alias
Data elements I.1 (Individual Type) and I.2 (Individual Sequence Number) combine to uniquely identify the individual within the incident report.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 17
Individual Supplemental Segment
The data elements used in the Individual Supplemental Segment are:
1.1 ORI Number
1.2 Incident Number
I.1 Individual Type
I.2 Individual (Sequence) Number
H.1 Individual Mailing Address
H.2 Individual City
H.3 Individual State
H.4 Individual Zip Code – with +4
H.5 Individual Telephone Number
H.6 Individual Occupation
H.7 Personal Identification Number
H.8 Personal Identification Type
H.9 Personal Identification Issuing Authority
H.10 Citizenship
H.11 Individual Residence Country Code
Page 18 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Vehicle Segment
The Vehicle Segment gathers information related to vehicles involved in the incident. A vehicle should be submitted only once per incident with
appropriate codes If no vehicle information is available, no Vehicle Segment should be submitted.
The data elements used in the Vehicle Segment are:
1.1 ORI Number
1.2 Incident Number
V.1 Vehicle (Sequence) Number
V.2 License Number
V.3 License State
V.4 License Year
V.5 License Type
V.6 Vehicle Identification Number (VIN)
V.7 Vehicle Year
V.8 Vehicle Make
V.9 Vehicle Model
V.10 Vehicle Style
V.11 Vehicle Color
V.12 Vehicle Type
V.13 Recovered Vehicle Condition
V.14 Vehicle Involvement Role Code
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 19
Zero Reporting Segment
The zero reporting segment should only be submitted when no other segments are submitted. It is a confirmation that there was no activity to
report for the month.
1.1 ORI Number
0.1 Incident Number
0.2 Zero Report Month
0.3 Zero Report Year
Note that when submitting this segment, the incident number must be filled with all zeros (0). Also, no other incident segments may be
submitted. The only segment that may be submitted is an agency segment.
Page 20 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Narrative Segment
The Narrative segment is used to report a brief summary of the incident. This segment is required when reporting an incident of homicide (011,
012, 013, 014 or 015) or an incident determined to be a bias crime. The narrative segment is optional for all other incidents.
1.1 ORI Number
1.2 Incident Number
N.1 Narrative
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 21
(Blank Page)
Page 22 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Data Element Definitions
The "data elements" and "data values" set forth in this section represent those which are required to satisfy the requirements of the Oregon
reporting system. Agencies participating in the O-NIBRS program must be able to collect incident data according to the following specifications.
Data Elements
"Data elements" are the data fields used to describe the victims, offenders, arrestees, and circumstances of criminal incidents and
arrests. Examples are: "Incident Number," "Offense Code," "Type of Victim," and "Age of Offender."
Some data elements are required to be reported, i.e., they are "Required." Others may be reported at the option of the agency
submitting the report, i.e., they are "Optional."
Data Values
"Data values" are the specific codes which are allowed to be entered into the data elements. Each code appears in bold print, followed
by its underlined translation. Examples are: "M" = Male, "F" = Female, and "U" = Unknown, which are the data values allowed in the
"Sex" data elements; and "W" = White, "B" = Black, "I" = American Indian/Alaskan Native, "A" = Asian/Pacific Islander, and "U" =
Unknown allowed in the Race data elements. The data values for each data element follow the data element description.
If more than one of the data values associated with a data element would apply to the situation, use the most specific one. For
example, a 7-Eleven store could be described in Data Element 2.4 (Location Type) as a "05" = Commercial/Office Building, "07" =
Convenience Store, or "12" = Grocery/Supermarket. However, since "07" = Convenience Store is the most specific description, it
should be used.
Furthermore, some data elements allow for the entry of more than one data value. For example, Data Element 2.7 (Type Criminal
Activity) allows up to three (3) types of activity to be entered for each offense. If in a drug case, the offenders had grown marijuana and
distributed it by having children sell it at school, the data values of "C" = Cultivating/Manufacturing/Publishing, "D" = Distributing/Selling,
and "E" = Exploiting Children should be entered.
[Description of Data Elements Detailed Data Element Descriptions]
The following data elements and data values are used to report incidents and arrests involving offenses. A complete description of
each data element is given on the following pages.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 23
(Blank Page)
Page 24 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
AGENCY SEGMENT
A.1 ORI Number
The ORI number is the six character NCIC Originating Agency Identifier Number that has been assigned to the reporting
agency. The complete number is unique within the nation and indicates the location of the incident. [Oregon ORI’s are
formatted like OR0240200; for Oregon O-NIBRS reporting you’ll want to extract the right six digits as the ORI in the input
data. For example: OR0240200 would look like 240200 in the input data.]
Format: 6 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 25
A.2 Agency Name
This is the literal name of the reporting agency. This field is used as the description of the Agency's ORI Number when
agency information is printed or displayed.
Format: 30 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Page 26 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.3 Agency Mnemonic
The agency mnemonic is a three character abbreviation of the agency's name. This terminal and printer address is assigned
by LEDS. It is used to direct communication through the LEDS switching system.
Format: 4 Alpha Numeric
Occurrences: 1/ Submission
Mandatory:: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 27
A.4 Agency Type
The agency type is a two character code that classifies the agency as a specific type of law enforcement agency. The
agency type code is used when reports are generated for specific agency types. It is also used when the agency type
determines the order in which agencies are printed on reports.
Format: 2 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Data Values: PD Police Department
SO Sheriff's Office
SP State Police
LC Liquor Control Commission
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 28 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.5 Agency Administrator
This data element is the name of the person who is the chief, sheriff, or administrator of the agency.
Format: 30 Alpha Numeric, (first name last name)
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 29
A.6 OUCR Representative's Name
This data element is the name of the person responsible for the agency's OUCR reporting. This field is used by the OUCR
operations staff to identify the agency's primary contact person regarding OUCR reporting matters.
Format: 30 Alpha Numeric, (first name last name)
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 30 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.7 Phone Number
The agency telephone number field includes the area code, prefix, suffix, and extension of the agency's telephone number.
It is used to facilitate communications between O-NIBRS operations and the reporting agency.
Format: 14 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Example: 50337830570000 Area code/prefix/phone number/extention number or zeros
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 31
A.8 Fax Number
The agency fax number field includes the area code, prefix, suffix, and extension of the agency's telephone number. It is
used to facilitate communications between O-NIBRS operations and the reporting agency.
Format: 14 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Example: 50337830570000 Same format as phone number
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 32 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.9 Reporting Media Type
The reporting media code will describe the media on which the reporting agency submits its O-NIBRS data.
Format: 2 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Data Values: EM Electronic Transfer
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 33
A.10 Regional System Name
The regional system name describes the system that provides law enforcement information and communication services to
the reporting agency.
Format: 8 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Data Values: AIRS
CLASS
NONE = Not Applicable
OSP
PPBS
SOLAR
SOJIC
COPS (Deschutes County)
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 34 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.11 Agency Population
This data element is used to record the population count of each reporting agency's jurisdiction.
Format: 9 Numeric
Occurrences: 1/ Submission
Mandatory: NO Entered by LEDS/OUCR from Portland State University population estimates as of July 1, current
year.
Edits: All of the agencies must have a population greater than zero except for OLCC and State Police.
[NOTE: This information is provided by Portland State University from Census records.]
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 35
A.12 Number of Sworn Males
This data element is used to record the number of sworn male officers employed by the reporting agency. This number may
include jail personnel only if they are sworn law enforcement officers who have authority to investigate crimes and make
arrests outside of the jail. The employee count is used to produce reports used by the state and FBI. A value of 0 (zero) is
acceptable for agencies who have disbanded. [INCLUDE: Full-time criminal law enforcement officers, Chief, Sheriff,
Superintendent and (paid) recruits, jail staff WITH patrol duties), part-time employees job sharing a single position. DO NOT
count or include in SWORN count: Non-sworn officers and staff, animal control, reserve or part-time officers].
Format: 4 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting this information from the input data; agencies will need to directly
enter the information into the O-NIBRS website.]
Page 36 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.13 Number of Sworn Females
This data element is used to record the number of sworn female officers employed by the reporting agency. This number
may include jail personnel only if they are sworn law enforcement officers who have authority to investigate crimes and
make arrests outside of the jail. The employee count is used to produce reports used by the state and FBI. A value of 0
(zero) is acceptable for agencies who have disbanded. [INCLUDE: Full-time criminal law enforcement officers, Chief,
Sheriff, Superintendent and (paid) recruits, jail staff WITH patrol duties), part-time employees job sharing a single position.
DO NOT count or include in SWORN count: Non-sworn officers and staff, animal control, reserve or part-time officers].
Format: 4 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting this information from the input data; agencies will need to directly
enter the information into the O-NIBRS website.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 37
A.14 Number of Civilian Males
This data element is used to record the number of full-time civilian males employed by the reporting agency. This number
includes personnel who provide direct support for law enforcement officers such as records staff, dispatchers and
administrative staff . The employee count is used to produce reports used by the state and FBI. A value of 0 (zero) is
acceptable for agencies who have disbanded. INCLUDE: Full-time criminal law enforecement support employees.
(Records, dispatch, clerical and other administrative office staff, Jail (WITHOUT Patrol Duties), part-time employees job
sharing a single position. DO NOT count or include: Part-time employees or employees not paid from law enforcement
funds such as school crossing guards.,etc.
Format: 4 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting this information from the input data; agencies will need to directly
enter the information into the O-NIBRS website.]
Page 38 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.15 Number of Civilian Females
This data element is used to record the number of full-time civilian female employed by the reporting agency. This number
includes personnel who provide direct support for law enforcement officers such as records staff, dispatchers and
administrative staff . The employee count is used to produce reports used by the state and FBI. A value of 0 (zero) is
acceptable for agencies who have disbanded. INCLUDE: Full-time criminal law enforecement support employees.
(Records, dispatch, clerical and other administrative office staff, Jail (WITHOUT Patrol Duties), part-time employees job
sharing a single position. DO NOT count or include: Part-time employees or employees not paid from law enforcement
funds such as school crossing guards.,etc.
Format: 4 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting this information from the input data; agencies will need to directly
enter the information into the O-NIBRS website.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 39
A.16 Location --Street Address
This data element is used to capture the address of the agency's location.
Format: 30 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 40 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.17 Location City
This data element is used to capture the city where the agency is located.
Format: 15 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 41
A.18 Location State
This data element is used to capture the state where the agency is located.
Format: 2 Alpha
Occurrences: 1/ Submission
Mandatory: Must be = OR
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 42 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.19 Location Zip Code
This data element is used to capture the zip code where the agency is located.
Format: 10 Alpha/Numeric
Occurrences: 1/ Submission
Mandatory: Yes Example: 97304-0000
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 43
A.20 Mailing Street Address
This data element is used to capture the mailing address of the agency.
Format: 30 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 44 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.21 Mailing City
This data element is used to capture the city of the agency's mailing address.
Format: 15 Alpha Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 45
A.22 Mailing State
This data element is used to capture the state of the agency's mailing address.
Format: 2 Alpha
Occurrences: 1/ Submission
Mandatory: Must be = OR
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 46 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
A.23 Mailing Zip Code
This data element is used to capture the zip code of the agency's mailing address.
Format: 10 Alpha/Numeric
Occurrences: 1/ Submission
Mandatory: Yes Example: 97304-0000
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 47
A.24 OUCR Representative E-Mail
This data element is used to capture the email address of the agency's OUCR Representative.
Format: 50 Alpha/Numeric
Occurrences: 1/ Submission
Mandatory: Yes
[NOTE: As of Fall of 2013 we are no longer collecting some of the Agency information section A.3 – A.24 from the input
data; agencies need to notify the OUCR unit when this information changes. See section A. 12 for information regarding
Employee Counts.]
Page 48 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
ADMINISTRATIVE SEGMENT
1.1 ORI Number
The ORI number is the nine character NCIC Originating Agency Identifier Number that has been assigned to the reporting
agency. The complete number is unique within the nation and indicates the location of the incident
Format: 6 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Edits: Must be a valid 6 character ORI number.
Consists of the last 6 digits of the 9-digit ORI.
Example: OR0030200 is entered as 030200
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 49
1.2 Incident Number
The incident number is the unique identifier for each incident in a reporting agency's jurisdiction. It is assigned by the
reporting agency and is sometimes referred to as the case number. The system will accept 12 character incident numbers
however any number of characters up to 12 will be accepted, incident numbers less than 12 should be right-filled with blanks.
Format: 12 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Edits: 1) Must be left-justified with blank right-fill if less than 12 characters in length.
2) Valid character combinations can include A-Z, 0-9 and the ‘-‘. For example, 09-1234SC is
valid, but 09+1234*SC is invalid.
3) Cannot have embedded "blanks" between the first and last character entered.
4) For each submitting agency, as identified in "1.1 ORI Number" above, the value must be a
unique number. This means that no two incidents can have the same incident number. Some
agencies ensure uniqueness by prefixing the incident number with a two-digit year followed by
a number starting with 1, while others just increment the number by 1 for each new incident.
Page 50 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.3 Incident Date
The incident date is the date when the incident occurred or started. The date value should be entered as YYYYMMDD. It
may not exceed the current date or be before January 1, 1989.
If the actual incident date is not known, the date of the report may be entered and an R placed in the Report Date Indicator
field.
Format: 8 Numeric / YYYYMMDD
Occurrences: 1/ Incident
Mandatory: Yes
Edits: 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 (e.g., June cannot have 31 days). The date cannot exceed the current date.
2) The date cannot be earlier than 01/01/1989
3) The date cannot be later than the year and month the file represents. For example, the January
2011 file cannot contain incidents happening later than this date.
Note: If the incident occurred at exactly midnight, enter the Incident Date as if the time was 1
minute past midnight. For example, if the crime occurred at exactly midnight on Thursday, enter
Friday's date.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 51
1.4 Report Date Indicator
A value of R is entered whenever a report date is submitted in the place of the incident date.
Format: 1 Alpha
Occurrences: 1/ Incident
Mandatory: No, default = “blank”
Page 52 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.5 Incident Hour
The incident hour is the time when the incident occurred or started. The value is entered into 24 hour military clock format.
Format: 2 Alpha/Numeric
Occurrences: 1/ Incident
Mandatory: Conditional, if known must be entered
Edits: If entered, it must be "00" through "23", “DY” or “NT”
Blank = Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 53
1.6 Cleared Exceptionally
The clearance indicator is a code used to indicate the reason that the incident is being exceptionally cleared. An unfounded
incident cannot be cleared exceptionally. If the incident is still being investigated or the incident is cleared by arrest, a value
of N should be entered.
Format: 1 Alpha
Occurrences: 1/ Incident
Mandatory: Conditionally required
Edits: 1) Must be a valid code.
2) Cannot be "N" = Not Applicable if Exceptional Clearance Date is entered.
3) When a value other than "N" = Not Applicable is entered, there can be no Arrestee Segments
associated with the Incident Report.
Data Values: A Death of Offender
B Prosecution Declined
C Extradition Denied
D Victim Refused to Cooperate
E Juvenile/ No Custody
N Not Applicable
Page 54 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.7 Exceptional Clearance Date
If the incident was cleared by exceptional means, the date the clearance took place should be entered in this data element.
Format: 8 character date in this format or blank YYYYMMDD
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: 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 (e.g., June cannot have 31 days). The date cannot exceed the
current date.
2) The clearance date cannot be earlier than the incident date.
3) Must be present if case was cleared exceptionally per data value code in Cleared
Exceptionally field.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 55
1.8 County Code
The incident county code identifies the county in which the incident occurred. For agencies whose jurisdiction crosses
county boundaries, a county code must be entered if different from the agency's primary code.
Format: 2 Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Edits: Must be a valid code.
Data Values:
01 Baker 02 Benton
03 Clackamas 04 Clatsop
05 Columbia 06 Coos
07 Crook 08 Curry
09 Deschutes 10 Douglas
11 Gilliam 12 Grant
13 Harney 14 Hood River
15 Jackson 16 Jefferson
17 Josephine 18 Klamath
19 Lake 20 Lane
21 Lincoln 22 Linn
23 Malheur 24 Marion
25 Morrow 26 Multnomah
27 Polk 28 Sherman
29 Tillamook 30 Umatilla
31 Union 32 Wallowa
33 Wasco 34 Washington
35 Wheeler 36 Yamhill
Page 56 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.9 Longitude
If known, the longitude based upon the incident location should be entered here.
Format: 10 Numeric
Occurrences: 1/ Incident
Mandatory: No
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 57
1.10 Latitude
If known, the latitude based upon the incident location should be entered here.
Format: 10 Numeric
Occurrences: 1/ Incident
Mandatory: No
Page 58 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.11 Agency's Location Code
The location codes submitted are defined by each reporting agency. The agency is to decide the most logical way to dissect
their jurisdiction into meaningful areas and assign a corresponding code.
This data is used to provide summarized data to the submitting agency.
Format: 9 [Alpha/]Numeric
Occurrences: 1/ Incident
Mandatory: No
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 59
1.12 Incident Address
This data element is used to capture the address where the incident occurred.
Format: 30 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Page 60 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.13 Incident City
This data element is used to capture the city of the address where the incident occurred.
Format: 15 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 61
1.14 Incident State
This data element is used to capture the state of the address where the incident occurred.
Format: 2 Alpha
Occurrences: 1/ Incident
Mandatory: Yes, default = OR
Page 62 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.15 Incident Zip Code
This data element is used to capture the zip code of the address where the incident occurred. The zip code plus the four
digit extension may be entered.
Format: 10 Alpha/Numeric
Occurrences: 1/ Incident
Mandatory: Yes Example: 97304-0000
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 63
1.16 Officer ID
This field contains the ID number of the officer reporting the incident. The officer ID numbers are assigned by each reporting
agency.
Format: 5 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: No
Page 64 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.17 Security Flag
This field contains the indicator for green, yellow or red security.
Format: 1 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Edits: Must be a valid code.
Data Values: G Green – Unrestricted Access
Y Yellow – Pointer Based Access
R Red – Restricted Access
Definitions: Green: Law enforcement agencies with appropriate access authority will have access to the full record
and all data elements within the record. For investigative data-sharing purposes, all agencies
are encouraged to code their records as Green. All records will be considered Green unless
otherwise marked.
Yellow: Law enforcement agencies with appropriate access authority will only receive Point Of Contact
(POC) information if an inquiry “hits” on a record with a Yellow security flag. In N-DEx
agencies that enter records with a Yellow security flag may specify certain investigators or
sharing groups to have full access to the record. All others will only receive the record’s POC
information.
Red: Law enforcement agencies with appropriate access authority will not receive any indication
that a record exists if an inquiry “hits” on a record with a Red security flag. If an inquiry is
made on a record that has a Red security flag, the owner of the record will receive a
notification from N-DEx that an inquiry was made. Agencies are strongly encouraged to use
the Red security flag sparingly and limit it to only the most sensitive of records where
dissemination of the information could compromise an on-going, confidential investigation.
Caveat: Regardless of which security flag is used, no data that could identify a person, address, business, vehicle or
other sensitive information will ever be made available to the public or any other entity without the
appropriate access authority. The only information to be made available to those without proper authority
will be statistical information, just as it has been in Oregon since 1973.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 65
1.18 Case Status Indicator
This field contains the case status indicator.
Format: 1 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes
Edits: 1) Must be a valid code.
2) When value is “A” or “T” = Cleared by Arrest, record must include at least 1 Arrestee
Segment.
3) When value is “E” = Cleared by Exception, data element 1.6 “Cleared Exceptionally” cannot
have a data value of “N” = Not Applicable.
4) When value is “E” – Cleared by Exception, data element 1.7 “Exceptional Clearance Date”
must have a value.
Data Values: A Cleared by Arrest (by Your Agency)
C Administratively Closed: Closure of a case because investigation cannot proceed for some
reason. For example, the victim of a crime may be unavailable for interview due to being
out of the country for a prolonged period of time. An Administratively Closed case may be
re-opened at a later date. Administratively closing a case does not “clear” the case.
E Cleared by Exception: – See 1.6 for details.
N Inactive: All leads in a case have been investigated and the investigation cannot move
forward. The case is set aside until new leads are developed. A “cold case”. Giving a case
an Inactive status does not “clear” the case.
O Open
P Pending: The investigation is awaiting additional anticipated information. For example,
forensic evidence has been sent to the crime lab and investigators are waiting for results
before moving forward. A Pending case has not been “cleared”. It is an open case where
investigation has been discontinued or reduced for a short period and will resume upon
receipt of expected information, return of a witness for interview, etc.
R Re-opened
T Cleared by Arrest (by Another Agency)
U Unfounded
Page 66 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.19 Point of Contact - Name
This field contains the name of the Point of Contact for this incident.
Format: 30 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: If blank - field will be populated with the agency OUCR Representative information from the Agency
record.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 67
1.20 Point of Contact - Phone
This field contains the phone number of the Point of Contact for this incident.
Format: 10 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: If blank - field will be populated with the agency OUCR Representative information from the Agency
record.
Page 68 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.21 Point of Contact - Email
This field contains the email address of the Point of Contact for this incident.
Format: 40 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: If blank - field will be populated with the agency OUCR Representative information from the Agency
record.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 69
1.22 Reported Date
The reported date is the date when the incident was reported to authorities. The date value should be entered as
YYYYMMDD. It may not exceed the current date or be before January 1, 1989.
If the actual incident date is not known, the date of the report may be entered and an R placed in the Report Date Indicator
field (1.4).
Format: 8 Numeric / YYYYMMDD
Occurrences: 1/ Incident
Mandatory: No, optional
Edits: 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., 20xx). In addition, days cannot exceed maximum for the
month (e.g., June cannot have 31 days). The date cannot exceed the current date.
2) The date cannot be earlier than 01/01/1989
3) The date cannot be later than the year and month the file represents. For example, the January
2008 file cannot contain incidents happening later than the last day of that month.
Note: If the incident occurred at exactly midnight, enter the Incident Date as if the time was 1
minute past midnight. For example, if the crime occurred at exactly midnight on Thursday, enter
Friday's date.
Page 70 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
1.23 Cargo Theft
This data element is to be used to indicate whether or not the incident involved a cargo theft. This data element must
be entered when the incident has at least one of the allowed offenses.
[Cargo Theft is defined as the theft of product being commercially transported.]
Format: 1 Alpha
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: 1) Must be entered if incident includes one of the following offenses:
03X Robbery – (all forms)
05X Burglary – (all forms)
064 Larceny - Theft From Motor Vehicle
067 Larceny - Theft From Building
069 Larceny - All Other Larceny
071 Motor Vehicle Theft
114 Fraud – Credit Card / Automatic Teller Machine
115 Fraud – By Deception / False Pretenses
116 Fraud – Of Services / False Pretenses
[117 Fraud – False Info to Law Enforcement]
119 Fraud - Other
11C Fraud - Impersonation
11E Fraud – Wire Fraud
[11F Fraud – Identity Theft]
120 Embezzlement
230 Extortion / Blackmail
266 All Other - Bribery
2) Must be: Y or N
3) Otherwise blank
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 71
(Blank Page)
Page 72 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
OFFENSE SEGMENT
2.1 Offense Code
The offense codes describe the offense(s) that occurred during an incident.
Format: 3 Alpha Numeric
Occurrences: Up to 10/ Incident
Mandatory: Yes
Edits: Must be a valid code.
Data Values: See the section titled Offense Codes for a complete listing of valid offenses.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 73
2.2 Offense Attempted/ Completed
This flag indicates whether or not the specified offense was completed or just attempted.
Format: 1 Alpha
Occurrences: 1/ Offense
Mandatory: Yes
Edits: 1) Must be a valid code.
2) If "A" = Attempted is entered and Offense Code is a "Crime Against Property," Property Type
Loss, etc. must be "1" = None or "8" = Unknown. If one or more property offenses is "C" =
Completed, ignore this edit.
3) If the Offense Code is a "Crime Against Property," Kidnapping (25x), Gambling (19x), or Drug
Law Violation (18x), and Offense Attempted/Completed is "C" = Completed, a Property
Segment must be sent with a valid code in Property Type Loss, etc..
4) If theOffense Code is an Assault (04x) or Homicide (01x) offense, the offense must be "C" =
Completed.
Data Values: A Attempted
C Completed
Page 74 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.3 Oregon Revised Statute
The Oregon Revised Statute associated with the UCR offense code. The first four characters are followed by the period and
then the last 3 characters (E.G. 016 95). When the ORS is only 6 digits (which is the norm), the first character should be
padded with a zero. [Many agencies have their own local ordinances that will be reported as offenses, but we are unable to
enter all the local ordinances, so those will need to be reported to the state as statute 0221.926.]
Format: 8 Alpha/numeric (i.e., 123A.123)
Occurrences: 1/ Offense
Mandatory: [Yes Optional]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 75
2.4 Offender(s) Suspected of Using
This data element is used to indicate if any of the offenders in the incident were suspected of consuming alcohol or using
drugs or narcotics during or shortly before the incident, or of using a computer or computer equipment to perpetrate the
crime. You may enter up to three different entries for each offense.
Format: 1 Alpha
Occurrences: Up to 3/ Offense
Mandatory: Yes
Edits: 1) Must be a valid code.
2) If more than one code entered, cannot be a duplicate.
3) Value "N" = Not Applicable is mutually exclusive with any other value entered, i.e., "N" is to be
entered only if no other code applies.
Data Values: A Alcohol
B Burglar Tools [(not sent to FBI/NIBRS)]
C Computer Equipment
D Drugs/ Narcotics
N Not Applicable
Page 76 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.5 Location Type
The type of location where the offense occurred is described using this field. If the location can be described using more
than one code, use the one that best describes the location.
Format: 2 Numeric
Occurrences: 1/ Offense
Mandatory: Yes
Edits: Must be a valid code.
Data Values: Dwelling
10 Single Family Residence
11 Apartment / Plex / Condominium
12 Club/ Dormitory / Rooming House
13 Cabin
14 Hotel / Motel
15 Shelter – Mission / Homeless
16 Halfway House / Transitional
Public Buildings
20 Public Safety Facility / Jail / Prison
21 Government Office / Service
22 Public School (Elementary/Secondary)
23 Auditorium / Stadium / Arena / Coliseum
24 Airport/ Depot / Bus / Train Terminal
25 Church / Synagogue / Temple
26 Private School (Elementary / Secondary)
27 Hospital
28 Military Facility
29 Museum
92 Public School (College / University)
93 Private School (College / University)
[97 Community Center]
Business
30 Restaurant
31 Theater
32 Bowling Alley / Skating Rink / Arcade
33 Bar/ Night Club / Tavern / Lodge
34 Financial (Bank, Insurance, Finance, etc.)
35 Services (Gas, Rental, etc.)
36 Medical / Dental
37 Pharmacy / Drug Store
38 Grocery
39 Convenience Store (7-11, Circle K, etc.)
40 Department / Variety Store
41 Apparel (Clothing, Shoes, Furs, etc.)
42 Jewelry / Camera
43 Furniture / Appliance
44 Hardware / Sporting Goods
45 Motor Vehicle / Sales / Service / Parts
46 Marine
47 Construction (Building, Electrical, Plumbing, etc.)
48 Liquor / Beverage Store
49 Other Commercial Office Building
[continued on next page]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 77
80 Amusement Park / Fairgrounds
81 Automatic Teller Machine (stand alone, not related to bank building)
83 Auto Body Repair Shop (as opposed to sales/routine service)
84 Public Gaming Facility (Casino, etc.)
85 Daycare Facility
86 Assisted Living (Adult Foster Home, Nursing Home, etc.)
94 Shopping Center / Mall
96 Other Commercial Business [(Equipment Rental, etc.)]
Other Structures
50 Rental Storage Facility (Self Storage Etc.)
51 Other Residence Bldg. (Storage bldg., Pump house, etc.)
52 Other Farm Bldg. (Barn, Shed, etc.)
53 Dock / Pier / Wharf
54 Factory / Warehouse
55 Cargo Container
56 Abandoned / Condemned Structure
59 Other Buildings
67 Box Car
68 Airplane, Train, Cruise Ship
Thoroughfare
60 Street / Alley / Sidewalk
61 Freeway
62 Other Road
63 Bridge / Viaduct / Tunnel
64 Parking Lot / Public Driveway
65 Residential Driveway
66 Rail Line (Tracks, Roadbed, Etc.)
Area
70 Golf Course
71 Campground
72 Water / Shoreline (Ocean, Lake, River, etc.)
73 Cemetery
74 Yard / Related Area (Associated with Residences e.g., Front Yard / Back Yard / Garden)
75 Developed Farm Land / Pasture
76 Logging Site
77 Woods / Forest / Mountains
78 State Park / State Campground; (for all other campgrounds use 71; for all other parks use 91)
79 Other Area
82 Ball Field (Soccer / Football / Baseball / Softball)
87 Rest Area
88 Vacant Lot
89 Construction Site
90 Storage Yard (Storage for Heavy Machinery / Semi Trailers / Farm Equipment)
91 Park / Playground
95 Tribal Lands
Page 78 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.6 Number of Premises Entered
This field is [allowed used only when you have a burglary of offense codes and] location types [such as burglary (052)] of a
hotel or motel or rental storage facility.. It is used to indicate the number of premises that were entered and is applicable only
for location types that have multiple units.
Format: 2 Numeric
Occurrences: 1/ Offense
Mandatory: Conditional
Edits: 1) Must be entered if the Offense Code is Burglary ([05x 052]) and Location Type contains Hotel/
Motel/ Etc. (14) or Rental Storage Facility (50).
2) Must be numeric entry of 01 - 99 if entered.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 79
2.7 Method of Entry
This entry indicates whether or not force was used to enter a structure. The code is only allowed and required for specific O-
NIBRS offenses.
Format: 1 Alpha
Occurrences: 1/ Offense
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be entered when the Offense Code is Burglary (05x).
3) Must not be entered when the Offense Code is not Burglary (05x).
Data Values: F Force
N No Force
Page 80 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.8 Type of Criminal Activity/Gang Information
The code submitted in this field is used to identify additional information describing the criminal activity of the offender(s).
You may enter up to three different activity codes per offense.
Format: 1 Alpha
Occurrences: Up to 3/ Offense
Mandatory: Conditional [if offense is one of those listed in 3 or 4 below, valid codes must be entered]
Edits: 1) Must be a valid code.
2) If more than one code entered, cannot be a duplicate.
3) When Offense Code is:
[100 Counterfeiting/Forgery
130 Stolen Property Offenses
170 Pornography/Obscene Material
194 Illegal Devices/Machines
Data Values: B Buying/Possessing/Receiving
C Cultivating/Manufacturing/Publishing
D Distributing/Selling
E Exploiting Children
F Tampering
O Operating/Promoting/Assisting
T Transporting/Transmitting/Importing
U Using/Consuming
4) 15X Weapon Law Violations
P Possessing/Concealing (Weapons only)
5) 180 Drugs Law Violations
181 Drug Equipment Violations
Q Possess For Sale (Drugs)
R Possess For Use (Drugs)
S Furnishing (Drugs)
Z Obtain Unlawfully (Drugs)
6) When Offense Code is:
011 Willful Murder
012 Aggravated Murder
013 Negligent Manslaughter
020 Forcible Rape
03X Robbery
041 Aggravated Assault
042 Attempted Murder
043 Simple Assault
045 Intimidation/Other Threat
177 Forcible Sodomy
17C Sexual Assault With An Object
173 Physical Molest
25X Kidnapping/Abduction
(change in sort order)
Data Values: G Other Gang
J Juvenile Gang
N None/Unknown
(change in sort order)]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 81
2.9 Type of Weapon/Force Involved
The types of weapons or force used by the offender(s) in the commission of the specified offense are submitted in this field.
You may enter up to three different codes per offense.
Certain weapons can be classified as automatics and the corresponding codes are extended with an A.
Format: 3 Alpha Numeric
Occurrences: Up to 3/ Offense
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) If more than one code entered, cannot be a duplicate.
3) Value "99" = None is mutually exclusive with any other value, i.e., "99" is to be entered only if
no other code applies.
4) [Must Can} only be entered when Offense Code is:
011, 012,[ 013] Murder
[013, 014 Negligent Manslaughter, Negligent Homicide Traffic]
015 Justifiable Homicide
020 Forcible Rape
03X Robbery
041 Aggravated Assault
042 Attempted Murder
043 Simple Assault
15X Weapon Law Violations
173 Physical Molest
177 Forcible Sodomy
17C Sexual Assault With An Object
230 Extortion /Blackmail
25X Kidnapping/Abduction
5) If the firearm is an Automatic, add "A" as the third character; valid only with codes: 11, 12, 13,
14 & 15 [. "11" = Firearm (Type Not Stated), "12" = Handgun, "13" = Rifle, "14" = Shotgun,
"15" = Other Firearm].
6) The third character of the code must be "A" = Automatic or blank.
7) If an Offense Segment was submitted for Simple Assault, Type Weapon/Force Involved can
only have codes of "40" = Personal Weapons, "90" = Other and "95" = Unknown. All other
codes are not valid because they do not relate to a simple assault.
8) If a homicide, attempted homicide or aggravated assault offense is submitted, Type
Weapon/Force Involved cannot have "99" = None. Some type of weapon/force must be used
in a homicide or aggravated assault offense.
9) If offense = 15X, weapon can be any code EXCEPT 40, 99.
Data Values:
11 Firearm [(not 12, 13, 14)] 40 Personal Weapons
12 Handgun 50 Poison
13 Rifle 60 Explosives
14 Shotgun 65 Fire / Incendiary Device
15 Other Firearm [(bazookas, stinger missiles, 70 Drugs / Narcotics / Sleeping Pills
rocket and grenade launchers and cannons)] 85 Asphyxiation
18 Taser 86 Drowning
19 Chemicals (i.e., mace, pepperspray) 87 Strangulation
20 Knife/ Cutting Instrument 90 Other
30 Blunt Object 95 Unknown
35 Motor Vehicle 99 None
Page 82 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.10 Firearm Make Code
This code is used to indicate the make of firearm.
Format: 3 Alpha/Numeric
Occurrences: Up to 3/ Offense
Mandatory: Conditional
Edits: 1) Must be a valid code if not blank.
2) If more than one code entered, cannot be a duplicate.
3) Value "99" = None is mutually exclusive with any other value, i.e., "99" is to be entered only if
no other code applies.
4) Can only be entered when Offense Code is one of those listed in 2.9 [and weapon type is one
of the following 11, 12, 13, 14 or 15].
Data Values:Refer to the NCIC manual for current listing.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 83
2.11 Knife Type Code
This code is used to indicate the type of knife involved.
Format: 1 Alphanumeric
Occurrences: 3/ Offense
Mandatory: Conditional, must be present if known.
Edits: 1) Must be a valid code if not blank.
[2) Weapon type = 20.]
Data Values: A Kitchen/Cooking/Dining
B Butterfly/Switch Blade
C Pocket-Multipurpose
D Pocket-Single Blade
E Hunting/Bowie/Fixed Blade
F Tactical/Dagger/Boot
G Throwing (includes Stars)
H Utility
J Sword/Bayonet
K Razor
L Axe/Hatchet
M Machete
Page 84 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.12 Offense Hate/Bias Code
This code is used to indicate the commission of an offense that was motivated by hate or bias toward a racial, religious,
ethnic/national origin, or sexual orientation group. This data element also collects a special set of Oregon bias codes.
Format: 2 Numeric
Occurrences: 1/ Offense
Mandatory: Yes
Edits: Must be a valid code.
Racial Sexual
11 Anti-White 41 Anti-Male Homosexual (Gay)
12 Anti-Black or African American 42 Anti-Female Homosexual (Lesbian)
13 Anti-American Indian/Alaska Native 43 [Anti-Lesbian, Gay, Bisexual or Transgender
14 Anti-Asian[/ Pacific Islander or Native Mixed Group]
Hawaiian] 44 Anti-Heterosexual
15 Anti-Multi-Racial Group 45 Anti–Bisexual
[16 Anti-Native Hawaiian or Other Pacific Islander]
[Gender
Religious 46 Anti–Female
21 Anti-Jewish 47 Anti–Male
22 Anti-Catholic
23 Anti-Protestant Gender Identity
24 Anti-Islamic (Moslem) 48 Anti–Transgender
25 Anti-Other Religion 49 Anti - Gender Non-Conforming]
26 Anti-Multi-Religious Group
27 Anti-Atheism/Agnosticism Oregon Bias
[28 Anti-Mormon 51 Age
29 Anti-Jehovah’s Witness 52 Citizenship
81 Anti-Eastern Orthodox (Greek, Russian, etc.)] 53 Eco/Social Status
82 Anti-Other Christian 54 Labor Union
83 Anti-Buddhist 55 Marital Status
84 Anti-Hindu 57 Political Affiliation
85 Anti-Sikh]
Disability
Ethnicity/National Origin 61 Anti - Physical Disability
31 Anti-Arab 62 Anti - Mental Disability
32 Anti-Hispanic or Latino
33 Anti-Other [Race]/Ethnicity/Ancestry [National None or Unknown
Origin] 88 No Bias
99 Unknown Bias
[NOTE: The codes under Religious above were renumbered from 20, 30, 34, 35, and 36 to 81, 82, 83, 84 and 85.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 85
2.13 Domestic Violence Indicator
This field indicates whether or not the offense reported is the result of a domestic violence dispute. Enter a Y if domestic
violence was involved and an N if it was not.
Format: 1 Alpha
Occurrences: 1/ Offense
Mandatory: Yes
Edits: Must be Y or N.
Page 86 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
2.14 Gang Involvement
The gang involvement field is used to indicate whether or not any gang was involved in the commission of the offense. Enter
a Y if a gang was involved and N if it was not.
Format: 1 Alpha
Occurrences: 1/ Offense
Mandatory: Yes
Edits: Must be Y or N.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 87
2.15 Location Qualifier
This field contains the location qualifier, identifying the state of the location.
Format: 1 Alpha Numeric
Occurrences: 1/ offense
Mandatory: Conditional
Edits: 1) If the location is a structure (location types: [10-16, 20-59, 67, 68, 80, 81, 83-86, 91, 92-94,
97)] the code must be valid.
2) Must be a valid code.
Data Values: A Abandoned - The location is a structure that has been vacated with no apparent intention of
the owner to return. The location is left to decay with no maintenance or care given to prevent
weathering or other damage. Occasionally the owner will inflict damage such as setting the
location on fire upon leaving. An example of an abandoned building would be a warehouse
that has gone unused for a number of years, has fallen into disrepair due to weathering and
lack of maintenance and is infested with weeds and vermin.
O Occupied - The location is in use, or is frequently used with short periods of vacancy between
uses. An example of an occupied structure would be a residence where a family lives. It is
not necessary for someone to physically be present at all times for a location to be occupied.
For example, while the occupants of a residence are all out shopping, someone burglarizes
the home. Even though the building is empty of occupants at the time of the burglary, there is
a family that normally resides there on a daily basis and therefore “occupy” the residence.
V Vacant - The location or structure is temporarily not being used, but is maintained so that it
can be occupied with little or no effort. An example of a vacant structure would be an office
building where former tenants have recently moved out and new tenants have not yet moved
in. The owner of the office building maintains the property so that new tenants can easily
move in and occupy the offices.
U Unknown
Page 88 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
PROPERTY SEGMENT
3.1 Property Loss Code.
This code describes the circumstances surrounding property involved in the incident. Certain offense codes require the
submission of specific property codes. For example, an incident with a Completed Burglary (05x) offense must contain a
property segment for the stolen and/or recovered property.
Format: 1 Numeric
Occurrences: Up to 8/ Incident
Mandatory: Conditional
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
3) If "1" = None or "8" = Unknown, Data Elements 3.2 through 3.9 must be blank. The exception
is when the offense is a Drug Law Violation (180). In this case, if "1" = None is entered, then
only Suspected Drug Type (3.7) should be provided.
4) If "5" = Recovered, every property description code entered into Data Element 3.2 (Property
Description) must also have been reported as "7" = Stolen/Etc. This applies to both initial
submissions and resubmissions for incident reports . This does not apply, of course, for Stolen
Property Offenses (130), Recovered Vehicle – Other Agency (530) or Recovered Property –
Other Agency (540).
5) If code is "2" = Burned, "3" = Counterfeited/Forged, "4" = Destroyed/ Damaged/ Vandalized,
"5" = Recovered, "6" = Seized, or "7" = Stolen/Etc., Data Elements 3.2 - 3.9 must have
applicable entries in the segment.
Data Values: 1 None
2 Burned [(includes damage caused in fighting the fire)]
3 Counterfeited/ Forged
4 Destroyed/ Damaged/ Vandalized
5 Recovered [(to impound property that was previously stolen)]
6 Seized [(to impound property that was not previously stolen)]
7 Stolen{/Etc. (includes bribed, defrauded, embezzled, extorted, ransomed, robbed, etc.)]
8 Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 89
3.2 Property Description Category
The property description codes define categories of property such as Automobiles, Bicycles, or Firearms. You may submit
up to twenty different property categories for each type of Property Loss code. If more than twenty categories of property
need to be submitted, the first nineteen entries should define the most valuable/notable (as determined by the reporting
agency) and the remaining types of property are combined and submitted as the twentieth with the code of 750 =
"Miscellaneous".
Format: 3 Numeric
Occurrences: Up to 20/ Property Type Loss, etc.
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) If more than one code entered, cannot be a duplicate.
3) If “880” = Pending Inventory is entered, Value of Property must be = Unknown ($1). One dollar
is used as a quality assurance edit check that instructs the computer to accept the “880” entry.
4) At least one description code must be entered when Property Type Loss, etc. contains Property
Segment(s) for: "2" = Burned, "3" = Counterfeited/Forged, "4" = Destroyed/Damaged/Vandalized,
"5" = Recovered, "6" = Seized, "7" = Stolen/Etc.
5) If "5" = Recovered, every property description code entered into Property Description must also
have been reported as "7" = Stolen/Etc. This does not apply, for Stolen Property Offenses (130),
Recovered Vehicle – Other Agency (530) or Recovered Property – Other Agency (540).
Data Values: 010 Bicycle / Tricycle
020 Boats
030 Cameras / Related Equipment / Camcorder
040 Clothing / Furs
051 Farm Tractor (under 50 hp)
052 Farm Tractor (over 50 hp)
053 Farm Tillage Imp. (Plow disc, etc.)
054 Farm Irrigation Equipment
055 Farm Spraying Equipment
056 Farm Harvest Imp. (Picker, baler, swather, combines, etc.)
057 Farm - All Other
058 Garden / Lawn Machine (Tiller, mower)
059 Garden - All Other
060 Furniture
070 Gambling Equipment / Paraphernalia
080 Household & Appliances
085 Art Supplies
086 Collectibles
090 Jewelry / Precious Metals / Watches (Gold, Silver, Platinum, etc.)
095 Venerated Object
100 Complete Computer (laptop or desk[s]top, etc.)
101 Hard Disk
102 Removable Storage Devices (Floppy Disks/Drives, Flash Drives, etc.)
103 Computer Monitor
104 Computer CD ROM
105 Computer Ram
106 Computer CPU Chip
107 Computer Tape Backup
108 Computers Other (Keyboard, Mouse, etc.)
109 Computer Software
110 Telephone / Accessories
111 Cell Phones / Accessories
112 Hand-held computers (i.e., [GPS], Palm Pilot, PDA, etc.)
113 Gaming Consoles / Accessories (Xbox, PlayStation, etc. Except Game Software)
120 Musical Instruments
130 Office Equipment
Page 90 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
141 Money (Legal tender, e.g., coins and paper currency)
142 Negotiable Instrument (Any document other than currency, which is payable without restrictions,
e.g., endorsed checks, endorsed money orders, gift cards, etc.)
143 Nonnegotiable Instruments (Documents requiring further action to become negotiable, e.g.,
unendorsed checks, money orders, etc.)
144 Mail documents
145 Mail Box
146 Documents, Personal and Business (receipts, files)
151 Radio
152 Stereo / Phonograph / Cassette / CD Player / MP3 Player / Ipod
153 Tape Recorder / Player
154 Television
155 VCR / DVD
156 P.A. / Paging Devices
157 Sound Metering Device
158 Two Way Radios (CB, walkie talkie, etc.)
159 Other Sound Equipment
160 Sports Equipment (Team Sports such as Baseball, Soccer, etc.)
161 Camping / Backpacking Equipment
162 Fishing Equipment
163 Hunting Equipment (Except Firearms)
170 Tools
180 Purses / Handbags / Wallets
[185 Luggage (suitcases, attaché, back packs (non-camping), steamer trunks)]
190 Credit / Debit Card (Includes automatic teller machine cards)
195 Personal ID (SS Card, DL, etc)
197 Identity – Intangible (A Person’s Identity) only offenses 115, 117, 119, 11C & 11F
200 Vehicle Parts / Accessories
210 Viewing Equipment (i.e., movie projector, etc.)
215 Binoculars, Telescopes, Microscopes, etc.
220 Firearms
225 Firearm Accessories (Ammunition, Holsters, Cases, Cleaning Kits, etc.)
230 Knives
235 Other Weapons (Brass Knuckles, Nun Chucks, Sling Shot, Pellet / BB / Paint Gun)
240 Explosives / Related (Except Fireworks)
241 Fireworks
245 Law Enforcement Equipment (Handcuffs, Batons, Vests, etc.)
(Excludes Firearms, Radios, Binoculars)
251 RV Trailer / Tent Trailer
252 Truck Trailer (Semi-Trailer)
253 Other / Utility Trailers
254 Pickup Canopy / Shell
255 Pickup Truck Camper
261 Horse(s)
262 Cattle
263 Pig(s)
265 Sheep
266 Llama(s)
269 Other Mammals (Other common farm stock)
270 Heavy Construction / Machinery
280 Drug / Narcotic Equipment
281 Drug Records (i.e., prescriptions)
282 Drug Test (i.e., UA)
283 Chemicals (Herbicides / Pesticides / Solvents)
284 Precursor Chemicals (For Making Drugs)
285 Medical / Medical Related Lab Equipment
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 91
290 Recordings - Audio / Visual (Phonograph records, compact disks, tape recordings, cassettes,
game software for gaming consoles, etc.)
321 Auto
322 Truck
323 Motorcycle / Moped
324 Snowmobile[s]
325 Bus Commercial
326 Vans Passenger Non-Commercial
327 Police Vehicle
328 Recreational Vehicle
329 Other - Go-Cart / Golf Cart / Motorized Wheel Chair, 4 Wheel ATV
330 Miscellaneous Vehicle[s] (Not applicable for Vehicle Theft)
331 Pocket Bike[s], Motorized Scooter[s], etc.
341 Aircraft (Airplanes, gliders, etc.)
342 Aircraft Parts / Accessories
350 Metals (Non-Precious i.e., Zinc, Tin, Lead, etc.)
351 Aluminum
352 Copper / Copper Alloys (Copper, Brass, Bronze)
353 Iron
354 Steel
360 Non-Alcoholic Beverages (Soft Drinks, Bottled Water, etc.)
361 Alcoholic Beverages (Liquor / Beer / Wine, etc.)
362 Food / Meat
363 Personal Hygiene Items
364 Gas /Fuel
365 Hay / Feed / Seed
366 Cigarettes / Tobacco
367 Drug / Narcotics
368 Utilities (Water, Electricity, Natural Gas, Cable TV, etc.)
369 Other Consumable
370 Fruits / Vegetables
500 Logging Equipment (Choker cables, chain binders, binders, blocks, etc.) DOES NOT INCLUDE
saws, tools, or other heavy machinery.
510 Timber / Raw Wood Products
520 Building Materials (Lumber, bricks, etc.)
590 Domestic Pets (Dogs, cats, birds, hamsters, etc.)
600 Saddles and Tack
610 Marine Equipment
701 Residence
702 Structure / Other Dwelling
703 Structure Other Commercial Business
704 Structure Industrial Manufacturing (Factories, plants, etc.)
705 Structure Public / Community (Hospital, jail, college, passenger terminal, church, sports arena,
etc.)
706 Structure - Storage (Barns, garages, storehouses, etc.)
709 Structure - Other
750 Miscellaneous
880 Unknown Property - Pending Inventory
990 Special category to be used by the NCIC UCR to compile statistics on certain types of property
Page 92 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
3.3 Value of Property
This element contains the total property value of each property description category submitted. If the property value is
unknown, an entry of $1 is submitted.
Format: 9 Numeric
Occurrences: 1/ Property Description Category
Mandatory: Conditional
Edits: 1) Must be numeric entry with zero left-fill if entered.
2) If value is unknown, must have value of "1" = Unknown ($1.00). A value of zero is allowable
only for property description codes of: "143" = Nonnegotiable Instruments, “144” = Mail
Documents, “146” = Personal Documents, "190" = Credit/Debit Cards, “195” = Personal
Identity Documents, “197” = Identity (intangible), "750" = Miscellaneous and "990" = ( special
category ).
3) If Property Description has a code of "143" = Nonnegotiable Instruments, “144” = Mail
Documents, “146” = Personal Documents, "190" = Credit/Debit Cards or “195” = Personal
Identity Documents or “197” = Identity (intangible) a zero value is required.
4) If Data Element 3.2 (Property Description) code is "367" = Drugs/Narcotics and the only
offense submitted is Drugs/Narcotic Violations, the property value must be blank. (Note that if
any offense other than 180 has a "367" = Drugs/Narcotics entry, the value for this property
must be entered.)
5) When Property Type Loss, etc. entries are made for both "7" = Stolen/Etc. and "5" =
Recovered, the recovered "property" cannot have property value(s) greater than
corresponding property value(s) reported stolen.
6) When Data Element 3.3 (Value of Property) contains a value that exceeds an assigned
threshold amount, a "warning" message will be created. The participant is asked to check to
see if the value entered was a data entry error, or if it was intended to be entered. A warning
message is always produced when the value is $1,000,000 or greater.
7) Only whole dollar amounts may be entered.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 93
3.4 Number of Property Items
This data element is used to report the number of property items totaled for each property description category. For
example, to report the number of stolen bicycles, you would submit a property segment with a Property Type Loss, etc. code
of 7. Then within that segment, you would enter the property description category, the value of the property, and then the
number of bicycles in the number of property items data element.
Format: 2 Numeric
Occurrences: 1/ Property Description Category
Mandatory: Conditional
Edits: Must be numeric entry of 01 - 99.
Page 94 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
3.5 Property Offense Code
The property offense code is the offense code related to the property being submitted.
Format: 3 Alpha Numeric
Occurrences: 1/ Property Description Category
Mandatory: Conditional
Edits: 1) The offense must be a valid offense code.
2) Each offense code entered must have a corresponding Offense Segment.
3) Required for all property offenses.
Data Values: See the section titled Offense Codes for a complete listing of valid offenses.
Note: This data element is used as a Foreign Key to allow a property search by offense category.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 95
3.6 Date Recovered
The date recovered field contains the date that property is reported as recovered. It is required when the Property Loss
Code is "Recovered". [Provided ONLY on recovered records, not on the stolen. On the Stolen Record, this field should be
left blank.]
Format: 8 character date in this format or blank YYYYMMDD
Occurrences: 1/ Property Description Category
Mandatory: Conditional
Edits: 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 (e.g., June cannot have 31 days).
2) Cannot be earlier than Data Element 3 (Incident Date/Hour).
3) If entered, then both Property Description and Value of Property must be entered.
4) If entered, Property Type Loss, etc. must be "5" = Recovered.
5) Follow NIBRS guidelines under 3.6 Recovered Date (page 34 in NIBRS Vol. 4) for specifics on
dates. For example, if Month and Year of the file are 012011, the recovered date cannot
contain any date 02/01/2011 or later.
Page 96 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
3.7 Suspected Drug Type
This data element is used to identify the types of drugs or narcotics that were seized in a drug case. An entry should not be
made when drugs were stolen, burned, etc., in connection with non-drug/narcotic violations.
You may enter up to three types of drugs/narcotics. If more than three types are involved, only the two most important (as
determined by the reporting agency) are submitted and “X” is entered as the third drug.
Next to each drug type data value is the category in which each of these drugs are counted.
Format: 1 Alpha
Occurrences: Up to 3/ Property Type Loss, etc.
Mandatory: Conditional
Edits: 1) Must be entered when there is a Drug Law Violations (180), "6" = Seized was entered into
Property Type Loss, etc., and "367" = Drugs/Narcotics was entered in Property Description.
If there are other offenses involved and "367" = Drugs/Narcotics was split between offense
Drug/Narcotic Violations and other offenses, only enter the drug types applicable to
Drug/Narcotic Violations.
2) If more than one code is entered, the same code cannot be entered within the same "Type
Measurement" category. In other words, cocaine cannot be reported in grams and pounds
(same weight category), but could be reported in grams and liters (mass and volume
categories).
3) Must be a valid code.
4) When the offense is Drug/Narcotic Violations and Property Type Loss (3.1), etc. is "1" = None,
[ONLY the] Suspected Drug Type is [required to be entered].
5) Follow NIBRS guidelines under Suspected Drug Type (approx. page 88 and 89 in NIBRS Vol.
1) for more detailed instruction on using code X.
Data Values: A "Crack" Cocaine (Narcotic)
B Cocaine (Narcotic)
C Hashish (Marijuana)
D Heroin (Narcotic)
E Marijuana (Marijuana)
F Morphine (Narcotic)
G Opium (Narcotic)
H Other Narcotics (Narcotic)
I LSD /Synthetic Drugs (Synthethic)
J PCP (Synthethic)
K Other Hallucinogens (Other)
L Amphetamines (Synthethic)
M Other Stimulants (Synthethic)
N Barbiturates (Narcotic)
O Other Depressants (Narcotic)
P Other Drugs (Other)
Q Methamphetamines (Synthethic)
U Unknown Type Drug (Other)
X Over 3 Drug Types
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 97
3.8 Estimated Drug Quantity and Fraction
This data element is used to indicate the quantity of drugs or narcotics seized in a drug case. The first nine digits represent
a whole number. The last three numbers represent the first three digits after the decimal point.
Format: 12 Numeric
Occurrences: 1/ Suspected Drug Type
Mandatory: Conditional, only when Property Type Loss (3.1) = Seized.
Edits: 1) Must be numeric entry with zero left-fill. The decimal fractional quantity, if entered, must be
expressed in thousandths as the last three digits.
2) If entered, Suspected Drug Type and TypeDrug Measurement must also be entered.
3) Follow NIBRS guidelines under Suspected Drug Type (page 88 and 89 in NIBRS Vol. 1) when
using X.
When reporting trace amounts of drugs, please use .001 (decimal) for the quantity/fraction and GM for the
measurement (3.9).
Page 98 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
3.9 Type of Drug Measurement
The type of measurement used to quantify drugs or narcotics is specified in this data element.
Format: 2 Alpha
Occurrences: 1/ Suspected Drug Type
Mandatory: Conditional, only when Property Type Loss (3.1) = Seized.
Edits: 1) Must be a valid code.
2) Based upon the various ways a drug can be measured, very few edits can check for illogical
combinations of drug type and measurement. The only restriction will be to limit "NP" =
Number of Plants to the following drugs: E = Marijuana, G = Opium, K = Other Hallucinogens.
All other "Type Drug Measurement" codes are applicable to any Suspected Drug Type code.
3 If entered, Suspected Drug Type and Estimated Drug Quantity must also be completed.
4) Estimated Quantity must have a value of "1" when "XX" = Not Reported is entered for Type
Measurement. Submission of a "Not Reported" indication requires that a value of "1" also be
submitted as a quality assurance measure. Once the Type Measurement has been
determined, a resubmission of the Incident Report would be done reflecting the completed
data.
Data Values: GM Gram
KG Kilogram
OZ Ounce
LB Pound
ML Milliliter
LT Liter
FO Fluid Ounce
GL Gallon
DU Dosage Units/ Items
NP Number of Plants
XX Not Reported
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 99
(Blank Page)
Page 100 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
VICTIM SEGMENT
4.1 Victim (Sequence) Number
The victim sequence number is an identifier for each victim involved in the incident. The numbers are assigned sequentially
from 001 to 999.
Format: 3 Numeric
Occurrences: Up to 999/ Incident
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be numeric entry (001 through 999) with zero left-fill.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 101
4.2a Victim Connected to Offense Code(s)
This field is used to connect the victim with the offenses listed in the incident. Each victim must be associated to at least one
offense. A maximum of ten offenses may be associated with each victim.
Each offense submitted must also be submitted in the Offense Segment.
Format: 3 Alpha Numeric
Occurrences: Up to 10/ Victim
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
3) If more than one code entered, cannot be a duplicate.
4) If the offense code is a "Crime Against Person," the Type of Victim must be "I" = Individual.
5) If the offense code is a "Crime Against Society," the Type of Victim must be "S" = Society.
6) If the offense code is a "Crime Against Property," the Type of Victim cannot be "S" = Society.
7) Each offense code entered must have a corresponding Offense Segment.
Data Values: See the section titled Offense Codes for a complete listing of valid offenses.
4.2b Victim Oregon Revised Statute
The Oregon Revised Statute associated with the UCR offense code. The first four characters are followed by the period and
then the last 3 characters (E.G. 0163.395). When the ORS is only 6 digits (which is the norm), the first character should be
padded with a zero.
Format: 8 Alpha/numeric (i.e., 123A.123)
Occurrences: 1/ Offense up to 10/victim
Mandatory: Yes
Page 102 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.3 Type of Victim
This code defines the type of victim being described. Victims can be defined as individuals, society, or business.
A victim type of L for Law Enforcement Officer is used to facilitate the collection of LEOKA data. All edits regarding
Individuals apply to Law Enforcement Officers. Additionally, Victim type L can only be used when the offense(s) is one of the
following: 011, 012, 013, 014, 041, 042, 043.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
Data Values: I Individual
B Business
F Financial Institution
G Government
L Law Enforcement Officer
R Religious/ Organization
S Society/ Public
O Other
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 103
4.4 Age (of Victim)
If the victim type was a person, his/her age is to be entered into this data element.
Format: 4 Alpha Numeric
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be present if Type of Victim is "I" = Individual or "L" = Law Enforcement Officer.
2) Type of Victim must be "I" = Individual or "L" = Law Enforcement Officer for data to be entered.
3) If Relationship of Victim to Offender contains a relationship of "SP" = Spouse, then the victim
cannot be less than 10 years old.
4) EXACT AGE:
A) Must be a valid code if alpha characters, i.e., NN, NB, or BB.
B) A single two-character age must be in first two positions of the field, not the
third and fourth.
5) AGE RANGE:
A) Must be four numeric digits.
B) First pair must be less than second pair.
C) The low age in a range cannot be "00" (unknown).
Data Values: NN Under 24 hours
NB 1 to 6 Days Old
BB 7 to 364 Days Old
01 to 98 Actual Years Old
99 [Over 98 Years Old 99 and over]
00 Unknown
Page 104 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.5 Sex (of Victim)
If the victim was a person, his/her sex is to be entered into this data element.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be present if Type of Victim is "I" = Individual or "L" = Law Enforcement Officer.
3) Type of Victim must be "I" = Individual or "L" = Law Enforcement Officer for data to be entered.
Data Values: F Female
M Male
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 105
4.6 Race (of Victim)
If the victim was a person, his/her race is to be entered into this data element.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be present if Type of Victim is "I" = Individual or "L" = Law Enforcement Officer.
3) Type of Victim must be "I" = Individual or "L" = Law Enforcement Officer for data to be entered.
Data Values: I American Indian/ Alaska Native
A Asian
B Black or African American
H Hispanic or Latino
P Native Hawaiian/Other Pacific Islander
W White
U Unknown
Page 106 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.7 Ethnicity (of Victim)
If the victim was a person, his/her ethnicity is to be entered into this data element.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be present if Type of Victim is "I" = Individual or "L" = Law Enforcement Officer.
3) Type of Victim must be "I" = Individual or "L" = Law Enforcement Officer for data to be entered.
Data Values: A Arab Origin
C Chinese Origin
H Hispanic or Latino Origin
J Japanese Origin
V Vietnamese Origin
[N Not Hispanic or Latino]
O Other/None Ethnic Origin
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 107
4.8 Resident Status (of Victim)
If the victim was a person, his/her resident status is to be entered into this data element. A "Resident" is a person who
maintains his/her permanent home for legal purposes in the locality where the crime took place.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be present if Type of Victim is "I" = Individual or "L" = Law Enforcement Officer.
2) Must be a valid code
Data Values: N Nonresident
R Resident
U Unknown
Page 108 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.9 Aggravated Assault/Homicide Circumstances
This data element is used to describe the circumstances of either an aggravated assault or a homicide.
Format: 2 Numeric
Occurrences: Up to 2/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) If more than one code entered within Aggravated Assault/Murder category, cannot be a
duplicate.
3) Can only be entered when one or more Victim Connected to Offense Codes entries are:
Murder (011 or 012), Negligent Manslaughter (013), Negligent Homicide - Traffic (014),
Justifiable Homicide (015), Aggravated Assault (041), Attempted Murder (042)
4) If "20" = Criminal Killed by Private Citizen or "21" = Criminal Killed by Police Officer is entered,
then Additional Justifiable Homicide Circumstances must be entered.
5) Value "10" = Unknown Circumstances is mutually exclusive with any other code -- no other
code can be entered. Enter "10" only if no other code applies.
6) No more than one circumstance category (i.e., Aggravated, Negligent, Justifiable) can be
entered.
7) When "08" = Other Felony Involved is entered, a minimum of two felony offenses should be
entered for Offense Code. When "08" is entered, it almost always involves multiple offenses.
In those instances where only one offense is submitted, a "warning" message will be
produced. When this situation is encountered, the participant should verify that the Incident
Report should only have one offense.
Data Values: For Aggravated Assault, Homicide and Attempted Murder
01 Argument
02 Assault on Law Enforcement Officer(s)
03 Drug Dealing
04 Gangland
05 Juvenile Gang
06 Lovers' Quarrel
07 Mercy Killing
08 Other Felony Involved
09 Other Circumstances
10 Unknown Circumstances
For Justifiable Homicide
20 Criminal Killed by Private Citizen
21 Criminal Killed by Police Officer
For Negligent Manslaughter and Negligent Homicide Traffic only
30 Child Playing With Weapon
31 Gun-Cleaning Accident
32 Hunting Accident
33 Other Negligent Weapon Handling
34 Other Negligent Killings
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 109
4.10 Additional Justifiable Homicide Circumstances
This data element is to be used to further describe the circumstances of a justifiable homicide.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) If it is entered, Aggravated Assault/Homicide Circumstances must show a "justifiable
homicide" circumstance, i.e., code "20" or "21."
Data Values: A Criminal Attacked Police Officer and Officer Killed Criminal
B Criminal Attacked Police Officer and Criminal Killed by Another Police Officer
C Criminal Attacked a Civilian
D Criminal Attempted Flight From a Crime
E Criminal Killed in Commission of a Crime
F Criminal Resisted Arrest
G Unable to Determine/ Not Enough Information
Page 110 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.11 Type of Injury
This data element is to be used to describe the type(s) of bodily injury suffered by a person. You may enter up to five entries
for each victim.
Format: 1 Alpha
Occurrences: Up to 5/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) If more than one code entered, cannot be a duplicate.
3) Value "N" = None is mutually exclusive with any other value entered, i.e., "N" is to be used
only if no other code applies.
4) Can only be entered when one or more Victim Connected to Offense Codes entries are:
[020 Forcible Rape
03X Robbery
041 Aggravated Assault
042 Attempted Murder
043 Simple Assault
177 Forcible Sodomy
17C Sexual Assault With An Object
173 Physical Molest/Forcible Fondling
230 Extortion/Blackmail
25X Kidnapping]
Data Values: B Apparent Broken Bones
I Possible Internal Injury
L Severe Laceration
M Apparent Minor Injury
N None
O Other Major Injury
T Loss of Teeth
U Unconsciousness
When offense is 043 – injury type can only be M or N.
[When offense is 048 – injury type must be blank.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 111
4.12 Related Offender(s)
This data element is to be used along with data element 4.13 to report the relationships of the victim to offenders who have
perpetrated a "Crime Against Person" or a Robbery against the victim.
Enter the offender sequence numbers of the offenders for whom victim-to-offender relationships are going to be reported in
data element 4.13. You may enter up to ten offender relationships for each victim.
Format: 2 Numeric
Occurrences: Up to 10/ Victim
Mandatory: Conditional
Edits: 1) Enter only if one or more of the offenses entered into Victim Connected to Offense
Code(s)(4.2) is a "Crime Against Person" or is a “Crime Against Property”. If more than 10
offenders satisfy this criteria, choose the 10 closest in relationship. For example, if 15
offenders were neighbors and one was the brother, enter the brother as one of the 10
offenders in this data element.
2) Data Element 25 (Type of Victim) must be "I" = Individual or "L" = Law Enforcement Officer for
data to be entered.
3) If more than one number entered, cannot be a duplicate.
4) "00" may only be entered if there is only one Offender Segment submitted where nothing was
known about identity and number of offender(s).
5) The corresponding Offender Segment must be present.
Page 112 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.13 Relationship(s) of Victim to Offender(s)
This data element is used to report the relationship of the victim to the associated offender in element 4.12.
Format: 2 Alpha
Occurrences: 1/ Related Offender
Mandatory: Conditional
Edits: 1) Every offender indicated in Related Offender requires an entry here except when the number
is "00" = Unknown. This field must be blank in instances when "00" is entered.
2) Must be a valid code.
3) Husbands and wives (i.e., spouses) must be at least 10 years of age.
4) The sex of the victim and/or offender must reflect the implied relationship. The following
relationships must reflect either the "Same" or "Different" sex codes depending upon this
relationship:
XS = Victim was Ex-Spouse Different
SE = Victim was Spouse Different
CS = Victim was Common-Law Spouse Different
BG = Victim was Boyfriend/Girlfriend Different
HR = Homosexual Relationship Same
5) The age of the victim and/or the offender must reflect the implied relationship. The following
relationships must be consistent with the victim's age in relation to the offender's age:
CH = Victim was Child Younger
PA = Victim was Parent Older
GP = Victim was Grandparent Older
GC = Victim was Grandchild Younger
6) Relationship cannot be entered when Offender Number to be Related is "00" = Unknown.
7) When "VO" = Victim Was Offender is entered, a minimum of 2 Victim and 2 Offender
Segments must be submitted. "VO" indicates situations such as brawls and domestic
disputes. In most of these cases, each victim is also the offender; therefore, every victim
record would contain a "VO" code. However, there may be some situations where only one of
the victims is also the offender, but where the other victim(s) are not also the offender(s). This
code can only be used when you have 2 PERSONS victims.
8) When entered, "VO" = Victim Was Offender can only be entered once in a victim record and
can refer to an offender only once. Since "VO" points to himself/herself, a victim cannot be
two offenders.
9) When the related offender has "unknown" values entered for age, sex, and race, the
relationship must be "RU" = Relationship Unknown. This edit ensures a logical relationship,
e.g., if brother was entered, age, sex, and race would not be unknown values.
Data Values: Within Family
SE Victim was Spouse
CS Victim was Common-Law Spouse
PA Victim was Parent
SB Victim was Sibling
CH Victim was Child
GP Victim was Grandparent
GC Victim was Grandchild
IL Victim was In-Law
SP Victim was Stepparent
SC Victim was Stepchild
SS Victim was Stepsibling
OF Victim was Other Family Member
(continued on next page)
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 113
Outside Family but Known to Victim
AQ Victim was Acquaintance
FR Victim was Friend
NE Victim was Neighbor
BE Victim was Babysittee (The baby/child being cared for)
BG Victim was Boyfriend/ Girlfriend
CF Victim was Child of Boyfriend or Girlfriend
HR Homosexual Relationship
XS Victim was Ex-Spouse
EE Victim was Employee
ER Victim was Employer
OK Victim was Otherwise Known
Not Known by Victim
RU Relationship Unknown
ST Victim was Stranger
Other Type of Relationship
VO Victim was Offender
Page 114 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.14 LEOKA Type of Act
This data element indicates whether the act was felonious or by accident or negligence. This value is only valid when the
type of victim is L.
Format: 1 Alpha
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be present if victim type is “L” - Law Enforcement Officer
Data Values: Default value = “N”
A Law Enforcement Official Assaulted
F Law Enforcement Official Killed (Felonious Act)
N Not LEOKA Incident
O Law Enforcement Official Killed (Acc./ Neglig./Other)
Note: To use the LEOKA data elements of the victim record, the offense(s) must be one of the following:
011, 012, 013, 014, 041, 042, 043
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 115
4.15 LEOKA Assignment Type
This data element is used to report the type of assignment the officer was on when the assault occurred. This value is only
valid when the type of victim is L. If this is not a LEOKA incident, this field should be left blank.
Format: 2 Numeric
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be provided if the victim type is Law Enforcement Officer.
Data Values: 01 Two Officer Vehicle,
02 Alone in One Officer Vehicle
03 Assisted in One Officer Vehicle
04 Detective/Special Assign. (Alone)
05 Detective/Special Assign (Assisted)
06 Other (Alone)
07 Other (Assisted)
Page 116 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
4.16 LEOKA Activity Type
This data element is used to capture the description of what activity the officer was involved in when the assault occurred.
This value is only valid when the type of victim is L. If this is not a LEOKA incident, this field should be left blank.
Format: 2 Numeric
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be present if the victim type is Law Enforcement Officer.
Data Values: 01 Responding to Domestic Disturbance
02 Responding to Disturbance Other
03 Burglary in Progress/Pursuing Burglary Suspects
04 Robbery in Progress/Pursuing Robbery Suspects
05 Attempting Other Arrests
06 Civil Disorder (Riot, Mass Disobedience)
07 Handling,Transporting,Custody of Prisoners
08 Investigating Suspicious Persons or Circumstances
09 Ambush/ No Warning
10 Mentally Deranged
11 Traffic Pursuits and Stops
12 All Other
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 117
4.17 LEOKA ORI-Other Officer Jurisdiction
This is the ORI for officers from another jurisdiction who are killed or assaulted [outside of their own jurisdiction while
assisting another agency].
Format: 6 Numeric
Occurrences: 1/ Victim
Mandatory: Conditional
Edits: Must be a valid code.
Page 118 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
OFFENDER SEGMENT
5.1 Offender (Sequence) Number
The offender sequence number is an identifier for each offender involved in the incident. The numbers are assigned
sequentially from 01 to 99.
The purpose of the field is to distinguish one offender from another and to identify the situation where nothing was known
about the number of offenders or who they were. For example, a corpse was found in a ditch and there were no
eyewitnesses or other information that would provide data about possible offenders. In that case, "00" = Unknown would be
entered. However, if five offenders were seen running from the scene, then five offender records would be submitted.
Format: 2 Numeric
Occurrences: Up to 99/ Incident
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) If the incident is exceptionally cleared, then "00" cannot be entered. "00" indicates that
nothing was known about the offender(s) regarding number and any identifying information.
One of the criteria for exceptionally clearing an incident is that at least one of the offenders be
known.
3) For a Justifiable Homicide, at least one of the offenders must have "known" information for
Age, Sex, and Race. Consequently, "00" is not valid as an offender sequence number.
4) If the number is "00" = Unknown, no other Offender Segments can be submitted.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 119
5.2 Age (of Offender)
The age of the offender is to be entered as an exact number of years, a range of years, or as unknown.
Format: 4 Alpha Numeric
Occurrences: 1/ Offender
Mandatory: Conditional
Edits: 1) Must be present when Offender Sequence Number is other than "00" = Unknown.
2) Cannot be entered when Offender Sequence Number is "00" = Unknown.
3) When an incident is cleared exceptionally, at least one of the offenders must have "known"
values in Age, Sex, and Race.
4) For a Justifiable Homicide (015), at least one of the offenders must have "known" information
for Age, Sex, and Race.
5) If Relationship of Victim to Offender contains a relationship of "SP" = Spouse, then the
offender cannot be less than 10 years old.
6) Exact Age:
A) Must contain numeric entry of 00 – 99, or NN, NB or BB.
B) A numeric age must be in first two positions of the field, not the third and fourth.
7) Age Range:
A) Must be four numeric digits.
B) First pair must be less than second pair.
C) The low age in a range cannot be "00" (unknown).
D) Cannot contain NN, NB or BB.
Data Values: NN Under 24 hours
NB 1 to 6 Days Old
BB 7 to 364 Days Old
01 to 98 Actual Years Old
99 [Over 98 Years Old 99 and over]
00 Unknown
Caveat: If codes of NN, NB or BB are entered (as in a protective custody), OUCR will convert age of offender
to 01 prior to submitting to the FBI.
Page 120 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
5.3 Sex (of Offender)
The sex of the offender is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Offender
Mandatory: Conditional
Edits: 1) Must be present when Offender Sequence Number is other than "00" = Unknown.
2) Must be a valid code.
3) Cannot be entered when Offender Sequence Number is "00" = Unknown.
4) When an incident is cleared exceptionally, at least one of the offenders must have "known"
values in Age, Sex, and Race.
5) For a Justifiable Homicide , at least one of the offenders must have "known" information for
Age, Sex, and Race.
Data Values: F Female
M Male
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 121
5.4 Race (of Offender)
The race of the offender is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Offender
Mandatory: Conditional
Edits: 1) Must be present when Offender Sequence Number is other than "00" = Unknown.
2) Must be a valid code.
3) Cannot be entered when Offender Sequence Number is "00" = Unknown.
4) When an incident is cleared exceptionally, at least one of the offenders must have "known"
values in Age, Sex, and Race.
5) For a Justifiable Homicide, at least one of the offenders must have "known" information for
Age, Sex, and Race.
Data Values: I American Indian/ Alaska Native
A Asian
B Black or African American
H Hispanic or Latino
P Native Hawaiian/Other Pacific Islander
W White
U Unknown
Page 122 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
5.5 Ethnicity (of Offender)
The ethnicity of the offender is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Conditional
Edits: 1) Must be present when Offender Sequence Number is other than "00" = Unknown.
2) Must be a valid code.
3) Cannot be entered when Offender Sequence Number is "00" = Unknown.
4) When an incident is cleared exceptionally, at least one of the offenders must have "known"
values in Age, Sex, and Race.
5) For a Justifiable Homicide, at least one of the offenders must have "known" information for
Age, Sex, and Race.
Data Values: A Arab Origin
C Chinese Origin
H Hispanic or Latino Origin
J Japanese Origin
V Vietnamese Origin
[N Not Hispanic or Latino]
O Other/None Ethnic Origin
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 123
(Blank Page)
Page 124 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
ARRESTEE SEGMENT
6.1 Arrestee (Sequence) Number
The arrestee sequence number is an identifier for each arrestee involved in the incident. The numbers are assigned [to
match up with the corresponding offender sequence number, sequentially numbers can range] from 01 to 99.
Format: 2 Numeric
Occurrences: Up to 99/ Incident
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be numeric entry of 01 to 99.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 125
6.2 Arrest (Transaction) Number
This number is assigned by the submitting agency to uniquely identify the arrest report. It may be the "Incident Number"
related to the arrest, however if more than one arrestee each must be unique.
Format: 12 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must uniquely identify the arrestee.
3) Must be left-justified with blank right-fill if under 8 characters in length.
4) Valid character combinations can include A through Z, 0 through 9 and – (hyphen). For
example, 11-123SC is valid, but, 11+123*SC is invalid.
5) Must be blank right-fill if under 12 characters in length. Cannot have embedded "blanks"
between the first and last character entered.
Page 126 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.3 Arrest Date
This data element is to be used to indicate the date the arrest took place. The date value should be entered as
YYYYMMDD.
Format: 8 Numeric / YYYYMMDD
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) 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 date cannot exceed the
current date.
3) Cannot be earlier than Incident Date/Hour.
4) Follow NIBRS guidelines under 3.6 Recovered Date (page 34 in NIBRS Vol. 4) for specifics on
dates. For example, if Month and Year of the File are 012011, the recovered date cannot
contain any date 02/01/2011 or later.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 127
6.4 Type of Arrest
This data element is used to indicate the type of apprehension.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
Data Values: O On-View Arrest (within your jurisdiction)
S Summoned/ Cited (cited and released)
T Taken Into Custody ( warrant service)
Page 128 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.5 Multiple Clearance Indicator
This data element is used to indicate whether or not the apprehension of the arrestee resulted in the clearance of more than
one previously reported incident within the jurisdiction served by the reporting agency.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
Data Values: C Count Arrestee for First Case Cleared
M Multiple Cases Cleared
N Not a Multiple Clearance Situation
Multiple Clearance Indicator is to be used to ensure that an arrestee is counted only once when the arrestee’s apprehension causes the
arresting agency to submit two or more Arrestee Segments concerning separate Incident Reports. In such a situation, C – Count
Arrestee is to be entered into one of the Arrestee Segments and M – Multiple is to be entered into all of the remaining Arrestee
Segments.
If the arrestee’s apprehension does not cause the arresting agency to submit multiple Arrestee Segments, enter an N – Not Applicable.
Example (1): The arrestee’s apprehension for robbery resulted in his identification as the perpetrator of five additional robberies within
the arresting agency’s jurisdiction. Six (6) Arrestee Segments should be submitted, e.g., one for each Incident report. One (1) should
have C – Count Arrestee entered into this field and five (5) should have M – Multiple entered.
Example (2): The arrestee’s apprehension resulted in the arresting agency submitting only one (1) Arrestee Segment. N – Not
Applicable should be entered.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 129
6.6 Arrest Offense Code
The offense code(s) for which the arrestee was apprehended is to be entered into this data element. If the arrestee was
apprehended for more than five offenses within a single incident, the reporting agency is to determine which were the most
serious offenses and enter them as the arrest offenses.
Format: 3 Alpha Numeric
Occurrences: Up to 5/ Arrestee
Mandatory: Yes
Edits: 1) Conditionally (1st entry must be present).
2) Must be a valid offense code.
3) The Arrest Offense Code cannot be Justifiable Homicide, because this offense does not result
in a subsequent arrest of the offender.
4) When the arrest offense is a Group A offense, then a group A incident offense must be
present in the offense segment.
Data Values: See the section titled Offense Codes for a complete listing of valid offenses.
Only the arrest for the most serious offense is forwarded to the National NIBRS program.
Page 130 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.7 Arrestee Was Armed With
This data element is to be used to indicate whether the arrestee was armed with a weapon at the time of his/her
apprehension.
Format: 3 Alpha Numeric
Occurrences: Up to 2/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
3) If more than one code entered, cannot be a duplicate.
4) Value "01" = Unarmed is mutually exclusive with any other value, i.e., it is to be used only if
no other code applies.
5) The third character must be "A" = Automatic or blank.
6) If the firearm is Automatic, add "A" as the third character of code; valid only with codes: "11" =
Firearm (Type Not Stated), "12" = Handgun, "13" = Rifle, "14" = Shotgun, "15" = Other
Firearm.
Data Values: 01 Unarmed
11 Firearm (type not stated)
12 Handgun
13 Rifle
14 Shotgun
15 Other Firearm
16 Lethal Cutting Instrument (i.e., switchblade knife, martial arts "stars," etc.)
17 Club/ Blackjack/ Brass Knuckles
18 Taser
19 Chemicals
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 131
6.8 Date of Birth (of Arrestee)
This data element is used to capture the arrestee's date of birth. If the exact date is unknown, then enter the approximate
age in the Age of Arrestee field, and leave the Date of Birth field empty.
Format: 8 Alpha Numeric / YYYYMMDD
Occurrences: 1/ Arrestee
Mandatory: Yes, if known, must be entered
Edits: 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 (e.g., June cannot have 31 days). The date cannot exceed the
current date. The DOB must be greater than 01/01/1900.
2) If unknown, leave the value blank.
Page 132 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.9 Age (of Arrestee)
The age of the arrestee is to be entered as an exact number of years, a range of years.
Format: 4 Alpha Numeric
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) EXACT AGE:
A) Must contain numeric entry of 01 – 99, or NN, NB or BB.
B) A single two-character age must be in first two positions of the field, not the third and
fourth.
3) AGE RANGE:
A) Must be four numeric digits.
B) First pair must be less than second pair.
C) Cannot contain NN, NB or BB.
Data Values: NN Under 24 hours
NB 1 to 6 Days Old
BB 7 to 364 Days Old
01 to 98 Actual Years Old
99 [Over 98 Years Old 99 and over]
00 Unknown
Caveat: If codes of NN, NB or BB are entered (as in a protective custody), OUCR will convert age of arrestee to
01 prior to submitting to the FBI.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 133
6.10 Sex (of Arrestee)
The sex of the arrestee is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code. Although "U" = Unknown is a valid code for victim and offender sex, it is
not valid for arrestees.
Data Values: F Female
M Male
Page 134 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.11 Race (of Arrestee)
The race of the arrestee is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
Data Values: I American Indian/ Alaska Native
A Asian
B Black or African American
H Hispanic or Latino
P Native Hawaiian/Other Pacific Islander
W White
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 135
6.12 Ethnicity (of Arrestee)
The ethnicity of the arrestee is to be indicated in this data element.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes
Edits: If entered, it must be a valid code.
Data Values: A Arab Origin
C Chinese Origin
H Hispanic or Latino Origin
J Japanese Origin
V Vietnamese Origin
[N Not Hispanic or Latino]
O Other/None Ethnic Origin
U Unknown
Page 136 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.13 Resident Status (of Arrestee)
The resident status of the arrestee is to be entered into this data element. A "Resident" is a person who maintains his/her
permanent home for legal purposes in the locality where the crime took place.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Yes, must be entered
Edits: Must be a valid code
Data Values: N Nonresident
R Resident
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 137
6.14 Disposition of Arrestee Under 18
This data element is to be used only if the arrestee was 17 years of age or younger at the time of the arrest. It is used to
indicate what action was taken regarding the juvenile.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must be entered if arrestee age is under 18.
3) Cannot be entered if arrestee age is over 17.
4) If not entered but Age of Arrestee reflected an age-range for a juvenile, a warning message
will be generated. This only happens when the low age is a juvenile and the high age is an
adult, but the average age is a juvenile.
Data Values: H Handled Within Department (released to parents, released with warning, etc.)
R Referred to Other Agency (turned over to juvenile court, probation department, welfare
agency, other police agency, criminal or adult court, etc.)
Page 138 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.15 Drug Codes
This data element is used to identify the types of drugs or narcotics that the arrestee possessed when apprehended.
You may enter up to three types of drugs/narcotics. If more than three types of drugs are involved, then the two most
important or significant are reported and “X” is entered as the third.
For a list of the categories for the drug, please refer to section 3.7.
Format: 1 Alpha
Occurrences: Up to 3/ Arrestee
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) Must have an offense code of 180.
Data Values: A "Crack" Cocaine
B Cocaine (all forms except “crack”)
C Hashish
D Heroin
E Marijuana
F Morphine
G Opium
H Other Narcotics: Codeine; Demerol; Dihydromorphinone or
Dilaudid; Hydrocodone or Percodan; Methadone; etc.
I LSD / Synthetic Drugs
J PCP
K Other Hallucinogens: BMAD or “White Acid”; DMT; MAD; DMAD; Mescaline or Peyote;
Psilocybin; STP; Etc.
L Amphetamines
M Other Stimulants Adipex, Fastine, and Ionamin
(Derivatives of Phentermine); Benzedrine; Didrex;
Methylphenidate or Ritalin; Phenmetrizine or Preludin/ Tenuate; etc.
N Barbiturates
O Other Depressants: Glutethimide or Doriden; Methaqualone
or Quaalude; Pentazocine or Talwin; etd.
P Other Drugs: Antidepressents (Elavil, Triavil, Tofranil, etc.)
Aromatic Hydrocarbons; Propoxyphene or Darvon; Tranquilizers
(Chlordiazepoxide or Librium, Diazepan or Valium, etc.) etc.
Q Methamphetamines
U Unknown Type Drug
X Over 3 drug types. See NIBRS Vol. 4, Pages 37 & 38 for more detailed instruction on using
this code.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 139
6.16 DUII Intoxicant Type
The DUII Intoxicant Type is a code that is used if the arrestee was arrested for a DUII offense. The code describes the type
of intoxicants that influenced the arrestee.
Format: 1 Alpha
Occurrences: 1/ Arrestee
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) The offense code must be a DUII offense (210).
Data Values: A Alcohol
[C Combination]
D Drugs
U Undetermined
Page 140 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
6.17 Breath Analyzer Results
The Breath Analyzer Results code is required if the DUII Intoxicant Type (6.16) indicates the influence of alcohol. The
results field is used to record the alcohol level of the individual arrested for a DUII offense.
Format: 2 Alpha Numeric
Occurrences: 1/ Arrestee
Mandatory: Conditional
Edits: 1) Must be a valid code.
2) The offense code must be a DUII offense (210).
3) The DUII Intoxicant Type (6.16) must be an A [or C].
Data Values: 08 Under .08
14 .08 - .14
19 .15 - .19
99 .20 and Above
RE Test was Refused
NG Test was Not Given
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 141
(Blank Page)
Page 142 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
INDIVIDUAL SEGMENT
I.1 Individual Type
The Individual Type describes how the person or entity being described was involved in the incident. It is used in
conjunction with the individual sequence as a unique identifier within the incident. For example, if we were submitting
information on an Arrestee, the code A would be entered.
Format: 1 Alpha
Occurrences: 1/person segment (Victim, Offender, Arrestee)
Mandatory: Yes
Edits: 1) Must be present -- cannot be blank.
2) Must be a valid code.
Data Values: A Arrestee
C Complainant: The person who reported the criminal incident to police. For example, a woman
hears another woman screaming from a park across the street and sees a man chasing her. The
woman calls police to report the incident. Upon arrival, police find that the other woman had been
assaulted by the man. The woman who called the police on behalf of the other woman is identified
as the “Complainant” in this incident. When the victim of a crime is the person who reports it to
police, that person is referred to as “Victim” rather than “Complainant”.
L Law Enforcement (used only for homicide & assault offenses when entering LEOKA data)
M Other Mentioned: Someone other than those that fit in the other categories.
[O] Offender: The person who committed an offense. Often the person who has committed a criminal
offense is unknown. What is known is that someone had to have committed the crime, so there is
always at least 1 offender for every incident. What distinguishes an Offender from a Suspect is that
there is certainty, or near-certainty that a specific person (the Offender) committed the offense.
Evidence or the subject’s confession removes doubt as to what part the person played in the
incident. For example, witnesses identified an individual as having pulled a gun from his coat and
shooting the victim. A search of the subject reveals that he does, in fact, have a gun that has
recently been fired. And, he gives a statement that he did shoot the victim.
P Person of Interest: This person may play one of many roles in an incident. For example, as police
respond to a report of a bank robbery, a subject known by police as being involved in previous
criminal activity is seen about 2 blocks from the bank walking away from the area. It is unknown if
this person has had any involvement in the bank robbery, but his presence is a curiosity that should
be investigated. A Person of Interest may have no direct connection to a criminal incident, but may
have information about people who are involved that could be beneficial to investigators. For
example, an acquaintance of a subject suspected of arson may be able to lead investigators to
where the subject may be hiding.
S Suspect: Something leads investigators or the victim to think that a specific person committed the
criminal offense, but don’t (yet) have enough evidence to prove it. For example, a man tells police
that yesterday he got into an argument with his next door neighbor over the neighbor riding his very
loud motorcycle late into the evening every night. Today the man’s car was vandalized by someone
removing the muffler. Although the man has no proof of who actually damaged the car, he thinks it
was probably his neighbor because of their previous argument.
V Victim
W Witness
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 143
I.2 Individual (Sequence) Number
This number along with the Individual Type is used to uniquely identify the individual being described in this segment.
Format: 3 Numeric
Occurrences: Up to 999/Victim Individual Types
Up to 99/Other Individual Types
Mandatory: Yes
Edits: Must be present -- cannot be blank.
Note: The Individual number must correspond to the sequence number from the victim, arrestee, offender segments,
identifying the same individual. i.e., Offender 01 should be O001 on the individual segment.
Page 144 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.3 Name
This data element is used to record the names of individuals or organizations involved in this incident. All names entered
should be as complete as possible and in Last Name, First Name [Middle Name or Initial] format. Reference the NCIC
manual for further information.
Format: 30 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes
Example: Jones, John E. [or Jones, John Edward]
NOTE: When name is unknown, use reference to individual type, i.e., suspect, offender, witness
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 145
I.4 Date of Birth (of Individual)
If the date of birth of the individual is known it should be submitted in this data element . Otherwise, it should be left blank.
Format: 8 character date in this format or blank YYYYMMDD
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: 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 date cannot exceed the current date. The DOB must be
greater than 01/01/1900.
Page 146 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.5 Age (of Individual)
The age of the individual is entered into this data element .
Format:4 Alpha Numeric
Occurrences:1/ Individual Type & Individual Number
Mandatory: Yes[, if known, must be entered]
Edits: 1) EXACT AGE:
A) Must be a valid code if alpha characters, i.e., NN, NB, or BB.
B) A single two-character age must be in first two positions of the field, not the third and fourth.
2) AGE RANGE:
A) Must be four numeric digits.
B) First pair must be less than second pair.
C) The low age in a range cannot be "00" (unknown).
3) Arrestees and offenders cannot [submit be] NN, NB, or BB [except when offense is 511.]
Data Values:NN Under 24 hours
NB 1 to 6 Days Old
BB 7 to 364 Days Old
01 to 98 Years Old
99 [Over 98 Years Old 99 and over]
00 Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 147
I.6 Sex (of Individual)
The sex of the individual is entered into this data element .
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes[, if known, must be entered]
Edits: Must be a valid code [if not blank].
Data Values: F Female
M Male
U Unknown
Page 148 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.7 Race (of Individual)
The race of the individual is entered into this data element .
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes[, if known, must be entered]
Edits: Must be a valid code [if not blank].
Data Values: I American Indian/ Alaska Native
A Asian
B Black or African American
H Hispanic or Latino
P Native Hawaiian/Other Pacific Islander
W White
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 149
I.8 Ethnicity (of Individual)
The ethnicity of the individual is entered into this data element .
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes[, if known, must be entered]
Edits: Must be a valid code [if not blank].
Data Values: A Arab Origin
C Chinese Origin
H Hispanic or Latino Origin
J Japanese Origin
V Vietnamese Origin
[N Not Hispanic or Latino]
O Other/None Ethnic Origin
U Unknown
Page 150 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.9 Resident Status (of Individual)
The resident status of the individual is entered into this data element. A "Resident" is a person who maintains his/her
permanent home for legal purposes in the locality where the crime took place.
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes[, if known, must be entered]
Edits: Must be a valid code [if not blank].
Data Values: N Nonresident
R Resident
U Unknown
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 151
I.10 Hair Color
The hair color code of the individual entered into this data element. Reference the NCIC manual for further information.
Format: 3 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code if not blank.
Data Values: Refer to the NCIC manual for current listing
Page 152 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.11 Eye Color
The eye color code of the individual is entered into this data element. Reference the NCIC manual for further information.
Format: 3 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code if not blank.
Data Values: Refer to the NCIC manual for current listing.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 153
I.12 Skin Color
The skin color of the individual is entered into this data element. Reference the NCIC manual for further information.
Format: 3 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code if not blank.
Data Values: Refer to the NCIC manual for current listing.
Page 154 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.13 Height
The height of the individual in feet and inches is entered into this data element. Reference the NCIC manual for further
information.
Format: 3 Numeric
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: First digit represents feet, last two represent inches. Therefore the last two digits must be within the
range 0 - 11.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 155
I.14 Weight
The weight of the individual in pounds is entered into this data element. Reference the NCIC manual for further information.
Format: 3 Numeric
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Page 156 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.15 Scars, Marks, Tattoos
Any description of scars, distinguishing marks, or tattoos for the individual are entered into this data element. Reference the
NCIC manual for further information.
Format: 10 Alpha Numeric
Occurrences: 3/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Data Values: Refer to the NCIC manual for current listing.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 157
I.16 Gang Affiliation Code
This code is used to associate the individual with a list of known gangs. It should indicate the individual's affiliation
regardless of the activity surrounding the incident.
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code if not blank.
Data Values: A Crip
B Blood
C Skinhead
D Asian
E Hispanic or Latino
M Motorcycle
N None
O Other or Unknown
Page 158 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.17 Corrections Indicator
The corrections indicator field stores information related to the status of the individual at the time of the incident.
Format: 1 Alpha Numeric
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code if not blank.
Data Values: 1 Parole
2 Probation
3 Work Release
4 Incarcerated
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 159
I.18 Registered Sex Offender Flag
This data element specifies whether or not the individual is a registered sex offender.
Format: 1 Alpha
Occurrences: 1/ Individual Type & Individual Number
Mandatory: Dependent. Mandatory when individual type = A.
Data values: Y = Yes
N = No
U = Unknown
Page 160 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
I.19 Alias
[Alias (Also Known As) An alias includes any name in which any last, first, or middle name is
different from that in the Name Field for the record, i.e., Name/Smith, Michael Lee and Alias/Smith,
Lee Michael.]
Format: 30 Alpha Numeric
Occurrences: Up to 9/ Individual Type & Individual Number
Mandatory: Yes, if known, must be entered
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 161
(Blank Page)
Page 162 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
INDIVIDUAL SUPPLEMENTAL SEGMENT
H.1 Individual Address
This data element is used to capture the address where the individual lives.
Format: 30 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes, if known, must be entered
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 163
H.2 Individual City
This data element is used to capture the city of the address where the individual lives.
Format: 15 Alpha Numeric
Occurrences: 1/ Incident
Mandatory: Yes, if known, must be entered
Page 164 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
H.3 Individual State
This data element is used to capture the state of the address where the individual lives.
Format: 2 Alpha
Occurrences: 1/ Incident
Mandatory: Yes, if known, must be entered, default = OR
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 165
H.4 Individual Zip Code
This data element is used to capture the zip code of the address where the individual lives. The zip code plus the four digit
extension may be entered.
Format: 10 Alpha/Numeric
Occurrences: 1/ Incident
Mandatory: Yes, if known, must be entered Example: 97304-0000
Page 166 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
H.5 Individual Telephone Number
Format: 10 Numeric
Occurrences: 3/ Submission
Mandatory: Yes, if known, must be entered
Example: 5033783057 Area code/prefix/phone number
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 167
H.6 Individual Occupation
Format: 25 Alpha
Occurrences: 1/ Submission
Mandatory: Yes, if known, must be entered
Edits: 1) Free text.
2) If possible, select from table prior to using free text.
Recommended
Data Values:
Auto Sales/[SVC Service] Lawyer/Judge
Bank/Finance LE Corrections
Cashie70 LE Deputy
Clergy LE Dispatch
Clerk/Aide LE Police
Computers LE Trooper
Construct-Genl Legislator
Construct-Hwy Manager
Cook Medic/EMT
Day Care Military
Doctor Nurse
Driver-Delivery [Other]
Driver-Sch Bus Oth[er] Health Care
Driver-Taxi Oth[er] Restaurant
Driver-Transit Parole/Probat
Driver-Truck Postal Worker
Elected Office Public Service
Farm/Dairy Real Estate
Fire Fighter Retail
Fisherman Retired
Forester/Logger Social Worker
Foster Care-Ad Student
Foster Care-Juv Teacher-College
General Office Teacher-Elem
Heavy Equipment Teacher-HS
Homemaker Unemployed
Janitor/Refuse Wait Person
Landscaper
Page 168 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
H.7 Personal Identification Number
Format: 15 Alpha/Numeric
Occurrences: 3/ Submission
Mandatory: Yes, if known, must be entered
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 169
H.8 Personal Identification Type
Format: 1 Alpha
Occurrences: 3/ Submission
Mandatory: Yes, if known, must be entered
Edits: 1) Must be present if Personal Identificaition Number is submitted
2) Must be a valid code
Data Values: B FBI Number
D Driver License Number
F Finger Print Number (FPN)
I Identification Card
N Social Security Number
S State Identification (SID) Number
O Other
Page 170 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
H.9 Personal Identification Issuing Authority
This data element identifies the organization that has authority of the identifier assigned to the person.
Format: 15 Alpha
Occurrences: 3/ Submission
Mandatory: Conditional
Edits: 1) Must be present if Personal Identificaition Number is submitted
2) If issuing authority is a State or Country, must be valid NCIC code. State codes will be the
standard 2 digit [code when using codes D, I or S].
3) If Personal Identification Type = “O”, may be free text
4) If Personal Identification Type = “N”, Social Security Number, entry must be SOC.
5) If Personal Identification Type = “B”, FBI Number, entry must be FBI.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 171
H.10 Citizenship
This data element identifies the country that assigns rights, duties and privileges to the person due to the person’s birth or
naturalization in that country.
Format: 2 Alpha
Occurrences: 1/ Individual
Mandatory: Yes, if known, must be entered
Data Values: Must be valid NCIC code from State and Country Data Codes, Section 7 of the NCIC code
manual.
Page 172 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
H.11 Individual Country Code
This data element identifies the country where the individual resides.
Format: 2 Alpha
Occurrences: 1/ Submission
Mandatory: Yes, if known, must be entered
Data Values: Must be valid NCIC code from State and Country Data Codes, Section 7 of the NCIC code
manual.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 173
(Blank Page)
Page 174 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
VEHICLE SEGMENT
ALL VEHICLE CODES USED IN THIS SEGMENT MUST BE OBTAINED FROM THE NCIC CODE MANUAL
Vehicle segment can be included for any incident where a vehicle is stolen, recovered, used or is of interest.
It is not limited only to stolen/recovered vehicle incidents.
V.1 Vehicle (Sequence) Number
This number is used to uniquely identify the VEHICLE being described in this segment. Only one vehicle record should be
submitted for each vehicle involved.
Format: 2 Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes
Edits: Must be a numeric value from 01 to 99.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 175
V.2 License Number
This data element contains the registered plate number of the vehicle.
Format: 8 Alpha Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Page 176 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.3 License State
This data element contains the state the vehicle is licensed in.
Format: 2 Alpha
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid two digit NCIC state code.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 177
V.4 License Year
This data element contains the year the vehicle licensed expires.
Format: 4 Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Page 178 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.5 License Type
This data element contains the type of vehicle license acquired.
Format: 2 Alpha
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid NCIC code
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 179
V.6 Vehicle Identification Number
The VIN is the vehicle's unique serial number.
Format: 20 Alpha Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Page 180 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.7 Vehicle Year
This data element contains the model year of the vehicle.
Format: 4 Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 181
V.8 Vehicle Make
This data element is used to describe the make of the vehicle. Reference the NCIC manual for further information.
Format: 4 Alpha Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid NCIC code.
Page 182 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.9 Vehicle Model
This data element is used to describe the model of the vehicle. Reference the NCIC manual for further information.
Format: 3 Alpha Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid NCIC code
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 183
V.10 Vehicle Style
This data element is used to describe the style of the body of the vehicle. Reference the NCIC manual for further
information.
Format: 2 Alpha Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid NCIC code
Page 184 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.11 Vehicle Color
This data element is used to describe the color of the vehicle. Two colors may be submitted for those cases where it is more
appropriate to use more than one color to describe a vehicle. Reference the NCIC manual for further information.
Format: 7 Alpha Numeric – 3 alpha “/” 3 alpha, an example would be DBL/WHI
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid NCIC code
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 185
V.12 Vehicle Type
This data element contains the type code of the vehicle. The type codes specify general categories of vehicles like trucks,
cars, and motorcycles.
Format: 3 Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code.
Data Values: 321 Auto
322 Truck
323 Motorcycle /Moped
324 Snowmobile
325 Bus Commercial
326 Vans Passenger Non-Commercial
327 Police Vehicle
328 Recreational Vehicle
329 Other - Go-Cart /Golf Cart
330 Miscellaneous Vehicles
331 Motorized scooters, pocketbikes, etc.
341 Aircraft (Airplanes, gliders, etc.)
Page 186 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
V.13 Recovered Vehicle Condition
This code table describes the condition that the [vehicle property] was in when it was stolen or recovered.
Format: 1 Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code.
Data Values: 1 Submerged
2 Burned
3 Stripped
4 Dismantled
5 Stripped/Burned
6 No damage
[7 Damaged
8 Crashed]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 187
V.14 Vehicle Involvement Code
This code describes the vehicle’s involvement in the incident.
Format: 1 Alpha/Numeric
Occurrences: 1/ Vehicle
Mandatory: Yes, if known, must be entered
Edits: Must be a valid code.
Data Values: 1 Unknown
2 Other
3 Witness Vehicle
4 Used As Weapon
5 Used To Commit Crime
6 Suspect Vehicle
7 Victim Vehicle
8 Stolen
9 Recovered
A Stolen & Recovered
Page 188 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
ZERO REPORTING SEGMENT
0.1 Incident Number
This data value is part of the zero reporting segment and must contain all zeros.
Format: 12 zeros \Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Edits: Must be 12 zeros.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 189
0.2 Zero Report Month
This data value is part of the zero reporting segment.
Format: 2 Numeric
Occurrences: 1/ Submission
Mandatory: Yes
Edits: Must be a valid month code from 01 to 12.
Page 190 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
0.3 Zero Report Year
This data value is part of the zero reporting segment.
Format: 4 Numeric / YYYY
Occurrences: 1/ Submission
Mandatory: Yes
Edits: Must be a valid year (> 1992)
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 191
(Blank page)
Page 192 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
NARRATIVE SEGMENT
N.1 Narrative
The Narrative provides a brief summary of details pertaining to the incident. In bias crime incidents, include enough detail to
show offender’s actions were motivated by a bias against victim(s). Simply stating that victim and offender are of different
races, or that a slur of some kind was spoken does not satisfy the bias crime requirement.
Format: 10,000 Alpha / Numeric
Occurrences: 1/ Incident
Mandatory: Conditional
Edits: 1) Must be present in homicide incidents (Offense Code = 011, 012, 013, 014 or 015)
2) Must be present in bias crime incidents (Offense Hate/Bias Code ≠ 88)
3) [Must be present in domestic violence cases (Offense Domestic Violence = Y)]
[4 3]) Optional for all other incidents
[5 4]) Data cannot contain line feed carriage returns and should be submitted as one continuous
paragraph.
NOTE: RDW should appear as 0030
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 193
(Blank page)
Page 194 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Additional Data Elements Required by Offense Type
"Additional" data elements are applicable to certain offenses and are in addition to the Common Data Elements previously listed. They
complete the data element reporting requirements for the individual offenses. These must be entered for the specified offense.
Arson (090)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 2
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Assault Offenses (041, 042, 043, 044, 045, 046, 047[, 048])
Mandatory: Offense Attempted/Completed (2.2) = C
Type of Victim (4.3) = I [or L]
If any code but 00 in Offender Sequence Number (5.1):
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
[If Type of Victim (4.3) = L (only allowed for Offense code 041, 042 or 043)
LEOKA Type Act (4.14)
LEOKA Assignment Type (4.15)
LEOKA Activity Type (4.16)
Conditional:
LEOKA ORI-Other Officer Jurisdiction (4.17)
In addition to the above requirements, there are more for the following assault offenses:]
Only 041, 042, 043:
Type Weapon/Force Involved (2.9)
Type Injury (4.11)
Only 041, 042:
Aggravated Assault/Homicide Circumstances (4.9)
[Only 048:
Type Injury (4.11) = ‘N’]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 195
Bribery (266)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1, 6 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1, 5, 6, 7 or 8
If 5, 6, or 7 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Cargo theft (1.23) must be Y or N
Burglary/Breaking and Entering (051, 052, 053)
Mandatory: Method of Entry (2.7)
If 14 or 50 in Location Type (2.5):
Number of Premises Entered (2.6)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1, 5, 7 or 8
If 5 or 7 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Cargo theft (1.23) must be Y or N
Counterfeiting/Forgery (100)
Mandatory: Type of Criminal Activity (2.8)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 3, 5 or 6
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Page 196 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Destruction/Damage/Vandalism of Property, Crime Damage (140, 141)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 4
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Drug/Narcotic Offenses (180, 181)
Mandatory: Type of Criminal Activity (2.8)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 6
Drug Codes (6.15)
If any code but 367 in Property Description Category (3.2):
Value of Property (3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Type of Victim (4.3) = S
Only 180: If 6 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2) = Any code but 280
If 1 in Type Property Loss/Etc. (3.1):
Suspected Drug Type (3.7)
If 6 in Type Property Loss/Etc. (3.1) and 367 in Property Description Category (3.2):
Suspected Drug Type (3.7)
Estimated Drug Quantity (3.8)
Type Drug Measurement (3.9)
Only 181: If 6 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2) = Any code but 367
DUII (210)
Mandatory: DUII Intoxicant Type (6.16)
[Only if A or C in DUII intoxicant Type (6.16)]
Breath Analyzer Results (6.17)
Embezzlement (120)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Cargo theft (1.23) must be Y or N
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 197
Extortion/Blackmail (230)
Mandatory: Type of Weapon/Force Involved (2.9)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1, 6 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
If I in Type of Victim (4.3)
Type of Injury (4.11)
Fraud Offenses (111, 112, 113, 114, 115, 116, [117,] 119, 11C, 11D, 11E, 11F, 11G)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
If Offense = 114, 115, 116, [117], 119, 11C, 11E[, 11F]
Cargo theft (1.23) must be Y or N
Only 11F: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 7
Property Description Category (3.2) = 197
Value of Property(3.3) = $0
Number of Property Items (3.4) = 1
[Property Offense Code (3.5) = 11F
Only 117: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 7
Property Description Category (3.2) = 197
Value of Property(3.3) = $0
Number of Property Items (3.4) = 1
Property Offense Code (3.5) = 117
Victim type (4.3) = G (Government)]
Page 198 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Gambling Offenses (191, 192, 193, 194, 195, [196,] 199)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 6
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Type of Victim (4.3) = S
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Only 194: Type of Criminal Activity (2.8)
Homicide Offenses (011, 012, 013, 014, 015)
Mandatory: Offense Attempted/Completed (2.2) = C
Type of Weapon/Force Involved (2.9)
Type of Victim (4.3) = I
Aggravated Assault/Homicide Circumstances (4.9) [= 1-10]
If any code but 00 in Offender Sequence Number (5.1):
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
Only 014: Aggravated Assault/Homicide Circumstances (4.9) = 30-34
Only 015: Aggravated Assault/Homicide Circumstances (4.9) = 20 or 21
Additional Justifiable Homicide Circumstances (4.10)
Kidnapping/Abduction (251, 252, 253, 254, 255, 256, [257])
Mandatory: Type of Weapon/Force Involved (2.9)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1, 5, 7, or 8
If 5 or 7 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Type of Victim (4.3) = I
Type of Injury (4.11)
If any code but 00 in Offender Sequence Number (5.1):
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 199
Larceny/Theft Offenses (061, 062, 063, 064, 065, 066, 067, 068, 069)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Only 065: If C in Offense Attempted/Completed (2.2):
Property Description Category (3.2) = 200
Only 066: If C in Offense Attempted/Completed (2.2):
Property Description Category (3.2) = 010
If Offense = 064, 067 or 069
Cargo theft (1.23) must be Y or N
Motor Vehicle Theft (071)
Mandatory: If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2) = 321 – 329 & 331
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
Cargo theft (1.23) must be Y or N
Pornography/Obscene Material (170)
Mandatory: Type of Criminal Activity (2.8)
Type of Victim (4.3) = S
Prostitution Offenses (161, 162, 163, [164,] 169)
Mandatory: Type of Victim (4.3) = S
Page 200 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Robbery (031, 032, 033, 034, 035, 036, 037, 039)
Mandatory: Type of Weapon/Force Involved (2.9)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 5 or 7
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
If 5 in Type Property Loss/Etc. (3.1):
Date Recovered (3.6)
If I in Type of Victim (4.3)
Type of Injury (4.11)
If I in Type of Victim (4.3) and
If any code but 00 in Offender Sequence Number (5.1)
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
Only 037: If C in Offense Attempted/Completed (2.2):
Property Description Category (3.2) = 321 - 329 and [330 331]
Cargo theft (1.23) must be Y or N
NOTE: On sex offenses – Forcible Rape (020) and Non-Force /Statutory Rape (171) one or
more offenders must be a different sex than the victim.
Sex Offenses, Forcible (020, 177, 17C, 173)
Mandatory: Type of Weapon/Force Involved (2.9)
Type of Victim (4.3) = I
Type of Injury (4.11)
If any code but 00 in Offender Sequence Number (5.1)
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
Sex Offenses, Non-forcible (171, 175)
Mandatory: Type of Victim (4.3) = I
If any code but 00 in Offender Sequence Number (5.1)
Related Offender(s) (4.12)
Relationship(s) of Victim to Offender (4.13)
Only 171 Victim age must be less than 18.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 201
Stolen Property Offenses (130, 530, 540)
Mandatory:
*If 130:
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 5
If 5 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Date Recovered (3.6)
If A in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 or 8
Type of Criminal Activity (2.8)
[Type of Victim (4.3) ≠ S]
If 530 or 540:
If C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = [1 or 5]
If 5 in Type Property Loss/Etc. (3.1):
Property Description Category (3.2)
Value of Property(3.3)
Number of Property Items (3.4)
Property Offense Code (3.5)
Date Recovered (3.6)
[Type of Victim (4.3) = S]
*Restructured the above section
Unauthorized Entry to Motor Vehicle (075)
Mandatory: If A or C in Offense Attempted/Completed (2.2):
Type Property Loss/Etc. (3.1) = 1 [or 8]
Weapon Law Violations (151, 152, 153, 154, 155, 159)
Mandatory: Type of Criminal Activity (2.8)
Type of Weapon/Force Involved (2.9), weapon can be any code EXCEPT 40, 99
Type of Victim (4.3) = S
If 155: Type of Weapon/Force (2.8) = 60 or 65
Page 202 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Additional Edits
The following edits look at the incident as a whole, rather than at a specific data element and reflect relationships between segments that
must be addressed within the submitting agency's software. The edits are grouped by category.
General Edits
Duplicate Segments Not Allowed
When a Group "A" Incident Report is submitted, the individual segments comprising the incident cannot contain duplicates. For
example, if two Offense Segments have the same value for the Offense Code (2.1), or if two Property Segments have the same
code entered in Type of Property Loss/Etc.(3.1), an error will be detected.
Cannot submit duplicate reports
Submitting two Incident Reports having the same ORI and Incident Number will generate an "Incident Already on File" error
condition (i.e., duplicate incident report). Ensure that each participant uses unique incident numbers within the ORI.
Incident Reports Must Have a Level 1 Segment
The first level within an Incident Report must be the Administrative Segment (Level 1).
Incident Reports Require A Minimum of Four Segments
If an Incident Report is submitted, the following segments must be included: Administrative Segment; Offense Segment; Victim
Segment; and Offender Segment.
The Processing Date Cannot Be Before The Date The Data Represents
The Month/Year in positions 7 through 12 of each record needs to equal(=) or be less than the processing month.
All Segments On the Electronic Media Must Have the Same Control Information
Each segment on the data submitted must contain the same "Month of File" and "Year of File" values in positions 7-12. The first
segment processed will be compared with all other segments to check for this condition.
All Segments for an Incident Must Be In Proper Order
All segments for an Incident Report must be in numeric order. For example, an incident having segments 1, 2, 2, 3, 4, 4, 4, 5, I, H,
V, V must be written in that order, not as 1, 2, 2, 5, 3, 4, 4, 4, I, H, V, I.
Valid Record Levels Are A, 0 - 6, I, H, and V
Every record submitted must have a valid record level as reflected in above. Levels 1 - 7 are for Incident Reports, Level A for
Agency, I for Individual, H for Individual Supplement, V for Vehicle, and Level 0 for Zero-Reporting.
Administrative Segments
Incident Date Cannot Be After Year and Month of File
The date entered into Incident Date/Hour (1.3) cannot be greater than that entered within the "Month of File" and "Year of File"
fields on the data record. For example, if "Month of File" and "Year of File" are "01” and “2011” respectively, data element 1.3 then
could NOT contain any date 02/01/2011 or greater. On the other hand, this date can be less than 01/2011, thus including crimes
occurring in previous months/years.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 203
Offense Segments
Only 10 Offenses per Incident Report Allowed
The maximum number of offenses that can be submitted for an Incident Report is 10.
Each Offense Segment Must Have A Victim Segment Linked to It
Each Offense Segment must have at least one Victim Segment pointing to it via Victim Connected to Offense Codes (4.2).
An Offense Segment cannot stand alone; it must have at least one Victim Segment linked to it.
Mutually Exclusive Offenses Submitted
Each offense submitted belongs to a specific offense classification. No more than one offense from each category may be
submitted as part of the same victim. The following table defines the offenses that are exclusive.
• 011, 012, 013, 014, 015
• 031, 032, 033, 034, 035, 036, 037, 039
• 041, 042, 043. 044, 045, 046, [048]
• 051, 052, 053
• 064, 075
• 071, 075
• 111, 112, 113
• 162, 163, 169
• 191, 193, 199
• 201, 202, 209
• 251, 252, 253, 254, 255, 256
•
• For Sex offense exclusions, see Oregon Specific edits section.
Property Segments
Property Offenses Must Have A Property Segment
If an Incident Report is submitted that contains an Offense Segment for an offense of "Crime Against Property," Kidnapping,
Gambling, or Drug/Narcotic, a Property Segment must also be submitted.
Drug Property Segment Must Have an Offense Segment for Offense Code 180
If a Property Segment containing 367 = Drugs/Narcotics for Property Description Category (3.2) is submitted and Value of
Property (3.3) is blank, there must be an Offense Segment for 180 = Drug/Narcotic Violations.
Crime Against Property Offenses Must Be Submitted When Property Segments are Submitted
Property Segments can only be submitted with offenses relating to "Crimes Against Property," Kidnapping, Gambling, or
Drug/Narcotic offenses.
Type Property Loss/Etc. Codes Must Be Related to the Offense
Refer to the Mandatories section for specifications about which Type Property Loss/Etc. (3.1) codes can be submitted for
offenses requiring Property Segments submissions. For example, a completed Arson requires a loss code of "2" = Burned.
Property Loss = 6 And Offense 180, 181 Require Specific Attention for Property Descriptions
of 367 and 280
To ensure that 180 and 181 Drug/Narcotic Offenses are properly reported, Property Description Category (3.2) cannot be
280 = Drug/Narcotic Equipment for a 180 Drug/Narcotic Violation. Similarly, 367 = Drugs/Narcotics cannot be entered for a
181 Drug Equipment Violation. This is enforced by software when there is a single "Crimes Against Property" offense.
Page 204 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
However, in multiple "Crimes Against Property" offenses where one offense is a 180 Drug/Narcotic Violation and the other is,
say, a Robbery that involves 280 = Drug/Narcotic Equipment, it can be entered. In this case, the above edit is bypassed.
Similarly, 367 = Drugs/Narcotics can be entered along with a 181 Drug Equipment Violation as long as that property is
involved in the Robbery.
Victim Segments
A Victim Must be Connected to All Offenders
When a victim is connected to a "Crime Against Person" or Robbery, all Offender Sequence Numbers (5.1) must be entered
in Related Offenders (4.12). If more than 10 offenders, use the 10 "closest" in relationship to the victim. In other words, if
there were 15 offenders and 14 were neighbors and 1 was the brother, ensure that the brother was 1 of the 10 offenders.
Crimes Against Society Can Only Have One Victim Segment
If the only Offense Segment (Level 2) submitted is a "Crime Against Society," there can only be one Victim Segment. This
victim must have a value of "S" = Society/Public in Type of Victim (4.3).
Victim References to Offense Codes Must Have Offense Segment Counterparts
Each Offense Code entered into Victim Connected to Offense Codes (4.2) must have a corresponding Offense Segment. A
victim cannot be connected to an offense when the offense itself is not present.
Arrestee Segments
No Arrestee Records are Permitted for A Justifiable Homicide
Incident Reports cannot have arrests when Offense Code is Justifiable Homicide. This is because by definition a justifiable
homicide never involves an arrest of the offender (the person who committed the justifiable homicide).
No Arrestee Segments Allowed When Incident is Cleared Exceptionally
Whenever an Exceptional Clearance is submitted in the Administrative Segment, there can be no Arrestee Segments
associated with the Incident Report.
Number of Arrestees Cannot be Greater Than Number of Offenders
When arrests are made for Incident Report incidents, the number of arrests cannot be greater than the number of offenders.
For example, if the number of offenders was at first unknown and the case was later cleared with an arrest, the Incident
Report must be resubmitted with at least one offender. Another example would be if the incident was initially submitted with
one offender and three months later two arrests were made. In this case, the incident would be resubmitted showing two
offenders and two arrests.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 205
Offense Code Edits
In addition to edits specified within the [mandanatories] section, a finer level of editing criteria is presented below for selected offenses.
Justifiable Homicide (015)
1) Aggravated Assault/Homicide Circumstances (4.9) can only have codes of:
20 Criminal Killed by Private Citizen
21 Criminal Killed by Police Officer.
No other code is allowable.
2) When a Justifiable Homicide is reported, no other offense may be reported in the Incident Report. These would be
submitted on another Incident Report.
3) Incident Reports cannot have arrests when Offense Code (2.1) is 015 = Justifiable Homicide. This is because by
definition a justifiable homicide never involves an arrest of the offender (the person who committed the justifiable
homicide).
Forcible Rape (020)
Sex of Victim (4.5) must be M = Male or F = Female to be connected to this offense code and at least one offender must be
the opposite sex.
Aggravated Assault (041, 042)
Aggravated Assault/Homicide Circumstances (4.9) can only have codes of 01 through 06, and 08 through 10. All other
codes, including 07 = Mercy Killing, are not valid because they do not relate to an aggravated assault.
Simple Assault (043)
Type Weapon/Force Involved (2.8) can only have codes of:
40 Personal Weapons
90 Other
95 Unknown
All other codes are invalid because they do not relate to a simple assault.
[Assaults (041, 042, 043)
Physcial assault offenses cannot be submitted on the same victim with any of the theft offenses.]
Burglary/Breaking and Entering (051, 052, 053)
Type of Victim (4.3) cannot have a value of S = Society/Public.
[Unauthorized Entry to Motor Vehicle (075)
Property loss type must be 1 (none).]
Statutory Rape (171)
Sex of Victim (4.5) must be M = Male or F = Female to be connected to this offense code and at least one offender must be
the opposite sex.
Curfew/Juvenile only (280)
Age of Arrestee (6.9) must be 01 to 17.
Runaway (290)
Age of Arrestee (6.9) must be 01 to 17.
Page 206 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Narrative Segment Edits
A narrative is required for all homicide incidents (Offense Code = 011, 012, 013, 014 or 015), for all bias crime incidents (Offense
Hate/Bias Code ≠ 88), and for incidents where Domestic Violence Indicator ≠ N. The narrative should include enough detail to briefly
describe what occurred in the incident and why it is being coded as bias or domestic violence. In cases of bias crimes, enough detail
must be included to show the offender committed the crime because of a bias/hatred of/for the victim(s). E.g., the offender assaulted
the victim strictly based on the victim’s race, religion, sexual orientation, etc.
A narrative is optional for all other incidents, although strongly encouraged.
[Narratives cannot contain any formatting characters. No carriage returns, line feeds or tabs.]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 207
Oregon Specific Edits
Oregon Specific Edits on Offense Combinations
If Offense Code = Same victim cannot include:
[011 (Willfull Murder) 012, 013, 041, 043, 045)
[013 (Negligent Manslaughter) 011, 012, 041, 043, 045)
020 ( Forcible Rape) [041, 043, 045, ]171, 173, 175
[031-039 (Robbery) 041, 043, 045, 061-069, 071]
041-046 (Assault) 020, 031-039, 171-179
[064 (Theft from Motor Vehicle) 075
075 (Unauthorized Entry to Motor Vehicle) 064,071]
171 (Non Force Rape/Statutory) 020, [172], 173, [174, 175, 176], 177, [178, 179,] 17C
173 (Physical Molest) [043, 045, ]020, 171, 175, 177, 178, 17C
175 (Incest) 020, [172], 173, [174,] 177, 17C
177 (Forcible Sodomy) [041, 043, 045, ]171, 172, 173, 174, 175
17C (Sexual Assault w/Object) [041, 043, 045, ]171, 172, 173, 174, 175
17D (Invasion of Personal Privacy) 172, 174, 179
17F (Unlawful Contact with Minor) 172, 174, 17E [(Unlawfully being where minors congregate)]
If Offense Code = Same victim may also include from the sex offense category:
172 (Cont. to Sex. Delinq.-minor) 173, [179]
174 (Obscene Phone Call) 176, [179]
Oregon Specific Offense Codes That Need Property Code Edits
If offense code = Property Description Code must =
037 (Car Jacking) 321-329 Motor Vehicle, [330 Miscellaneous Vehicles and 331]
065 (Theft of Motor Vehicle 200 Vehicle Parts/Accessories
Parts/Accessories)
066 (Theft of Bicycle) 010 Bicycle
071 (Motor Vehicle Theft) 321-329 [and 331] Motor Vehicle
11F (Identity Theft) 197 Identity
Property Value Code Edits
If property code = Property Value Code must be =
143, 144, 146, 190, 195, 197 All must have a value of $0 (zero).
Page 208 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Electronic Submission Specifications
Data may be submitted monthly via FTP or upload. This section describes the data submission format.
[Upload E-mail] or FTP test data to: Nancy Sharp. Production data will be sent via FTP or agencies may use the online tools to upload and
process their data.
Questions concerning specifications contact:
Nancy Sharp at [(503) 934-2155]
nancy.m.sharp@state.or.us or
[Michael Hawkins, Program Manager at 503 934-2342
Michael.Hawkins@state.or.us]
osp.oucr@state.or.us
File Name Format
Data may be submitted either via FTP or upload.
The filename on all submitted data should follow these examples: 0240000X.014.
There should be a leading zero”0” followed by the 6 digit ORI for the reporting agency. This is followed by an “X”.
The extension name is the two digit month and single digit year of reporting.
In this example we have Marion County SO – agency 240000, reporting for January of 2014.
FTP or Upload Submission
Records should be formatted in fixed field length, ASCII. Each record must end with a carriage return line feed (CR/LF). Field
delimiters between fields are not allowed.
Each record written to must first be initialized to "BLANKS/SPACES" before data is moved into the fields. This will provide "filler" for
those Data Elements which do not have data because of the circumstances of the report.
Data should be uploaded or posted on the FTP server. To receive instructions and login information contact Nancy Sharp.
Variable Length Record Format
Each different Segment Level number is for a specific segment which has its own fixed length but is written as a variable length record
using a 4-byte Record Descriptor Word (RDW) at the beginning of each record. For example, every Segment Level 1 written is 243
characters long; Segment Level 3 is 576 characters long; etc. Although each segment is written as a variable-length record, all records
for a given segment are the same length. Therefore, each Segment Level must be written with its appropriate fixed length as indicated
within Subsection 11 (Segment Levels).
[Data Records Should be Initialized to Blanks
Each record written to magnetic media must first be initialized to "BLANKS/SPACES" before data is moved into the fields. This will
provide "filler" for those Data Elements which do not have data because of the circumstances of the report. ]
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 209
Codes Must be Right-Justified with Zero Left-Fill
Fields containing "numeric" data codes must be right-justified with zero left-fill when there are data to be reported. For example, if Data
Element 15 (Property Description) code is "05" = Buses, value "05" would be entered, not "5 " or " 5". [For non-required data elements,
spaces are preferred over filling fields with zeros or null values.]
Record Descriptor Word (RDW) Explanation
The specifications state that records must be variable-length. Accordingly, each of the Segment Levels contains a 4-byte field that
reflects its specific record length. For example, the Administrative Segment has a Record Descriptor Word (RDW) containing a numeric
length of "244" that is the length of the actual data (positions 5-244) plus the beginning 4-byte RDW.
Segment Levels
Each segment has an assigned identifier called the segment level. When submitting data, each record must be identified by specifying
the level code. Below is the level identifier for each segment.
A Agency Segment
1 Administrative Segment
2 Offense Segment
3 Property Segment
4 Victim Segment
5 Offender Segment
6 Arrestee Segment
I Individual Segment
H Individual Supplement Segment
V Vehicle Segment
0 Zero Reporting Segment
N Narrative
On the following pages, the literal code defined above is placed in position 5 (Level).
Page 210 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Action Types
The action type is a one byte alpha numeric field. This data element identifies what processing is performed by the software specific to
the specified incident segment.
I Process a complete incident report. This is used with all level identifiers. All known data values concerning the circumstances
of an incident at the time the incident is being reported. This action type is used to identify the initial submission of an incident
report as well as to report change or modification of previously submitted reports. If a previously submitted report is being
changed or modified, it first must be deleted using the action type of D as described later.
D Delete an incident report. Used with levels 0, and 1. When used with level 0, this action type specifies that an offense actually
did occur during the month specified. When used with level 1, all segments related to the ORI and Incident are deleted. When
updating incident reports with additional information, a level 1 D should be submitted before the I.
Note that the only action type that may be submitted with an agency segment is an I. The database will automatically update the
information contained within this segment without first submitting a delete.
Month and Year
The month and year fields specify the month and year of the data submission. These elements must specify a valid month and year.
Version 2.7 – July 21, 2015 O-NIBRS System Specifcation Page 211
(Blank Page)
Page 212 O-NIBRS System Specifcation Version 2.7 – July 21, 2015
Record Layout Definitions
The following record layouts define how the data will be submitted to the state in ASCII format.
Version 2.7 – July 21,2015 O-NIBRS System Specification 213
(Blank Page)
214 O-NIBRS System Specification Version 2.7 – July 21, 2015
Agency Segment
Level: A
Length: 341
Number of Segments: 1/Incident
R L A M Y O A A M A A A R O N T N F R M R S A P
D E C O E R G G N G G D U A E U A E E E Y G O
W V T N A I E E E E E M C M L M X P D G S E P
E I T R N N M N N I R E E B O I I T N U
L O H N C C O C C N P E N R A O E C L
N U Y Y N Y Y I R H R U T N M Y A
M I S E O M I T A T
B N C T T P N B N Y L N I
E A Y R E E G P A O
R M P A R E M N
E E T E
O
(A.1) (A.2) (A.3) (A.4) (A.5) (A.6) (A.7) (A.8) (A.9) (A.10) (A.11)
[4] [1] [1] [2] [4] [6] [30] [4] [2] [30] [30] [14] [14] [2] [8] [9]
1-4 5 6 7-8 9-12 13-18 19-48 49-52 53-54 55-84 85-114 115-128 129-142 143-144 145-152 153-161
N S N S F N C M N C F L A L C L S L C M A M M S M C O E A
U W U W E U I A U I E O D O I O T O O A D A A T A O U M D
M O M O M M V L M V M C D C T C A C D I D I I A I D C A D
B R B R A B I E B I A A R A Y A T A E L R L L T L E R I R
E N E N L E L S E L L T E T T E T I E I I E I L E
R R E R I R I E I S I I I N S N N N R S
M S A A S O S O O O G S G G G E S
O A O O N O N N N N N P
F L F F F C Z
E Z I I
S I T P
P Y
(A.12) (A.13) (A.14) (A.15) (A.16) (A.17) (A.18) (A.19) (A.20) (A.21) (A.22) (A.23) (A.24)
[4] [4] [4] [4] [30] [15] [2] [10] [30] [15] [2] [10] [50]
162-165 166-169 170-173 174-177 178-207 208-222 223-224 225-234 235-264 265-279 280-281 282-291 292-341
Version 2.7 July 21, 2015 O-NIBRS System Specification 215
Administrative Segment
Level: 1
Length: 2
Number of Segments: 1/Incident
R L A M Y O I N I D R I I H C E E C D C L L
D E C O E R N U N A E N N O L X C L A O O A
W V T N A I C M C T P D C U E C E E T U N T
E I T R I B I E O I I R A E P A E N G I
L O H N D E D R C D R P T R T I T
N U E R E T A E E T I A Y T U
M N N T N D I O N U D
B T T O T O N C C D E
E D R N A E O E
R A A L D
T L E
E
(1.1) (1.2) (1.3) (1.4) (1.5) (1.6) (1.7) (1.8) (1.9) (1.10)
[4] [1] [1] [2] [4] [6] [12] [8] [1] [2] [1] [8] [2] [10] [10]
1-4 5 6 7-8 9-2 13-18 19-30 31-38 39 40-41 42 43-50 51-52 53-62 63-72
A L C I A I A I A S I A C O S F I S P C N P C P P C E R D C F
G O O N D N D N D T N D O F E L N T O O A O O H O O M e a a l
E C D C D C D C D A C D D F C A C A I N M I N O I N A p t r a
N A E I R I R I R T I R E I U G I T N T E N T N N T I o e g g
C T D E D E D E E D E C R D U T A T A E T A L r o
Y I E S E S E S E S E I E S C C C t
O N S N S N S N S R T N O T O T O T e T
N T T T T Y T F F F d h
C Z I e
I I D f
T P t
Y
(1.11) (1.12) (1.13) (1.14) (1.15) (1.16) (1.17) (1.18) (1.19) (1.20) (1.21) (1.22) (1.23)
[9] [30] [15] [2] [10] [5] [1] [1] [30] [10] [50] [8] [1]
73-81 82-111 112-126 127-128 129-138 139-143 144 145 146-175 176-185 186-235 236-243 244
216 O-NIBRS System Specification Version 2.7 – July 21, 2015
Offense Segment
Level: 2
Length: 151
Number of Segments: Up to 10/Incident
(2.4) (2.8)
Occurs Occurs
3 Times 3 Times
R L A M Y O I N O A C O R S F O U L T N P E E T C A
D E C O E R N U F T O R E T i F S O Y U R N N Y R C
W V T N A I C M F T M E V A l F E C P M E T T P I T
E I T R I B E E P G I T l E D A E B M E R E M I
L O H N D E N M L O S U e N T E I R Y I V
N U E R S P E N E T r D I R S E N I
M N E T T D E E O E D M A T
B T E E R N O S E L Y
E C D D F T
R O H
D / O
E D
(1.1) (1.2) (2.1) (2.2) (2.3) (2.3a) (2.4) (2.5) (2.6) (2.7) (2.8)
[4] [1] [1] [2] [4] [6] [12] [3] [1] [8] [72] [1] [2] [2] [1] [1]
1-4 5 6 7-8 9-2 13-18 19-30 31-33 34 35-42 43-114 115 118-119 120-121 122 123
116 124
117 125
(2.9 - 2.11)
Occurs
3 Times
W F I A C I R F M T K T C H B D V I G I E L Q R
E O N U N I A Y N Y O A I O I N A N N O U
A R V T W D R K P I P D T A M O D N V T C A
P C O O E I E E E F E E E S E L . G O A L
O E L M A C A E S E L I T I
N V A P A R / T N V N I F
E T O T M I C E D O I
/ D I N O C E M . N E
(2.9) (2.9) (2.10) (2.11) (2.12) (2.13) (2.14) (2.15)
[2] [1] [3] [1] [2] [1] [1] [1]
126-127 128 129-131 132 147-148 149 150 151
133-134 135 136-138 139
140-141 142 143-145 146
Version 2.7 July 21, 2015 O-NIBRS System Specification 217
Property Segment
Level: 3
Length: 576
Number of Segments: Up to 8/Incident
3.2 - 3.6 Occurs 20 Times 3.7 - 3.9 Occurs 3 Times
R L A M Y O I N T P L D V N P I P O R D S D E D Q E D F T
D E C O E R N U Y R O E A U R T R F E A U R S R U S R R Y
W V T N A I C M P O S S L M O E O F C T S U T U A T U A P
E I T R I B E P S C U B P M P E O E P G I G N I G C E
L O H N D E E R E E E S E N V E M T M T
N U E R R / I R R R S E C T A I A I M
M N T P T T E R T Y T T T O E
B T Y E T O Y Y Y E P E Y E N A
E T I F C D E D D S
R C O O U
N D R
E E
(1.1) (1.2) (3.1) (3.2) (3.3) (3.4) (3.5) (3.6) (3.7) (3.8) (3.8) (3.9)
[4] [1] [1] [2] [4] [6] [12] [1] [3] [9] [2] [3] [8] [1] [9] [3] [2]
1-4 5 6 7-8 9-2 13-18 19-30 31 32-34 35-43 44-45 46-48 49-56 532 533-541 542-544 545-546
57-59 60-68 69-70 71-73 74-81 547 548-556 557-559 560-561
82-84 85-93 94-95 96-98 99-106 562 563-571 572-574 575-576
107-109 110-118 119-120 121-123 124-131
132-134 135-143 144-145 146-148 149-156
157-159 160-168 169-170 171-173 174-181
182-184 185-193 194-195 196-198 199-206
207-209 210-218 219-220 221-223 224-231
232-234 235-243 244-245 246-248 249-256
257-259 260-268 269-270 271-273 274-281
282-284 285-293 294-295 296-298 299-306
307-309 310-318 319-320 321-323 324-331
332-334 335-343 344345 346-348 349-356
357-359 360-368 369-370 371-373 374-381
382-384 385-393 394-395 396-398 399-406
407-409 410-418 419-420 421-423 424-431
432-434 435-443 444-445 446-448 449-456
457-459 460-468 469-470 471-473 474-481
482-484 485-493 494-495 496-498 499-506
507-509 510-518 519-520 521-523 524-531
218 O-NIBRS System Specification Version 2.7 – July 21, 2015
Victim Segment Part 1 of 2
Level: 4
Length: 213 (4.2) (4.2)
Number of Segments: Up to 999/Incident Occurs Occurs
10 Times 10 Times
R L A M Y O I N V S N O C O R S V T A S R E R S
D E C O E R N U I E U F O R E T I Y G E A T E T
W V T N A I C M C Q M F D E V A C P E X C H S A
E I T R I B T U B E E G I T T E E N I T
L O H N D E I E E N O S U I I D U
N U E R M N R S N E T M C E S
M N C E D E I N
B T E T T
E Y
R
(1.1) (1.2) (4.1) (4.2) (4.2) (4.3) (4.4) (4.5) (4.6) (4.7) (4.8)
[4] [1] [1] [2] [4] [6] [12] [3] [3] [8] [1] [4] [1] [1] [1] [1]
1-4 5 6 7-8 9-2 13-18 19-30 31-33 34-36 37-44 144 145-148 149 150 151 152
45-47 48-55
56-58 59-66
67-69 70-77
78-80 81-88
89-91 92-99
100-102 103-110
111-113 114-121
122-124 125-132
133-135 136-143
Continued on next page
Version 2.7 July 21, 2015 O-NIBRS System Specification 219
Victim Segment Part 2 of 2
Continued from previous page
(4.9) (4.11) (4.12) (4.13)
Occurs Occurs Occurs Occurs
2 Times 5 Times 10 Times 10 Times
A A H C A H I O N R R S T L O L A T L A T O O
G S O I D O N F U E E H O O E F E S Y E C Y T F
G S M R D M J F M L L I F O O S P O T P H F
R A I C ' . U E B A A P F K A K I E K I E E I
A U C U T R N E T T E A C A G A V R C
V L I M L C Y D R E I V N T N I E
A T D S I E D O I D T I M T R
T E T J R T R T N C E Y V E Y
E / A U C Y O T R P I N O
D N S U P I E T T R
C T M E B M Y I
E . . E
(4.9) (4.10) (4.11) (4.12) (4.13) (4.14) (4.15) (4.16) (4.17)
[2] [1] [1] [2] [2] [1] [2] [2] [6]
153-154 157 158 163-164 165-166 203 204-205 206-207 208-213
155-156 159 167-168 169-170
160 171-172 173-174
161 175-176 177-178
162 179-180 181-182
183-184 185-186
187188 189-190
191-192 193-194
195-196 197-198
199-200 201-202
220 O-NIBRS System Specification Version 2.7 – July 21, 2015
Offender Segment
Level: 5
Length: 39
Number of Segments: Up to 99/Incident
R L A M Y O I N O S N A S R E
D E C O E R N U F E U G E A T
W V T N A I C M F Q M E X C H
E I T R I B E U B E N
L O H N D E N E E I
N U E R D N R C
M N E C I
B T R E T
E Y
R
(1.1) (1.2) (5.1) (5.2) (5.3) (5.4) (5.5)
[4] [1] [1] [2] [4] [6] [12] [2] [4] [1] [1] [1]
1-4 5 6 7-8 9-2 13-18 19-30 31-32 33-36 37 38 39
Version 2.7 July 21, 2015 O-NIBRS System Specification 221
Arrestee Segment
Level: 6
Length: 98 (6.6)
Number of Segments: Up to 99/Incident Occurs 5 (6.7)
Times Occurs 2 Times
R L A M Y O I N A S N A T N A T A M A S I A O C A WW A W I
D E C O E R N U R E U R R U R Y R U R E N R F O R A I U E N
W V T N A I C M R Q M R A M R P R L R G D R F D R S T T A D
E I T R I B E U B E N B E E E T E M I E E E E H O P I
L O H N D E S E E S S E S S I S E C S N S A M O C
N U E R T N R T . R T O T P T N A T S T R A N A
M N E C F L E T T E E M T T
B T E E D E E S O E E I O
E A R D C R
R T
E
(1.1) (1.2) (6.1) (6.2) (6.3) (6.4) (6.5) (6.6) (6.7) (6.7)
[4] [1] [1] [2] [4] [6] [12] [2] [12] [8] [1] [1] [3] [2] [1]
1-4 5 6 7-8 9-2 13-18 19-30 31-32 33-44 45-52 53 54 55-57 70-71 72
58-60 73-74 75
61-63
(6.15)
Juvenile Occurs 64-66
Disp. 3 Times 67-69
A D B A S R E R S D O U D D I T B A R
R A I G E A T E T I F N R U N Y R N E
R T R E X C H S A S D U I T P E A S
E E T E N I T P A E G I O E A L U
S H I D U O R R X T Y L
T O C E S S R C I H Z T
E F I N I E 1 O C E S
E T T T S 8 D A R
Y I T E N
O E S T
N E
(6.8) (6.9) (6.10) (6.11) (6.12) (6.13) (6.14) (6.15) (6.16) (6.17)
[8] [4] [1] [1] [1] [1] [1] [1] [1] [2]
76-83 84-87 88 89 90 91 92 93 96 97-98
94
95
222 O-NIBRS System Specification Version 2.7 – July 21, 2015
Individual Segment
Level: I
Length: 398
Number of Segments: Up to 999/Incident
R L A M Y O I N I T I S N N D B A S R E
D E C O E R N U N Y N E U A A I G E A T
W V T N A I C M D P D Q M M T R E X C H
E I T R I B I E I U B E E T E N
L O H N D E V V E E H I
N U E R I I N R O C
M N D D C F I
B T U U E T
E A A Y
R L L
(1.1) (1.2) (I.1) (I.2) (I.3) (I.4) (I.5) (I.6) (I.7) (I.8)
[4] [1] [1] [2] [4] [6] [12] [1] [3] [30] [8] [4] [1] [1] [1]
1-4 5 6 7-8 9-2 13-18 19-30 31 32-34 35-64 65-72 73-76 77 78 79
(I.15) (I.19)
Occurs 3 Occurs 9
Times Times
R S H E S H W S T G A C C I R S F A
E T A Y K E E C A A F O O N E E L L
S A I E I I I A T N F D R D G X A I
I T R N G G R T G L E R I I G A
D U C H H S O E I E C S O S
E S C O C T T O L C A T F
N O L O M S A T T E F
T L O L A T I O R E
O R O R I O R E N
R R K O N D E
S N S R
(I.9) (I.10) (I.11) (I.12) (I.13) (I.14) (I.15) (I.16) (I.17) (I.18) (I.19)
[1] [3] [3] [3] [3] [3] [10] [1] [1] [1] [30]
80 81-83 84-86 87-89 90-92 93-95 96-105 126 127 128 129-158
106-115 159-188 279-308
116-125 189-218 309-338
219-248 339-368
249-278 369-398
Version 2.7 July 21, 2015 O-NIBRS System Specification 223
Individual Supplemental Segment
Level: H
Length: 243
Number of Segments: Up to 999/Incident
R L A M Y O I N I T I S N I A I A C I A S I A C
D E C O E R N U N Y N E U N D N D I N D T N D O
W V T N A I C M D P D Q M D D D D T D D A D D D
E I T R I B I E I U B I R I R Y I R T I R E
L O H N D E V V E E V E V E V E E V E
N U E R I I N R I S I S I S I S
M N D D C D S D S D S D S
B T U U E U U U U
E A A A A A A Z
R L L L L L L I
P
(1.1) (1.2) (I.1) (I.2) (H.1) (H.2) (H.3) (H.4)
[4] [1] [1] [2] [4] [6] [12] [1] [3] [30] [15] [2] [10]
1-4 5 6 7-8 9-2 13-18 19-30 31 32-34 35-64 65-79 80-81 82-91
Occurs 3 Occurs 3 Occurs 3 Occurs 3
Times Times Times Times
I T N O P I O P I O P I O A C C
N E U C E D N E D N E D N U I o
D L M C R E R E R E T T u
I E B U S N N S N T S N I H I n
V P E P O T U O T Y O T S O Z t
I H R A N I M N I P N I S R E r
D O T A F B A F E A F U I N y
U N I L I E L I L I I T S
A E O C R C C N Y H C
L N A A A G I o
T T T P d
I I I e
(H.5) (H.6) (H.7) (H.8) (H.9) (H.10) (H.11)
[10] [25] [15] [1] [15] [2] [2]
92-101 122-146 147-161 192 195-209 240-241 242-243
102-111 162-176 193 210-224
112-121 177-191 194 225-239
224 O-NIBRS System Specification Version 2.7 – July 21, 2015
Vehicle Segment
Level: V
Length: 93
Number of Segments: Up to 99/Incident
R L A M Y O I N V S N L N L S L L V N
D E C O E R N U E E U I U I T I I E U
W V T N A I C M H Q M C M C A C C H M
E I T R I B I U B E B E T E E I B
L O H N D E C E E N E N E N N C E
N U E R L N R S R S S S L R
M N E C E E E E E
B T E
E Y T I
R E Y D
A P
R E
(1.1) (1.2) (V.1) (V.2) (V.3) (V.4) (V.5) (V.6)
[4] [1] [1] [2] [4] [6] [12] [2] [8] [2] [4] [2] [20]
1-4 5 6 7-8 9-2 13-18 19-30 31-32 33-40 41-42 43-46 47-48 49-68
V V V M V S V C V R V C V I C
E E E O E T E O E E E O E N O
H H H D H Y H L H C H N H V D
I I I E I L I O I O I D I O E
C C C L C E C R C V C I C L
L L L L L L E L T L V
E E E E E E R E I E E
E O M
Y M T D N E
E A Y N
A K P T
R E E
(V.7) (V.8) (V.9) (V.10) (V.11) (V.12) (V.13) (V.14)
[4] [4] [3] [2] [7] [3] [1] [1]
69-72 73-76 77-79 80-81 82-88 89-91 92 93
Version 2.7 July 21, 2015 O-NIBRS System Specification 225
Narrative Segment
Level: N
Length: 10,030
Number of Segments: Up to 1/Submission
R L A M Y O I N N
D E C O E R N U A
W V T N A I C M R
E I T R I B R
L O H N D E A
N U E R T
M N I
B T V
E E
R
(1.1) (1.2) (N.1)
[4] [1] [1] [2] [4] [6] [12] [10,000]
1-4 5 6 7-8 9-2 13-18 19-30 31-10030
226 O-NIBRS System Specification Version 2.7 – July 21, 2015
Zero Reporting Segment
Level: 0
Length: 36
Number of Segments: Up to 1/Submission
R L A M Y O I N Z M Z Y
D E C O E R N U E O E E
W V T N A I C M R N R A
E I T R I B O T O R
L O H N D E H
N U E R R R
M N E E
B T P P
E O O
R R R
T T
(1.1) (0.1) (0.2) (0.3)
[4] [1] [1] [2] [4] [6] [12] [2] [4]
1-4 5 6 7-8 9-2 13-18 19-30 31-32 33-36
Version 2.7 July 21, 2015 O-NIBRS System Specification 227
(Blank Page)
228 O-NIBRS System Specification Version 2.7 – July 21, 2015
Change Revision Summary (v. 2.5)
The following is the record of changes made in version 2.5, dated March 8, 2010.
Page ii Inside Cover Page Notes
Page 7 Change in verbiage on offense 155
Page 8 Added offense 256 – Involuntary Servitude/Human Trafficking
Page 13 Added Cargo Theft to the Administrative Record
Page 16 Renamed data element 4.2 Victim Connected to Offense Code(s) to 4.2a and added 4.2b Victim Connected to ORS(s)
Page 20 Added H.11 Individual Residence Country Code
Page 52 1.2 Incident Number, section 2, changed the verbiage for clarification
Page 68 Changed verbiage in section 4, from cannot to MUST
Page 73 Added 1.23 Cargo Theft
Page 79 Removed some strikethrough items and changed the verbiage on element 80 to include Fairgrounds
Page 83 Added verbiage in section 3, data values, element B, Possessing
Page 84 Formatting changes to data elements
Page 85 2.10 Firearm Make Code, section 4, data element reference from 2.8 to 2.9
Page 86 2.11 Knife Type Code, format and occurrences
Page 87 2.12 Offense Hate/Bias Code, added Latino to the Hispanic descriptor
Page 90 2.15 Location Qualifer, occurrences 1/offense
Page 91 3.1 Property Loss Code, section 4, included reference for offenses 530 (recovered vehicle other agency) and 540 (recovered property
other agency)
Page 92 3.2 Property Description Category: Occurrences changed from 10 to 20; Edit 5, added reference for offenses 530 (recovered vehicle other
agency) and 540 (recovered property other agency),
Pages 92-95 3.2 Data Values: various restructuring; removed strikethrough elements and repaginated the data elements.
Page 101 3.8 Estimated Drug Quantity, added verbiage.
Page 104 Section 4.2, changed to 4.2a and added 4.2b.
Page 108 Added a new code (P) per FBI direction; added African-American to data element B and Latino to data element H
Page 109 Added Latino to data element H, removed note paragraph.
Page 114 Added (4.2) after Victim Connected to Offense Codes; replaced “Robbery Offense (03x)” with “Crimes Against Property”
Page 117 Added Note: on 4.14
Page 119 Re-ordered the elements moving 1 to 2
Page 124 Added a new code (P) per FBI direction; added African-American to data element B and Latino to data element H; removed note.
Page 125 Added Latino to data element H, removed note paragraph.
Page 130 Added verbiage clarification
Page 132 Added edit 4.
Page 137 Added a new code (P) per FBI direction; added African-American to data element B and Latino to data element H
Page 138 Added Latino to data element H, removed note paragraph.
Page 145 Added verbiage clarification under L – Law Enforcement
Page 147 Added verbiage for clarification
Page 151 Added a new code (P) per FBI direction; added African-American to data element B and Latino to data element H
Page 152 Added Latino to data element H
Page 160 Added Latino to data element H
Page 174 Changed data element size from 3 to 2 and NCIC reference.
Page 175 New data element – Country Code for Individual residence
Page 195 Narrative – segment length changed, added clarification
Page 197-204 Additional Data Elements…This entire section was rearranged.
Page 198 Destruction/Damage/ etc. Added Crime Damage and offense code 141.
Page 200 Added changes to Fraud Offenses
Page 203 Added clarification for offense 171
Page 204 Added Unauthorized Entry of Motor Vehicle
Page 204 Added Offense 155 to Weapon Violations and validation for 155.
Page 206 Removed strikethroughs
Page 210 Removed strikethroughs and added information on 064 & 075 as well as property edits for 11F
Page 217 Changed record length to 244, added Cargo Theft Flag
Page 221 Victim Segment Part 2 of 2, previously printed version was missing some data elements.
Page 225 Individual Supplement Segment, changed citizenship field size and added country code, changing the record length.
Page 228 Narrative Segment: changed Length
Version 2.7 – July 21, 2015 O-NIBRS System Specification 229
Change Revision Summary (v. 2.6)
The following is the record of changes made in version 2.6, dated December 8, 2011.
Page ii Inside Cover Page Notes
Page 1 Table of Contents
Page 5-10 Added additional verbiage to further describe the victim types. Added offense code 048 – Reckless Endangering; added offense code
117 – False Information to Peace Officer; changed victim type information for the 25X Kidnapping group and on 265 – Animal Cruelty;
changed headings – added group for Failure to Register
Page 11 Change in verbiage
Page 31 & 32 Added verbiage
Page 44 & 48 Slight verbiage change
Page 52 Removed references to using only 8 character incident numbers
Page 53 Formatting, changed the reference made to tape input to file input, here and throughout the manual
Page 55 1.5 Incident Hour – added DY and NT to be allowable values
Page 56 Change in verbiage about unfounded
Page 68 Added clarification for definition of the data values
Page 73 Added additional edit
Page 76 Formatting
Page 79-80 Added several new values, renamed / changed some existing
Page 84 Added additional clarification on weapon usage and corrected formatting
Page 87 Formatting, spelling
Page 88 Formatting
Page 90 Added additional value – U – Unknown and included a definition of each structure type
Page 92-94 Changed reference from 10 to 20 in heading. Added 095 and 146 data values, added exception on value 197
Page 95 Added additional data values to the edit descriptions
Page 99 Added drug category to the list of data values
Page 105 Added information about using victim type “L”
Page 110 Removed a line and reformatted
Page 128 Added more clarification to formatting of the arrest (transaction) number
Page 134 Added additional DOB information to edit 1
Page 139 Minor verbiage changes
Page 141 Added reference for drug category
Page 145 Added descriptions to other Individual Types and added value M – Other mentioned
Page 146 Added clarification verbiage
Page 148 Added clarification verbiage
Page 153 Minor verbiage changes
Page 162 Added additional value – U – unknown
Page 171 Spelling correction
Page 177 Added additional verbiage
Page 195 Added additional clarification
Page 197-204 Updated element references for cargo theft.
Page 200 Added 11F to list of Fraud offenses
Page 201 Added references to 014 under homicide and 256 under Kidnapping
Page 202 Added reference to property type 331 under allowed property for Motor Vehicle Theft
Page 204 Added additional edit information on Weapon Laws
Page 206 Added 064, 075 to exclusives as well as 256
Page 208 Added additional clarification under Forcible Rape and Statutory Rape
Page 209 Added additional information under Narrative
Page 210 Updated the Oregon Specific Edits on the Sex offenses. Added an additional data value under the property value edits
Page 211 Changes to Submission section, verbiage and clarification; changes format section
Page 212 Verbiage changes to the Record Descriptor Word
Page 213 Changes in formatting
Change Revision Summary (v. 2.6a)
Page 93 Added property 185 – Luggage (suitcases, attaché, back packs (non-camping), steamer trunks
Under data value 197 – Added offense 117.
Page 145 Change the bullet on the offense section to an “O”.
Page 189 Added two new Recovered Vehicle conditions.
Page 200 Added offense to Fraud list and detail for offense requirements for offense 117
Page 206 Added offense 048 to the list of assault offenses that are exclusive
230 O-NIBRS System Specification Version 2.7 – July 21, 2015
Change Revision Summary (v. 2.7)
The following is the record of changes made in version 2.7, dated December 17, 2013.
Page 5 Addition of offense 164 – Purchase Prostitution/Human Trafficking
Page 6 Addition of offense 256 – Involuntary Servitude/Human Trafficking
Page 6 Removal of Persons and Property on offense 269 – only allows Society
Page 8 Removal of offense code 520 – Warrant; change 550 to Warrant
Page 23 Changed section title
Page 25 Section A.1 - additional detail on the ORI format
Page 27-48 Section A.2 – notations about the use of agency information. Referencing A.3 through A.24.
Page 29 Section A.5 – removal of a comma
Page 30 Section A.6 – removal of a comma
Page 36-39 Section A.12-15 – additional definitions for counting Law Enforcement Employees, and notations about entering information directly to the
O-NIBRS website.
Page 59 Section 1.11 – added ‘Alpha’ to the Format.
Page 71 Section 1.23 – Cargo Theft – added offenses 117 and 11F.
Page 75 Section 2.3 – additional information for coding Statutes
Page 76 Section 2.4 – clarification added to data values.
Page 77-78 Section 2.5 – added 97 Community Center, rearranged values to proper heading groups and added description detail to code 96
Page 79 Section 2.6 – additional clarification added
Page 81 Section 2.8 – re-ordered the data values in numeric or alpha sequence, added mandatory clarification
Page 82 Section 2.9 – Change verbiage from ‘Can’ to ‘Must’ on item 4; removed some verbiage; added descriptive information to data values.
Page 83 Section 2.10 – Added clarification to when firearm makes are entered.
Page 85 Section 2.11 – Added clarification to when knife types are entered.
Page 86 Section 2.12 – added and changed some descriptions
Page 88 Section 2.15 – updated the list of location types requiring this entry
Page 89 Section 3.1 – added descriptors to data values
Page 90-92 Section 3.2 – added new property categories, descriptions and corrected some data descriptors
Page 96 Section 3.6 – additional information added on when to include recovered date
Page 97 Section 3.7 – added some additional clarification
Page 104 Section 4.4 – rewording of data value 99
Page 107 Section 4.7 – addition of “N” = Not Hispanic or Latino
Page 111 Section 4.11 – changed sort order of data elements, added verbiage
Page 118 Section 4.17 – added verbiage for clarification
Page 120 Section 5.2 – rewording of data value 99
Page 123 Section 5.5 – addition of “N” = Not Hispanic or Latino
Page 125 Section 6.1 – clarifying the use of the arrestee sequence number and correlation to the offender sequence number
Page 133 Section 6.9 – rewording of data value 99
Page 136 Section 6.12 – addition of “N” = Not Hispanic or Latino
Page 140 Section 6.16 – addition of “C” combination for DUII intoxicant type
Page 141 Section 6.17 – added data value “C” for allowed DUII intoxicant
Page 143 Section I.1 – removed the bullet that should have been an ‘O” and replaced it with an “O”
Page 145 Section I.3 – edited and added verbiage
Page 147 Section I.5 – removed, edited and added verbiage
Page 148 Section I.6 – removed verbiage
Page 149 Section I.7 – removed verbiage
Page 150 Section I.8 – removed verbiage and added “N”.
Page 151 Section I.9 – removed verbiage
Page 161 Section I.19 – added definition for alias
Page 168 Section H.6 – added, edited values
Page 187 Section V.13 – added additional values, edited verbiage
Page 189 Section N.1 – added additional edit information
Page 195-202 Additional Data Elements – added, edited, removed various data values and elements under many headings
Page 204 Mutually Exclusive Offenses – added, removed and edited data values and verbiage
Page 206 Offense Code Edits – corrected verbiage; added offense
Page 207 Narrative Segment Edits – added additional verbiage for edits.
Page 208 Oregon Specific Edits – added and edited the verbiage and references
Page 209 Updated phone numbers for agency contacts; removed section about magnetic media
Page 210 Added additional information for justification of data values
Version 2.7 – July 21, 2015 O-NIBRS System Specification 231
Source: O-NIBRS_SystemSpec_07-17-2015-v2-7.docx